[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Moving Windows 2000 server Domain Controler to a new box with Server2003.

Posted on 2006-03-22
10
Medium Priority
?
323 Views
Last Modified: 2010-04-18
I just came into an environment where they are running Windows2000 Server(Domain Controller) on a PII.  I would like to decommission this box and replace it with a new Server2003 R2 box.  Any suggestions on what the best way to do this is?  The mnachine also runs DNS and DHCP.  I have done upgrades on 1 box but new moved to a new box and upgraded.

Thanks
0
Comment
Question by:bpopola
  • 4
  • 3
  • 3
10 Comments
 
LVL 9

Accepted Solution

by:
vsg375 earned 1000 total points
ID: 16257504
Hi,

Take a look at this question, I think it's the best way to proceed in your case.


http://www.experts-exchange.com/Operating_Systems/Q_21694951.html


Don't hesitate to post again if you need more information.

HTH
GL
Cheers
0
 

Author Comment

by:bpopola
ID: 16258279
great post.  Just  a question.  I would like to reneme the server 2003 box the same as the old 200 server.  I believe after the old box is turned off for good I can just rename?

Also How to update the schema on the 2000 box?
0
 
LVL 9

Expert Comment

by:vsg375
ID: 16258416
You can rename the DC after the old one is offline. Here's the procedure :

http://www.petri.co.il/windows_2003_domain_controller_rename.htm

the adprep /forestprep / domainprep takes care of updating the schema.

HTH
Cheers
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 

Assisted Solution

by:raybwf
raybwf earned 1000 total points
ID: 16260117
One little add on here. If you are going to promote your w2k3 standalone to a member server and then run the DCPROMO, keep in mind that you have to run ADPREP from the R2, DISK2 setup disk NOT disc1!!  ADPREP is also on disk 1 but you will fail when attempting make your win2k3-r2 box a Domain Controller. Unfortunately this isn't in the Msoft knowledgebase yet and I spent many pointless hours trying to upgrade a recent client of mine.

Good Luck!


Ray
0
 
LVL 9

Expert Comment

by:vsg375
ID: 16260233
good point Ray ! Having not done this for ages, I wasn't even aware of that one.

Cheers
0
 

Author Comment

by:bpopola
ID: 16275313
info looks great.  Will give it a shot this weekend.
0
 

Expert Comment

by:raybwf
ID: 16276047
Guys/Gals,

Just to follow up quickly, I was on the phone with Microsoft this morning regarding an issue I was having with exchange 2k3 not auth. with all my dc's. (I am not in a native environment). It appears that we were having issues because I only ran ADPEP on the primary operations master (win2k) and not on the other backup dc (which was win2k) also. Everything looked good initially because the win2k3 server got promoted without error. I only saw errors a few days after the fact. Anyhow - Good luck this weekend!
0
 

Author Comment

by:bpopola
ID: 16310090
All worked ok except the sysvol info did not copy over.  And ideas?
0
 

Author Comment

by:bpopola
ID: 16311745
I got.  a problem on the 2000 box.

On the 2000 box  I did the following
To change this registry parameter, run regedit. Click on Start, Run and
> type regedit. Expand HKEY_LOCAL_MACHINE.
> Click down the key path:
> "System\CurrentControlSet\Services\NtFrs\Parameters"
> Double click on the value name
> "Enable Journal Wrap Automatic Restore" and update to 1.
If not create new dword.  value 1
Restart the file rep service.  When done.  Change value back.

Went to the 2003 box and restarted the replication service.  
Now I get:
"The File Replication Service is no longer preventing the computer ITDS2 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL."
0
 

Expert Comment

by:raybwf
ID: 16313294
I had a similar problem with my upgrades as well. SYSVOL folders weren't automatically created on the new win2k3r2 box.  I went through a slew of things with Microsoft including runnign the GPOFIX utility and editing the registry Burflags set. Manually creating the SYSVOL folders and following the article below resolved my issue in particular. Check this out:

http://support.microsoft.com/kb/290762/en-us

Let us know how it goes
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
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…
Screencast - Getting to Know the Pipeline
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

834 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