Moving WDS to new server

Hi Experts,

I am in the process of moving my WDS from one server to another.  Both servers are server 2008 R2 64bit.  I have looked online and everywhere I find says to stop both servers and then copy the RemoteInstall directory from the old server to the new server.  The issue is when I do this it breaks the service and it won't start back up.

So my question is how do I move WDS from the old server to the new server?
Christian CoutureAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeff PerryWindows AdministratorCommented:
I haven't used WDS in a while so I looked it up and as you said the correct method is to copy oldreminst to newreminst.

Do you receive any details on the error for the failing wds service that might offer a clue to what is keeping it from working?
0
Christian CoutureAuthor Commented:
Here is the error:

Log Name:      Application
Source:        WDSServer
Date:          1/23/2014 1:52:14 PM
Event ID:      257
Task Category: WDSServer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.domain.com
Description:
An error occurred while trying to start the Windows Deployment Services server.
 
 Error Information: 0xFFFFFB4D

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="WDSServer" />
    <EventID Qualifiers="49409">257</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-23T18:52:14.000Z" />
    <EventRecordID>47781641</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xFFFFFB4D</Data>
  </EventData>
</Event>
0
Jeff PerryWindows AdministratorCommented:
I have looked at your error code and the suggested fix is as follows.

To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:

1.Click Start, click Run, type cmd, and then click OK.
2.At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
3.Move the WDS account to Active Directory in the new organizational unit.
4.To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

You may have to try different combinations. I would try running line 2 on the old server and line 4 on the new server.

As an alternative you could also just make sure the two servers are in the same OU if they are not.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Christian CoutureAuthor Commented:
Tried that solution doesn't work, if I delete the folders out of the remoteinstall folder and run the command it will put the folders back in and start up. But as soon as I put the folders from the other server it fails.  This is what it says:

C:\Windows\system32>wdsutil /initialize-server /reminst:C:\remoteinstall

Windows Deployment Services Management Utility [Version 6.0.6002.18005]
Copyright (C) Microsoft Corporation. All rights reserved.


An error occurred while trying to execute the command.
Error Code: 0x41D
Error Description: The service did not respond to the start or control request i
n a timely fashion.

The servers are both in the same OU
0
Jeff PerryWindows AdministratorCommented:
If you initialize the new server with blank folders.

Can you stop the service and populate the folders individually and then restart the service?

Does the user account starting the service have the correct permissions on the new or copied folders?
0
Christian CoutureAuthor Commented:
The server starts with blank folders, I am currently trying to move the folders over one by one and starting the server after each folder to maybe isolate which one is causing the issue.  Will update once I am done.

And yes the user starting the service is a domain admin.
0
Christian CoutureAuthor Commented:
So it seems that if I copy the folders over one by one and start and stop it after each folder they all copy over fine and the server starts.  But if I copy them over all together it doesn't start.  Very Weird!

Next step is to see now that I have everything transferred over if I can connect and create an image.  I will have to test that on Monday.  Will update after I try and image something from the new box.

Thanks so far for the input.
0
Christian CoutureAuthor Commented:
Ok just to update this and close this question.  It turns out that the server that WDS got moved to was only a windows 2008 SP2 server and not an 2008 R2 server.  Turns out that the versions of WDS are different between 2008 SP2 and server 2008 R2 which was the reason for the error.  I have moved it to a 2012 R2 server and it is now working.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Christian CoutureAuthor Commented:
Server versions were different causing the issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.