Migration for WDS 2003\Legacy to WDS 2008 Native, XP cant join domain or get computer name

Posted on 2009-07-02
Last Modified: 2012-05-07
Ok here is my senario.
Had a 2003 WDS setup running in legacy mode (RIS).
Images that were installed on Clients, came down, joined domain with a computer name dictated by the "Directory Servies" tab in WDS.

so the computer name woud be username##
it would also put the newly installed computer account into a specific OU (also in the same tab)

took all the old images, converted them to .WIM's and imported them as install images on the 2008 server runing WDS

now the converted images, still do what they are suppose to. The Directory services tab is the same on 2008 as on the old 2003 server.
However on newly created images, using th wdsutil, they do not get the name formating specified, they do not join the domain, and if you manually join the domain, they do not go to the OU specified.

now alot of this can be put (somewhat) in the sysprep.inf, however it is not in the sysprep.inf on the old images.
I have even tryed to replace the whole sysprep.inf of a working install with the failing one with no luck.

So there has to be something else in the old RIS (rpi\reped) images that is not in the WDS images.
There is something in WDS that tells the clients to join the domain, and create the computer account, however i cannot find it.

more information, in the old images, during the new WDS setup after the expansion of files and before the first reboot the computer account is created in AD, but i have not idea what is creating this, is it WDS, is it in the old RIS image?
any one have any ideas?
Question by:prelude812
  • 2

Accepted Solution

prelude812 earned 0 total points
ID: 24797833
found the issue.
needed to create a sysprep.inf in \\servername\remoteinstall\images\windows xp\image name\$OEM$\$1\sysprep\

even though i had done this it ws missing the

Author Comment

ID: 24798288
in case any one wants an example here is my sysprep
located here
\\server\REMINST\Images\Windows XP\760v2\$OEM$\$1\sysprep














    OrgName="my company"









DoOldStyleDomainJoin = Yes

MachineObjectOU= "OU=some OU, dc=domain, dc=domain, dc=com"




Open in new window


Featured Post

Why are Office 365 signatures so complicated?

Trying to setup transport rules for Office 365 email signatures and can’t quite figure it out? Having to test the signature over and over? Make things simple by using Exclaimer Cloud - Signatures for Office 365.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Issue: Unstable cursor in Windows XP and Windows runs extremely slow in that any click will bring up the Hour glass (sometimes for several seconds before giving you what you want) . Troubleshooting Process and the FINAL FIX: This issue see…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

25 Experts available now in Live!

Get 1:1 Help Now