I had to Configure (not install, just configure the already installed wds service) 121 servers and i couldn’t find a script handy so had to put one together,
here’s the result, create a blank text file called computerlist.txt with a list of your servers computernames in this format
computername1
computername2
computername3
computername4
etc…
save the file to c:\scripts
using psexec (available from here), execute the following line in c:\scripts and change the D:\RemoteInstall folder to the folder that you have installed WDS on.
C:\scripts>psexec -s -n 60 @C:\scripts\computerlist.txt c:\windows\system32\cmd
exe /c “IF EXIST D:\RemoteInstall wdsutil /verbose /progress /initialize-server
/reminst:”D:\RemoteInstall” > c:\wds_setup.log”
the results will look similar to this
Starting c:\windows\system32\cmd.exe on computername1…
c:\windows\system32\cmd.exe exited on computername1 with error code 0.
Starting c:\windows\system32\cmd.exe on computername2…
c:\windows\system32\cmd.exe exited on computername2 with error code 0.
Starting c:\windows\system32\cmd.exe on computername3…
c:\windows\system32\cmd.exe exited on computername3 with error code -1056767739.
Starting c:\windows\system32\cmd.exe on computername4…
c:\windows\system32\cmd.exe exited on computername4 with error code 110.
but what do the results mean,
an Error code of 0 means that it has successfully configured the WDS service,or that it didn’t find the RemoteInstall folder on the specified drive, so didn’t do anything
an error code of -1056767739 means the WDS was already configured on the server
an error code of 110 means that you should check that WDS server (it’s configured but has another problem..)
tested this fine on 121 Windows 2003 sp2 servers with WDS preinstalled, for your convenience a wds_setup.log file is left on c:\
That log file will contain text similar to the following if the configuration was successful:-
Windows Deployment Services Management Utility [Version 6.0.6000.16386]
Copyright (C) Microsoft Corporation. All rights reserved.
Setting up server…
-> Creating Windows Deployment Services installation tree
—> Creating Windows Deployment Services installation root at \\computer1.windows.noob.local\D$\RemoteInstall
—> Creating Windows Deployment Services share at \\computer1.windows.noob.local\REMINST
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Images
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Boot
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Boot\x86\Images
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Boot\ia64\Images
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Boot\x64\Images
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Boot\Fonts
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Tmp
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Mgmt
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\WdsClientUnattend
—> Creating Windows Deployment Services folder \\computer1.windows.noob.local\REMINST\Templates
-> Installing Windows Deployment Services files
—> Installing system files
.
—> Installing boot files for x86
….
—> Installing boot files for ia64
..
—> Installing boot files for x64
..
-> Updating registry
-> Configuring the TFTPD service
-> Configuring BINL SCP
Enabling Windows Deployment Services services…
Starting Windows Deployment Services services…
The command completed successfully.
and if WDS is already configured, will contain:-
Windows Deployment Services Management Utility [Version 6.0.6000.16386]
Copyright (C) Microsoft Corporation. All rights reserved.
Setting up server…
An error occurred while trying to execute the command.
Error Code: 0xC1030105
Error Description: Windows Deployment Services initial setup has already been completed on the server.
cheers
niall