Difference between revisions of "Active Directory/Documentation/WDS/Management"
(→Policies: Staging Area Policy) |
(→Policies: Custom Image Policies rework; Add Permissions policy) |
||
| Line 14: | Line 14: | ||
==Policies== | ==Policies== | ||
| − | ===Custom | + | ===Custom Images=== |
| + | ====Allowances==== | ||
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. | 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. | ||
| − | === | + | ====Naming==== |
| − | In order to keep custom image listings | + | In order to keep custom image listings 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. |
| + | |||
| + | ====Permissions==== | ||
| + | Once a custom image is added to the service, permissions will be reset on it so that only members of the unit's "Allow RIS" group will be permitted to use the image. If additional permissions need to be assigned to the image, contact the WDS administrators. | ||
===Staging Area=== | ===Staging Area=== | ||
Revision as of 16:03, 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 Images
Allowances
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.
Naming
In order to keep custom image listings 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.
Permissions
Once a custom image is added to the service, permissions will be reset on it so that only members of the unit's "Allow RIS" group will be permitted to use the image. If additional permissions need to be assigned to the image, contact the WDS administrators.
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.