Printable View
Hello, we are getting a complete new server with server 2008. Our current
2000 Server only does DHCP, Domain control and file sharing. Nothing fancy.
What are the steps to migrate from 2000 to 2008? I have seen a lot of
examples for going from 03 to 08 but none to go from 2000. This will be the
first time I personally have done a server migration but I've been working
with Windows Servers for a long time. Thanks!
According to your description, my understanding is that:
You want to migrate active directory database, DHCP service and File
sharing service from Windows Server 2000 box to Windows Server 2008 box
because of the replacement of hardware.
If I have any misunderstanding, please feel free to let me know.
Based on the experience, here is some information for your reference.
Analysis and Suggestions:
=======================
The general steps to migrate from Windows Server 2000 to Windows Server
2008 is almost the same as the steps to migrate from Windows Server 2003 to
Windows Server 2008.
Scenario:
Old server: Windows Server 2000 box
New server: Windows Server 2008 box
1. Verify that Windows 2000 SP4 have been installed on the old server and
Windows Server 2008 SP1 have been installed on the new server
Note: the domain functional level should be in Windows 2000 native mode for
the Windows 2000 domain.
2. Upgrade the Windows 2000 forest schema by running "adprep /forestprep"
command on old server
Note: you can copy the adprep folder from the Windows Server 2008
installation disc to the old server to run "adprep /forestprep".
The location is \source\adprep on the installation disc.
3. Upgrade the Windows 2000 domain schema by running "adprep /domainprep"
command on old server
4. Verify the new server's TCP/IP configuration has been pointed to
existing DNS server.
5. Add new server to existing Windows 2000 domain as a member server.
6. Run dcpromo on new server to promote it as an additional domain
controller in existing Windows 2000 domain, afterwards you may verify the
installation of Active Directory.
7. Enable Global Catalog on new server and manually Check Replication
Topology and afterwards manually trigger replication to synchronize Active
Directory database between 2 replica.
8. Disable Global Catalog on old server.
9. Use NTDSUTIL utility to transfer all the 5 FSMO roles from old server to
new server. You'd better transfer FSMO roles via GUI method instead of
using NTDSUTIL.
10. Install DNS component on new server and configure it as a new DNS
Server(Active Directory Integrated-Zone is preferred)
Note: all the DNS configuration need to be transferred from the existing
DNS Server.
11. Migrate DHCP service from Windows Server 2000 to Windows Server 2008
Please refer to:
How to move a DHCP database from a computer that is running Windows NT
Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
running Windows Server 2003
http://support.microsoft.com/default.aspx/kb/325473
(This should work on Windows Server 2008)
12. Migrate File Sharing service from
You can also use robocopy.exe from the Windows Server Resource kit to copy
the files and maintain NTFS permissions.
For the shares, the shares definitions and permissions are stored in the
following registry key on the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares
If you export out the whole key and import in the new server, and if you
have the files and folders in the same path as in the old server, then you
will retain all you shares and share permissions.
12. It's better to make the old DC offline for several days and check
whether everything works normally with the new server online. If so, you
may let the old DC online and run DCPROMO to demote it.
For more information, please refer to:
Identifying Your Windows Server 2008 Functional Level Upgrade
http://technet2.microsoft.com/window...03a77-d9ba-4a2
6-b756-eba5499f15581033.mspx?mfr=true
How To Install and Configure DNS Server in Windows Server 2003
http://support.microsoft.com/kb/814591/EN-US/
How To Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/kb/816101
Prepare the domain with adprep from the 2008 install disk, add the 2008 as
member server to the domain.
Make in DNS on the 2000 DC ADintegrated zones(if not already done), run dcpromo
on the new one, make it DNS server and let DNS replicate.
Then move the 5 FSMO roles to the new server, make it Global catalog server.
Reconfigure the clients to use the new server for DNS.
With robocopy from MS resource kit you can copy the files including the permissions
to the 2008 server.
I am glad that the information is helpful to you. If you have any question,
please welcome to the newsgroup again.
I am trying to do the same thing as Brenden, going from 2000 server to 2008 server. I got to step 7 and am having DNS Problems causing Active Directory to crash. Everytime I try and open active directory sites and services it crashes and says its a visual c++ runtime library error. Any suggestions? When running the previous steps 2008 allowed me to check the global catalog addition so I did.
Generally, we answer one issue per post in the newsgroup. In order to
concentrate fully on this new issue we ask that you post it as a separate
thread. That way each issue can receive full attention and make the thread
more clear for others' reference. Please open a new post for this issue and
we will be very glad to work with you there.
some great information above thankyou. i once replaced a windows 2000 sbs server with a new 2000 sbs server and had a nightmare of a time having to go round 40+ computers in the building dissjoining them from the previous server and rejoining them because somehow it creates some ID within the users profiles on a pc. this happened even though the new server was later given the same domain name and ip etc.
if i followed the outlined method above with putting a new server 2008 enterprise onto a network that has a single DC running 2000 sbs. will this problem come back arround and have to do this rejoining on each pc or will it be a swift migration.
I've never migrated a server but this article is very helpful. I want to run my 2000 server in parallel with the 2008 server so I can test out some things before I retire the 2000 DC. I would be the only person logging into the 2008 server.
So given that scenario, I'm not sure which steps I would not complete until I'm ready to "go live" with new DC.
Thanks for any suggestions you might have.
You just need to make sure you run your 2000 Serve through a SQL Server Upgrade Advisor to make sure no hidden surprises wait for you. Database will be upgrade as soon as you restore it; so just changing the compatibility level will be needed. Database users and their permissions will come over; server users no. So all the SQL Server logins will be recreated. But you will not have to recreate the database users; you can map them to new logins you create using "sp_change_users_login".Quote:
Originally Posted by bhellwege
Thanks for your comments but I'm not running SQL on these servers. They are domain controllers.
Mr Shen:
I've never migrated a server but this article is very helpful. I want to run my 2000 server in parallel with the 2008 server so I can test out some things before I retire the 2000 DC. I would be the only person logging into the 2008 server.
So given that scenario, I'm not sure which steps I would not complete until I'm ready to "go live" with new DC.
Thanks for any suggestions you might have.
If you really a little knowledge about migration of server, then you will determinately come to know about it when you read the and understand the above post. However i am still looking for a solution regarding your query. I ma not a professional but i hope that i will get it somewhere. When i get it i will post it back here.