Difference between revisions of "Active Directory/Documentation/WDS/Management"

From WolfTech
Jump to navigation Jump to search
m (Intro text)
(Custom Image Allowance & Custom Image Naming Policies)
Line 1: Line 1:
 
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.
 
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]]
 
*[[../Using WDS with WolfPrep|Using WDS with WolfPrep]]
 
*[[../WDS_NICDrivers| Troubleshooting NIC Drivers]]
 
*[[../WDS_NICDrivers| Troubleshooting NIC Drivers]]
Line 12: Line 13:
 
*[[/Images|Image Management]]
 
*[[/Images|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 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.
 +
 +
==Other==
 
These external links may be helpful as references.
 
These external links may be helpful as references.
 
*[http://blogs.msdn.com/winre/archive/2006/12/12/creating-winre-using-waik.aspx Create WinRE Image]
 
*[http://blogs.msdn.com/winre/archive/2006/12/12/creating-winre-using-waik.aspx Create WinRE Image]
 
*[http://social.technet.microsoft.com/forums/en-US/winserversetup/threads/ Longhorn Server Deployment Technet Forum]
 
*[http://social.technet.microsoft.com/forums/en-US/winserversetup/threads/ Longhorn Server Deployment Technet Forum]
 
*[http://social.technet.microsoft.com/forums/en-US/itprovistadeployment/threads/ Vista Deployment Technet Forum]
 
*[http://social.technet.microsoft.com/forums/en-US/itprovistadeployment/threads/ Vista Deployment Technet Forum]

Revision as of 15:39, 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 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.

Other

These external links may be helpful as references.