Windows Server 2008 Thread, adding a server 2008 dc to a 2003 domain in Technical; Originally Posted by irsprint
I would just run it in 2003 mode, from what I remember
You still need to ...
22nd May 2009, 10:17 PM #16
You still need to do AD prep
Originally Posted by irsprint
Yep you can. I did have a mix running for a few weeks.
Originally Posted by cookie_monster
22nd May 2009, 11:03 PM #17
This is almost correct. You need to update your existing 2003 PDC Schema first, before adding any 2008 server to your domain. Server 2003 is Schema 30 and Server 2003 R2 is Schema 31. 2008 Server is Schema 44, so quite a big difference.
1.install server 2008
2.run the following commands on my 2 2003 dc's
adprep /domainprep /gprep
3.run through dcpromo on my 2008 dc
4.get a cup or coffee and enjoy my success
If you don't do it this way round, you'll get lots of errors as the Schemas will be different versions.
- Take a full backup (including System State) of your existing 2003 PDC
- Update existing 2003 PDC Schema to 44. You aren't required to do this on any other domain controller
- Join the 2008 Server to the domain
- Promote 2008 Server as a domain controller, including DNS
- Either migrate DHCP or create a secondary DHCP Server for redundancy
- Force Replication through Sites and Services manually
- Migrate all FSMO roles
- Force Replication again through Sites and Services manually
- Either leave the 2003 Server as a BDC, or demote it to a member server
- Get a cup of coffee and enjoy your success
Will you have any downtime? Not much if done properly, however you will require reboots to join the 2008 Server to the domain and promote it to a DC; you'll also need to reboot your 2003 Server, if you decide to demote it to a member server.
28th May 2009, 12:42 PM #18
- Rep Power
oh dear this is confusing but i'm getting there
how do i Force Replication through Sites and Services manually? just a dos command i'm guessing or a button.
other than that step i think i'm ready to give this whole process a go
1st June 2009, 08:53 AM #19
- Rep Power
1st June 2009, 08:59 AM #20
Did the schema updates take seconds as anticipated?
1st June 2009, 09:02 AM #21
- Rep Power
the forestprep took quite a long time (well 30 minutes) but the others only took a few minutes. In the end the whole process was very easy and actually quite quick.
27th August 2009, 01:10 PM #22
Thanks for this, I will be doing this at some point.
Just wondering whether to go with 2008 or 2008 R2 now.
I'm guessing we need those DC's to be able to run windows 7 properly as clients.
27th August 2009, 02:09 PM #23
If you want my opinion, hold off from 2008 R2 until at least early next year. There are lots of reports of 'quirks' with it, but I'm sure in time these will be ironed out.
A good example of this is WSUS 3.0 SP2 (which has or is going to be released) to make it compatible with 2008 R2.
28th August 2009, 10:46 AM #24
There's bound to be problems with third party software when using software that has just gone RTM I think it's good advice to wait for a while and let MS iron out these issues, I think i'll stick with 2008 for now having seen the number of issues reported here.
30th August 2009, 06:34 PM #25
We have just introduced two 2008 R2 DC's to our previous 2k domain. Our schema went from a level of 13 to 47! Rather substantial upgrade.
Have had no problems so far and are nearly at the point where we can demote our 4 2k DC's.
The only server we won't be running R2 on is our support server, exchange and ISA. Our support server will be running SCCM, ePo4, helpdesk etc... so want to avoid incompatibilities that will inevitably be there, especially with WSUS.
But not had any problems with R2 as of yet. Fingers crossed.
Just out of interest, has anyone had any problems with CMIS on R2? Or indeed SQL 2008? We had some feedback saying to avoid sql 2008 as there are still some quirks that should be avoided...
30th August 2009, 06:42 PM #26
I have asked the question of Serco about 2008 R2 Support, they support 2008 but I said they should look into R2 especially the SSO stuff as that seems to be a common thing that is failing with other items that use the DCs. So I am awaiting hearing back from Serco. I am not rushing to 2008 R2 for my Serco box, it can stay on 2003 for now. So long as its 2008 R2 supported by summer next year when I replace the box (unless I bring that forth to help some of our issues....)
30th August 2009, 06:56 PM #27
Could you not just move that box to 2008 john? What's the need for R2 on the Serco box?
30th August 2009, 07:42 PM #28
I want them all to match in the end
Originally Posted by cookie_monster
31st August 2009, 04:25 AM #29
- Rep Power
Re: adding a server 2008 dc to a 2003 domain
These steps are pretty much what we have just done, from 2000 to 2008 R2, and it went OK. What caught us out was having WINS on our old PDC, and when we turned the old PDC off, a few things went wrong (some legacy stuff on the network that needs WINS obviously - will be working hard to iron that out...) We fixed this temporarily by putting WINS on the new 2008 R2 box and migrating the database across. We also had a strange DNS issue with alias (CName) records to certain servers as well, where you could ping the servers and map a drive to the real server name, but not to the alias name. Only some servers were affected. I'm thinking WINS again but we worked around it. The other things I'd add to this list is to watch where your logon scripts are being run from (if they are in the default AD location that is fine as they are replicated, but if they are running from a share on your old DC, obviously they will stop working!) and just to do a really good analysis of your old server(s), looking for those little gotchas that someone else might have setup years ago, before you turn them off. We had lots of disconnecting the network cable of the old server and then plugging it back in again when little things stopped working. No disruption to the network really, other than the DNS issues etc.
Originally Posted by Michael
31st August 2009, 11:25 AM #30
Generally (as a recommendation) you should join a new server to the domain and then promote it to a domain controller. At this point you should make sure DNS is correct. The server should point to itself first, then a secondary DNS server, then external DNS servers.
You also need to add it to DHCP Server so machines know where to look when you migrate FSMO roles. In doing this you should receive no DNS errors whatsoever.
Any reason why you wouldn't run login scripts from within NETLOGON? If you stored scripts within a share, what were you using NETLOGON for (if anything)?
By reggiep in forum Windows Server 2000/2003
Last Post: 6th May 2009, 09:47 AM
By Jobos in forum Windows Server 2000/2003
Last Post: 11th December 2008, 04:51 PM
By broyles in forum Windows Server 2008
Last Post: 10th April 2008, 03:58 PM
Last Post: 3rd August 2007, 05:37 PM
By dezt in forum Wireless Networks
Last Post: 13th July 2007, 10:09 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)