Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?



"markm75g" wrote:



"Meinolf Weber [MVP-DS]" wrote:

Hello markm75g,

Personally i always use the way of fresh install where possible. Standard
2003 to enterprise 2008 you can upgrade. http://support.microsoft.com/?kbid=951041

Running DC's only as VM's is a not recommended way. you should have at least
one physical machine which helds all the 5 FSMO roles and is also GC/DNS
server.

Yes your order will remove the complete domain and configuration of user
accounts, computer accounts policies etc., because you demote the complete
DC's before promoting the new 2008 to DC.

Exchange 2007 will work in the 2008 domain on a 2003 server.

When no older OS DC exists then you can raise the functional levels to 2008
and then you can NOT have any earlier OS DC anymore.

See here about a way:

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon from the run line or repadmin /showrepl, dcdiag and netdiag
from the command prompt on the old machine to check for errors, if you have
some post the complete output from the command here or solve them first.
For this tools you have to install the support\tools\suptools.msi from the
2003 installation disk.

- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2003 schema master, with an account
that is member of the Schema admins, to upgrade the schema to the new version
(44), you can check the version with "schupgr" in a command prompt.

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only

- run dcpromo and follow the wizard to add the 2008 server to an existing
domain, make it also Global catalog.

- if you are prompted for DNS configuration choose Yes. If not, install DNS
role after promotion.

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on
both domain controllers

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
applies also for 2008)

- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2008 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database for 2008 choose "netshell dhcp backup"
and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/library/cc772372.aspx)



Demoting the old DC

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever

- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm




Thanks for that detailed response..

I had already begun the inplace upgrade...

I had issues with my one domain controller, so i had to seize all 5 roles
onto the other DC VM ( i see your notes on how i should use a dedicated
machine with all 5 roles, ill be moving to this shortly, I was trying to
avoid that, as i have/will have two hyper-v barebones servers)..

So i seized the roles, i then demoted the main DC back to member server.. I
ran the adpreps with the exception of the one you listed (adprep /rodcprep)..
This worked fine.. I then tried the 2008 upgrade, it rolled along until at
one point it "froze" on 59% copying files.. I restarted and it reverted this
(only) VM DC back to 2003..

Now I tried running adprep /rodcprep and received some errors, i wont list
them just yet... i did a dcdiag /fix.. i'm receiving this error:

testing server VSDC02 (this only remaining DC).. test connectivity...

The host 9adff94e-xxxxxx-xxx-x-xxx._msdcs.domain.local could not be resolved
to an ip address.. it goes on to say the although the guid dns couldnt be
resolved its ip address 100.15 was pingable.

This remaining DC was one of the two boxes with DNS installed.. the old dns
(DC) which was demoted still has DNS installed on it (and is now upgraded to
2008)..

If i connect to that dns server, it connects but there is nothing in forward
lookup zones..

I think i have a dns mess going on..




I ran a netdiag /fix and it corrected the one issue, i removed the entry in
the tcp ip settings that had the primary DNS going to the old DC/dns..

I then ran dcdiag again.. this time it passed on that one, but failed on a
bunch of tests under systemlog

some eventids included 0x00000416 (dhcp/binl service on local machine)..
eventid 0xc0001b6e (event string could not be retrieved).. eventid
0xc25a001d same event string error.. etc..

I do have the (only dhpc) on the other former DC (now with 2008 server
again).. this box used to host dhcp in a split fashion, but i went to a
single dhcp mode a while ago and unauthorized this vsdc02 machine, which is
the one i'm trying to upgrade to 2008..
.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • Re: Login issues for Active Directory Users. Unsure of root cause
    ... Every computer, including the server, ... the DNS or DHCP set up wizard. ... I've created enough bugs on the present install that it may not be ...
    (microsoft.public.windows.server.active_directory)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... All you need to do is make sure there are no other DHCP servers running on ... The only time I have seen the connectcomputer error you mentioned about DNS ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
Loading