Upgrading Server2000 DC to Server2003 R2 – best method 1

[tookawhile]

I have 1 PDC running Srv2k in native mode (only have XP clients) with around 20 users, very simple AD structure – the hardware is old and now have a new server to eventually replace it – the new server runs Server 2003 R2.

I want to know the best way of integrating the new server whilst leaving the old PDC running, so the way I had in mind was to remove all the clients from the domain (small office – around 20 clients) then demote the old Win2k server to a member server only, then plug in the new Server2003 in and promote it to be the new DC – I will add a backup DC later. Will this work out Ok?

I have been trying out the new server on a separate subnet so it is running as a DC at the moment – also not physically connected to the same network at the moment.

 

[nsglists]

Davetoo,
This question might sound stupid after all these posts,
(1) Should I run adprep on the existing SP1 DC servers using the R2 CD OR
--> If I understand you correctly, this is what I should do first!!
(2) Should I run adprep on the new R2 server so that it can be made DC OR
--> again, if I understand you correctly, then I dont have to do this as the AD schema for the R2 server is already prepared!!!
(3) both in a particular order.
--> dont have to!!

Also, I understand what I confused myself with. For some reason, I thought running adprep on SP1 DC server was akin to upgrading SP1 to R2.... I now understand that all it does is adds object to the AD schema!!

Kindly confirm.
Thanks a bunch for everything.

 

[hellboy101]

Hello-

This is just a general question if I may be so bold.. I am comtemplating researching this topic but since you are all discussing this....

What are the overall differences and/or enhancments between Win 2k3 server and Win 2k3 R2 server? just gui bells and whistles or are has Microsoft added an entire class of new features pertaining to R2. Thanks for any guidance at all..

hb101

 

[nsglists]

hellboy,
check the links for some basics,

http://www.microsoft.com/windowsserver2003/R2/R2FAQ.mspx

http://www.windowsitpro.com/Article/ArticleID/46609/46609.html?Ad=1

Thanks.

 

[tookawhile]

Just noticed something on the new W2003 (still set-up as a test rig) - its functional leverl is at Windows 2000 native, so after following the instructions for adprep/foresprep et al, do I then raise the functional level on the new W2003 to Windows Srv 2003? Assuming I no longer want to use the old DC in any way.

At a later date, could I then add back the W2000 Srv a just a member server?

Again, with regards to the W2003 Srv, if I use the 'Add/Remove' roles wizard and remove all current roles - is the same as running dcpromo?

 

[nsglists]

Could anyone kindly confirm one more things. In a AD environment which has both SP1 and R2 DCs, is it a must that the R2 DC holds all the roles.
Please advice.
Thanks.

 

[binh817]

NOPE R2 doesn't necessary need to hold all the roles

 

[58sniper]

But it's a good idea to upgrade the DCs to R2 so that they may all use the R2 features.

I noticed that one of Davetoo's original replies mentioned seizing the FSMO roles. Careful on the wording. If both DCs are up and running, your TRANSFERRING, not SEIZING. Big difference. The kb article that is linked is the correct one for TRANSFERRING.

Pat Richard, MCSE MCSA:Messaging CNA
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[nsglists]

Thanks for the great advice. This thread has been a wonderful experience for me.

Thanks a bunch again for all the great advice. This has been a great learning experience.

The AD setup went well.
I did one stupid thing though without realizing it. Nothing 's wrong, but I am just trying to understand the consequence.

After dcpromo'ing R2 as a DC, I was trying to setup DNS. Without realizing, I tried to set it up as a primary zone for the domain. Now the DNS on SP1 server was also setup as the primary zone for the domain. It actually went through but later it said that a zone already exits, but it created a copy of the all the DNS recods on the R2 server.

Now, I realize I should have set it up the R2 DNS as the secondary zone, which would have acted as the secondary zone. But I am curious here,
- Does having a copy of the primary zone on the R2 not resolve queries ?
- What is the difference between having a secondary zone on the R2 and having a secondary zone for the dns on the R2.

Also, kindly correct me if I am muddling terms again here!!

Please advice.

 

[tookawhile]

I'm just try out the procedure, I have set-up another server with W2000+SP4 to mimic my current DC.

So, I've demoted my new W2003 R2 server and dis-joined from any domains.

I then used W2003 R2 on the mimic DC (W2000) and ran adprep /forestprep - which seemed to go ok and said it had completed.

I then try and run adprep /domainprep and get the following

'Forest-wide information needs to be updated before the domain-wide information c
an be updated.
[User Action]
Log on to the schema master malvern-srv1.aurix.com for this forest, run the foll
owing command from the installation media to complete the forest update first:
adprep.exe /forestprep
and then rerun adprep.exe /domainprep on infrastructure master again.'

I've already ran forestprep successfully, so why this message?

This happens everytime I try and run adprep /domainprep

 

[nsglists]

Going ahead, I was trying to setup a print server on the AD. The following was a good link for the same,

http://www.microsoft.com/windowsserver2003/technologies/print/default.mspx

I presently have the print server running on a Win2K non-DC server. I backed up the config using the print migrator. I might not actually restore from this cab file on the new print server on the 2003 machine as I will install newer drivers for the printers.

I installed print management on 2003 and added a few printers. I guess I can publish the printers in AD and the AD clients would find them automatically.

But there are some machines which will not be part of the domain and need access to the printers. In 2000 these clients would simply browse to a URL on the print server and connect to the printers. I am not sure how to setup the same in 2003 AD. So,
- how do I setup the print server the same way as I have in 2000 so that non AD clients can browse the printers on the print server and choose to install them as they want?
- how can the clients find the printers on the print server if they are not published in AD?
- how do I set it up on a separate network interface and IP, so that all print requests would go only to that IP for print requests?

Please advice.
Thanks.

 

[Davetoo]

58sniper is correct, I mis-used the term "seizing"..if the DC is still accessible, you simple move the FSMO roles from it to another server. You only have to seize the roles if a server is non-responsive to the domain.

nsglists - I highly recommend you pickup some books on W2K3 server and start reading. MS Press provides a good starting point.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215

 

[tookawhile]

One last question.

Assuming I've run adprep /forest and domain on my current W2000 srv, I then DCPROMO the new W2003 srv - do I have to run adprep /domain prep on the new W2003 srv before DCPROMO or do not run it all on the new W2003 srv?

 

[tookawhile]

Anybody?

I'm still unsure if I need a step between 2 and 3, running adprep /domain on the new DC before DCpromo.

Currently doing this:

1. On current DC (- Win2k srv), insert 2nd CD from the Server2003 R2 set-up CDs.
2. On current DC (- Win2k srv), run adprep/forestprep from the Server2003 R2 CD (D:\COMPONENTS\R2\ADPREP) - adprep/domainprep prepares schema to accept the 2003R2 DC
3. Join the 2003R2 to domain and then dcpromo it – can take a while, leave overnight
4. Transfer the FSMO roles from existing DC over to the new 2003R2 one – see

http://support.microsoft.com/kb/255690/

5. Esure that the 2003R2 is running any services that the old server was handling (DHCP, DNS, WINS, etc.)
6. Config DHCP scope, zone, NTP
7. dcpromo the old server to remove it as a DC – unplug NIC or demote to a member server.

 

[Davetoo]

Your steps are accurate. You do not run adprep on the 2003R2 server, you run it on the 2000 server using the 2003R2 2nd CD.

You have all the information you need, now go do it.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
The poster formerly known as lander215

 

[tookawhile]

See you on the other side....hopefully..and thanks for your help Davetoo