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.
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 (also known as Cross-VLAN PXE booting to WDS)
- Creating Bootable Discover CDs
Base images are install images that are supported by the WDS administrators; they contain only a Windows installation and no other programs. It is recommended that WDS users begin making custom images from one of these base install images.
Not all base images will be displayed by default to WDS users. A number of infrequently-used images have been designated to be hidden from view by default, and users who want to make use of one of those base images will be required to request it be added to their image listing by contacting firstname.lastname@example.org.
The following images are base images. Entries shown in italics will be hidden from view by default, and entries with an asterisk (*) are configured for periodic updates to current Windows Update patch levels:
- Windows 2008 Server Enterprise, x86
- Windows 2008 Server Enterprise NO Hyper-V, x86
- Windows Server 2008 R2 Enterprise, x64*
- Windows Server 2008 R2 Enterprise No Domain Join, x64*
- Windows Server 2008 R2 Enterprise Core, x64*
- Windows Server 2008 R2 Datacenter, x64*
- Windows Server 2008 R2 Datacenter Core, x64*
- Windows Server 2012 Datacenter, x64
- Windows Server 2012 Datacenter Core, x64
- Windows Server 2012 Standard, x64
- Windows Server 2012 Standard Core, x64
- Windows Server 2012 R2 Datacenter, x64
- Windows Server 2012 R2 Datacenter Core, x64
- Windows Server 2012 R2 Standard, x64
- Windows Server 2012 R2 Standard Core, x64
- Windows 7 Enterprise, x86*
- Windows 7 Enterprise, x64*
- Windows 7 Enterprise No Domain Join, x64*
- Windows 7 Enterprise No Domain Join, x86*
- Windows 8 Enterprise, x86
- Windows 8 Enterprise, x64*
- Windows 8 Enterprise No Domain Join, x86
- Windows 8.1 Enterprise, x86
- Windows 8.1 Enterprise, x64
- Windows 8.1 Update 1 Enterprise, x86
- Windows 8.1 Update 1 Enterprise, x64
The image listing will be formatted to show any custom images available to the user first, followed by the base images (some of which may be hidden from view as noted in the Base Images section above), with any public images being available at the bottom of the list.
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.
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.
Once a custom image is added to the service, permissions will be automatically set on it so that only members of the unit’s “Allow Imaging” group will be permitted to use the image. If additional permissions need to be assigned to the image, contact the WDS administrators.
The staging area of the deployment DFS share (\\wolftech.ad.ncsu.edu\deployment\staging) shall contain, at minimum, the following subfolders:
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.