Markus0815
MIS
Hi All,
we recently installed an additional Windows 2003 Domain Controller with slipstreamed Service Pack 2. Everything worked just fine until we tried to prestage a new client machine in AD for Client Rollout with WDS...
Creating a new computer object in AD presents the first dialog box for the computer name, user to join the computer and if to assign the account as pre-Windows 2000 Computer or backup domain controller - simply business as usual...
But instead of the 'Next' button guiding you to the next dialog box for the Computers GUID/UUID the slipstreamed SP2 version leaves you with a 'OK' button instead, creating an unmannaged account which cannot be found by WDS !!
However, using our 'old' Windows 2003 DC even with Service Pack 2 installed, there is no problem at all.
We have slipstreamed both a Windows 2003 Server as well as a Windows 2003 Server R2, both with same results.
/Markus
we recently installed an additional Windows 2003 Domain Controller with slipstreamed Service Pack 2. Everything worked just fine until we tried to prestage a new client machine in AD for Client Rollout with WDS...
Creating a new computer object in AD presents the first dialog box for the computer name, user to join the computer and if to assign the account as pre-Windows 2000 Computer or backup domain controller - simply business as usual...
But instead of the 'Next' button guiding you to the next dialog box for the Computers GUID/UUID the slipstreamed SP2 version leaves you with a 'OK' button instead, creating an unmannaged account which cannot be found by WDS !!
However, using our 'old' Windows 2003 DC even with Service Pack 2 installed, there is no problem at all.
We have slipstreamed both a Windows 2003 Server as well as a Windows 2003 Server R2, both with same results.
/Markus
