Difference between revisions of "Active Directory/Documentation/WDS/Management"
(Custom Image Allowance & Custom Image Naming Policies) |
(→Policies: Staging Area Policy) |
||
| Line 15: | Line 15: | ||
==Policies== | ==Policies== | ||
===Custom Image Allowance=== | ===Custom Image Allowance=== | ||
| − | All college IT units are allotted one guaranteed custom image slot. In addition, each department within each college is allotted one guaranteed custom image slot. If departmental IT staff are not using their slot, then the college IT unit is permitted to use that slot. Note that these are guaranteed numbers - space permitting, each unit may utilize additional custom image slots. However, if space becomes scarce, units with additional custom images may be required to reduce their usage so that other units may utilize their guaranteed slots. | + | All college IT units are allotted one guaranteed custom image slot. In addition, each department within each college is allotted one guaranteed custom image slot. If departmental IT staff are not using their slot, then the college IT unit is permitted to use that slot. Note that these are guaranteed numbers - space permitting, each unit may utilize additional custom image slots. However, if storage space becomes scarce, units with additional custom images may be required to reduce their usage so that other units may utilize their guaranteed slots. |
===Custom Image Naming=== | ===Custom Image Naming=== | ||
In order to keep custom image listings on the server sane, the following image naming convention will be required for custom images: ''<OU>-<PreferredName>'', where <OU> is the OU prefix of the unit managing the custom image (examples: COEDEAN, CNR, ECE, OIT), and <PreferredName> is the name of the image as given by the unit managing the custom image. | In order to keep custom image listings on the server sane, the following image naming convention will be required for custom images: ''<OU>-<PreferredName>'', where <OU> is the OU prefix of the unit managing the custom image (examples: COEDEAN, CNR, ECE, OIT), and <PreferredName> is the name of the image as given by the unit managing the custom image. | ||
| + | |||
| + | ===Staging Area=== | ||
| + | The staging area of the deployment DFS share (\\wolftech.ad.ncsu.edu\deployment\staging) shall contain, at minimum, the following subfolders: | ||
| + | * Images | ||
| + | * Drivers | ||
| + | * Boot | ||
| + | |||
| + | These folders shall be used in a temporary manner for the drop-off and pick-up purposes of users and WDS service admins. The images and drivers subfolders are self-explanatory; the boot subfolder is for boot images. To preserve space, the images and boot folders will be regularly cleaned after processing these images. | ||
==Other== | ==Other== | ||
Revision as of 16:59, 17 July 2009
This section provides documentation and policy information for WDS server administrators and others on campus with an interest in the centralized WDS system. This includes lab administrators, custom image maintainers, and administrators of WDS servers outside of the centralized WDS infrastructure.
Documentation
- [[../Using WDS with WolfPrep|Using WDS with WolfPrep]]
- [[../WDS_NICDrivers| Troubleshooting NIC Drivers]]
- [[../WDS_Images| Images]]
- [[../Performance|Performance Documentation]]
The following pages are intended as a reference to WDS server administrators. They contain no user documentation.
- Setting up a WDS server
- [[../Separating DHCP From WDS|Separating DHCP From WDS]] (also known as Cross-VLAN PXE booting to WDS)
- [[../Creating Bootable Discover CDs|Creating Bootable Discover CDs]]
- Image Management
Policies
Custom Image Allowance
All college IT units are allotted one guaranteed custom image slot. In addition, each department within each college is allotted one guaranteed custom image slot. If departmental IT staff are not using their slot, then the college IT unit is permitted to use that slot. Note that these are guaranteed numbers - space permitting, each unit may utilize additional custom image slots. However, if storage space becomes scarce, units with additional custom images may be required to reduce their usage so that other units may utilize their guaranteed slots.
Custom Image Naming
In order to keep custom image listings on the server sane, the following image naming convention will be required for custom images: <OU>-<PreferredName>, where <OU> is the OU prefix of the unit managing the custom image (examples: COEDEAN, CNR, ECE, OIT), and <PreferredName> is the name of the image as given by the unit managing the custom image.
Staging Area
The staging area of the deployment DFS share (\\wolftech.ad.ncsu.edu\deployment\staging) shall contain, at minimum, the following subfolders:
- Images
- Drivers
- Boot
These folders shall be used in a temporary manner for the drop-off and pick-up purposes of users and WDS service admins. The images and drivers subfolders are self-explanatory; the boot subfolder is for boot images. To preserve space, the images and boot folders will be regularly cleaned after processing these images.
Other
These external links may be helpful as references.