Solved

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

Posted on 2009-07-02
2
1,140 Views
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.
OR
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?
0
Comment
Question by:prelude812
[X]
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
2 Comments
 
LVL 5

Accepted Solution

by:
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
DoOldStyleDomainJoin
0
 
LVL 5

Author Comment

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


;SetupMgrTag
[Unattended]
OemSkipEula=Yes
 
 
[GuiUnattended]
    AdminPassword="password"
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    OEMDuplicatorstring=760v2
    TimeZone=20
    OemSkipWelcome=1
 
[UserData]
    ProductKey=12345-12345-12345-13245
    FullName="IT"
    OrgName="my company"
    ComputerName=%MACHINENAME%
 
[TapiLocation]
    CountryCode=1
    AreaCode=636
 
[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist
 
[Identification]
DoOldStyleDomainJoin = Yes    
JoinDomain=my.domain.name
MachineObjectOU= "OU=some OU, dc=domain, dc=domain, dc=com"
 
[Networking]
    InstallDefaultComponents=Yes
 
[sysprepcleanup]

Open in new window

0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

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

Suggested Solutions

If you have done a reformat of your hard drive and proceeded to do a successful Windows XP installation, you may notice that a choice between two operating systems when you start up the machine. Here is how to get rid of this: Click Start Clic…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

730 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