Error message

Notice: Undefined index: localized_options in menu_navigation_links() (line 1861 of /net/council/home/www/drupal/includes/menu.inc).

Setting up Windows Deployment Services (WDM)

I set up Windows Deployment Services today to take away some of the pain of (re)installing an OS on a machine. It was amazingly easy for a M$ server service configuration!!

!!Server Setup

* Basic guidelines I'm following are here: [[http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx]]
* Installed the 'role' Windows Deployment Services
** Installed both optional services 'deployment server' and 'transport server' (approximate name) while installing the role
* Since we run a dedicated non-MS (bind9) DHCP server on a different machine I didn't have to do anything!
* Selected the option to 'Respond to all clients known and unknown' for the PXE boot response option
** Selected the additional check to 'Require administrative approval....'
** What this does is prevent me from having to manually enter the '''LONG''' GUID that is embedded somewhere in BIOS to enable a machine to install
** With this setting any machine that PXE boots will get the option to 'Boot windows setup' (or something to that effect), then they will have to wait for an Admin to go into the management interface for WDS and authorize and '''name''' the machine, which is useful as an override to accepting default names
* Accidentally cancelled the setup wizard
* Manual Setup As Follows
** Add group 'MATRIX' as a install group intended for on-domain machines
** Note: adding image after trying to copy disk contents to share didn't make M$ happy and failed, so..
** Added install image from Windows 7 Pro x32 disk in drive on diff machine, shared over network (sources/install.wim)
** Added install image from Windows 7 Pro x64 disk in drive on diff machine, shared over network (sources/install.wim)
** Added boot image from Windows 7 Pro x32 disk in drive on diff machine, shared over network (sources/boot.wim)
** Added boot image from Windows 7 Pro x64 disk in drive on diff machine, shared over network (sources/boot.wim)
* That's really it!!!!
* To further customize I set the following options in the 'Properties' of the WDM management server MMC
** On 'ADDS' tab I selected a customized OU in which to place the new machines so they get put where they will get the proper GPOs applied for the type of machine

!!Client Setup
* Client PXE boots
* If it gets a DHCP address on the subnet it will get the option to 'Boot windows setup' (or something to that effect)
* An Admin must then authorize and name the client

!!More
* There are options to specify specific boot images for types of architecture... I didn't have to use these
* There are probably various uses for the 'Install Groups' config in the WDS management MMC
* If you have DHCP on the same machine as the WDS server there are additional requirements to configure (doesn't seem too complicated, I just can't speak to them)
* As an alternative to requiring 'Administrative approval' to start the install someone mentioned only turning on (starting) the service when you are doing installs... seems useful, but it would prevent my use of the naming option
* Still have to configure silent installation

!!Troubleshooting
* I did already have a case where the system was 'authorized' inside WDM but then it blue-screened during install, upon subsequent attempts to boot the option to 'Press F12' was not given, To Fix
** I deleted the account that was created upon 'authorization' inside of Active Directory, this should be necessary but it was not enough to allow the option during PXE boot
** Next I followed the steps described here: http://social.technet.microsoft.com/Forums/en/winserversetup/thread/88f6... the key parts being:
*** Run WDSUTIL /stop-server to stop all services.
*** Create a Temporary folder in the \RemoteInstall\Mgmt folder.
*** Move all existing files in the Mgmt folder to the Temporary folder.
*** Run WDSUTIL /start-server to start all services.
** Essentially you're just deleting/resetting the configuration/authorization database for WDS, obviously this wipes previously authorized clients and records of installation, no it's not ideal, but once a machine is installed and running I had no need of the formal records in WDS
** Surely there's probably a more intuitive way, maybe inside the interface, but I couldn't find it
** Also, I was installing using WDS on a Xen domU 64-bit machine that I had booted into x32 during the setup phase then chose 64bit option for the actual installation media option to create this blue-screen scenario, so I don't want to jump the gun and blame M$ for this

=== Useful Links ===
* [[http://technet.microsoft.com/en-us/library/cc772106(WS.10).aspx http://technet.microsoft.com/en-us/library/cc772106(WS.10).aspx]] - WDS Technet Base for WDS
* [[http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx]] - amazingly short and sweet steps from MS
* http://blog.augustoalvarez.com.ar/2008/12/12/installing-and-configuring-... - another guide
* http://blog.augustoalvarez.com.ar/2008/12/12/installing-and-configuring-... - part 2
* http://blog.augustoalvarez.com.ar/2008/12/12/installing-and-configuring-... - part 3 includes silent and custom installs
* http://social.technet.microsoft.com/Forums/en/winserversetup/thread/88f6... - thread on resetting the authorization database if a machine is not allowing PXE 'press F12' boot option, may be useful in other situations