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
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

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

When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
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 …

696 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