Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » AD Migration Scenarios
AD Migration Scenarios [message #161886] Thu, 08 October 2009 20:04 Go to next message
John  is currently offline John
Messages: 1125
Registered: July 2009
Senior Member
We need to migrate 2 old domains into a single trusted domain (different
forests - W2K3) soon. In anticipation of an IP address space change, our new
domain infrastructure and servers were configured with a new IP address
scheme. However, networking cannot support changing the IP addresses of the
computers in the timetable established for the migration of user and computer
objects into new domain.

At this point, it appears we're faced with the following options:

1) Migrate (ADMT) the user objects, and wait for the computer object
migration to coincide with the IP address change (maybe 1 month later). In
this case, as well as the next one, the PC's will be in a different vlan, and
have a different address space than the servers (DC's) in this domian. Is
that a big concern?

2) Migrate the user objects, and computer objects immediately after. For
this case, and the previous one, which should be the DNS server for the PC's
- the new DNS servers (reside in same domain) or the legacy DNS servers
(reside in same IP space)? What are the DNS implications for both options?

Case 2 above will be much preferred by management - the migration of all the
objects is the only way they'll be able to fully meet our committment. Are
either/both of these options ugly?

We'd even be open to changing the new domain servers back to the old IP
address scheme, if that is a creative, not clunky, solution (even though that
doesn't sound good). We're not looking to do anything crazy to 'declare
victory', but are trying to avoid a major 'black eye' that would come by
delaying the migration.
Thanks!
Re: AD Migration Scenarios [message #161914 is a reply to message #161886] Fri, 09 October 2009 01:50 Go to previous message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello John,

If i understand you correct, the main problem in the moment is the ip range
in use. So you can have multiple VLANs in use for a domain, no problem. You
have to make sure that all domain members can contact the domain DC/DNS servers
and of course that all DCs can replicate.

You can change ip addresses on the machines later on without any problem.
As long as no application or whatever network ressource relies on a specific
ip address there is no problem with change the ip range.

During ip change make sure to start with the DC/DNS servers and run ipconfig
/flushdns and ipconfig /registerdns after the change, additional run netdiag
/fix or restart the netlogon service or thejust reboot the complete server.
After change check in all DNS zones for the correct new entries, rund support
tools dcdiag, netdiag, repadmin and go on with all other servers and if they
are all working again do the workstations.

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


> We need to migrate 2 old domains into a single trusted domain
> (different forests - W2K3) soon. In anticipation of an IP address
> space change, our new domain infrastructure and servers were
> configured with a new IP address scheme. However, networking cannot
> support changing the IP addresses of the computers in the timetable
> established for the migration of user and computer objects into new
> domain.
>
> At this point, it appears we're faced with the following options:
>
> 1) Migrate (ADMT) the user objects, and wait for the computer object
> migration to coincide with the IP address change (maybe 1 month
> later). In this case, as well as the next one, the PC's will be in a
> different vlan, and have a different address space than the servers
> (DC's) in this domian. Is that a big concern?
>
> 2) Migrate the user objects, and computer objects immediately after.
> For this case, and the previous one, which should be the DNS server
> for the PC's - the new DNS servers (reside in same domain) or the
> legacy DNS servers (reside in same IP space)? What are the DNS
> implications for both options?
>
> Case 2 above will be much preferred by management - the migration of
> all the objects is the only way they'll be able to fully meet our
> committment. Are either/both of these options ugly?
>
> We'd even be open to changing the new domain servers back to the old
> IP
> address scheme, if that is a creative, not clunky, solution (even
> though that
> doesn't sound good). We're not looking to do anything crazy to
> 'declare
> victory', but are trying to avoid a major 'black eye' that would come
> by
> delaying the migration.
> Thanks!
Previous Topic:group policy does not refresh
Next Topic:ADAM 2008 (LDS) not replicating with ADAM v1 W2K3
Goto Forum:
  


Current Time: Thu Jan 18 20:51:09 MST 2018

Total time taken to generate the page: 0.02034 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software