Migrating RAS on from an NT4 domain to 2003 AD

  • Thread starter Thread starter john
  • Start date Start date
J

john

Hi,

I am curently planning the following:


1. Migration from an NT4 Server environment to AD on 2003 Server.
2. Migrating from NT4 Exchange 5.5 to 2003 Server running Exchange 12.
3. Migrating a NT4 RAS server to 2003 Server.


Our current setup is as follows:


Type Primary Use Secondary Use


NT 4.0 Primary DNS Webserver
NT 5.0 Database - Tims PMS Head office
NT 4.0 SQL - Sun
NT 4.0 SQL - Sun
NT 5.2 MSDE SQL 2000 Centennial
NT 5.2 SQL Cube - Film
NT 5.0 Proxy Server SPAM/Email - Surf Control Email & Web filtering



NT 5.0 Coda Accounts BACS
NT 5.0 SQL Cube for product consessions
NT 5.0 Blackberry Server MSDE SQL 2000
NT 5.0 Purple - Film booking information, credit cards. VB
Development
folders
NT 4.0 Exchange 5.5
NT 4.0 BDC DNS RAS
NT 4.0 Phone switch management Voicemails
NT 5.2 DHCP Server FileServer
NT 4.0 PDC
NT 5.0 Contains old files from CineUK


What I am intending to do is have all of these servers in AD, the
current PDC will be upgraded to 2003 with AD.


The NT4 Server running Exchange 5.5 is due to be upgraded to a 2003
Server running Exchange 12.


The RAS server is due to be upgraded to windows 2003 Server.


As you can see this required a vast amount of planning, I have done
quite a few migrations before, I have never however done a migration
this complex which also includes a RAS server.


For Step 1.....

I have posted this on the migration board



For Step 2.....


I will post this to the exchange board.


For Step 3.....


I have read various articles and Microsoft white papers but the
solution and possible workarounds are unclear.


Many have sugested migrating to 2000 server first and using the
migration tool to aid in the transition to 2003. As the migration
involves RAS to RRAS to Routing and remote access, this particular
migration seems to be more involved than previous migrations I have
completed.


Many thanks in advance.
 
Just be aware of the following issues.
1. You may have a name resolution or connectivity issue if you enable RRAS on a DC with DNS.
2. The VPN may not work if you migrate RRAS from NT 4 to 2003. It is better just re-do the RRAS.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi,

I am curently planning the following:


1. Migration from an NT4 Server environment to AD on 2003 Server.
2. Migrating from NT4 Exchange 5.5 to 2003 Server running Exchange 12.
3. Migrating a NT4 RAS server to 2003 Server.


Our current setup is as follows:


Type Primary Use Secondary Use


NT 4.0 Primary DNS Webserver
NT 5.0 Database - Tims PMS Head office
NT 4.0 SQL - Sun
NT 4.0 SQL - Sun
NT 5.2 MSDE SQL 2000 Centennial
NT 5.2 SQL Cube - Film
NT 5.0 Proxy Server SPAM/Email - Surf Control Email & Web filtering



NT 5.0 Coda Accounts BACS
NT 5.0 SQL Cube for product consessions
NT 5.0 Blackberry Server MSDE SQL 2000
NT 5.0 Purple - Film booking information, credit cards. VB
Development
folders
NT 4.0 Exchange 5.5
NT 4.0 BDC DNS RAS
NT 4.0 Phone switch management Voicemails
NT 5.2 DHCP Server FileServer
NT 4.0 PDC
NT 5.0 Contains old files from CineUK


What I am intending to do is have all of these servers in AD, the
current PDC will be upgraded to 2003 with AD.


The NT4 Server running Exchange 5.5 is due to be upgraded to a 2003
Server running Exchange 12.


The RAS server is due to be upgraded to windows 2003 Server.


As you can see this required a vast amount of planning, I have done
quite a few migrations before, I have never however done a migration
this complex which also includes a RAS server.


For Step 1.....

I have posted this on the migration board



For Step 2.....


I will post this to the exchange board.


For Step 3.....


I have read various articles and Microsoft white papers but the
solution and possible workarounds are unclear.


Many have sugested migrating to 2000 server first and using the
migration tool to aid in the transition to 2003. As the migration
involves RAS to RRAS to Routing and remote access, this particular
migration seems to be more involved than previous migrations I have
completed.


Many thanks in advance.
 
Thanks for the reply.

Just thought that there would be an easier way of doing things.

Kind regards
 
Back
Top