Impact of moving FSMO's to different site?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

We have moved our production Datacenter to an office building an hour away
and it was designated by our management to be our production Datacenter. I
created a site in AD for this, and because we have fibre loop and very fast
connectivity, I gave it the minimum replication time of 15 minutes between
office HQ (where the FSMO's currently are) and the DataCenter. I was
wondering, what are the issues to consider with moving the FSMO role holders
to a different site. The officeHQ site was the first site, will it be a
problem to move the FSMO's to a new site?
 
Hello,

if you have a LAN-like speed on the network between the two sites I wouldn't
even split it up in two sites.

Apart from that you shouldn't have any issues to move FSMOs to another site.
 
Hello,

Just wondering, if the transfer is only going to be for 24 hours (management
decided only for this weekend due to an electrical outage), will it present
a problem to not change the time server? or should it be done immediately?
Will it cause problems?


Jorge_de_Almeida_Pinto said:
Hello,

We have moved our production Datacenter to an office building
an hour away
and it was designated by our management to be our production
Datacenter. I
created a site in AD for this, and because we have fibre loop
and very fast
connectivity, I gave it the minimum replication time of 15
minutes between
office HQ (where the FSMO's currently are) and the DataCenter.
I was
wondering, what are the issues to consider with moving the
FSMO role holders
to a different site. The officeHQ site was the first site,
will it be a
problem to move the FSMO's to a new site?

For information on transfering or seizing FSMO roles see:
http://support.microsoft.com/default.aspx?kbid=324801&product=winsvr2003
http://support.microsoft.com/kb/255504
http://www.petri.co.il/transferring_fsmo_roles.htm
http://www.petri.co.il/seizing_fsmo_roles.htm

For the AD site link between the fast connected sites you also enable
change notification on the site link. This way the intersite
replication between sites that use that site link looks like it is
intrasite replication
For more info see:
http://myitforum.techtarget.com/blog/tmintner/archive/2005/10/11/15742.aspx

The moving of the FSMO role holders will not present any specific
problems. The change of configuration still needs to replicate to
other DCs in the forest/domain.
There is one FSMO role however you might need to reconfigure! If it is
the PDC FSMO of the forest root domain you are moving you need to
reconfigure the NEW FSMO role owner DC with an external time source
and reconfigure the OLD FSMO role owner DC to use the domain hierarchy
On the old FSMO role owner DC run:
--> NET TIME /QUERYSNTP
Configure the new FSMO role owner DC with
--> NET TIME /SETSNTP[:ntp server list]
or --> W32tm /config /manualpeerlist:â?<time server 1> <time server
2> <time server n>â? /syncfromflags:manual

To update the â?oWindows Time Serviceâ? configuration:
--> W32tm /config /update
OR
--> Net stop w32time & net start w32time

To resync time:
--> W32tm /resync

To clear the NTP configuration on the old PDC
--> NET TIME /SETSNTP

Fore more info
MS-KBQ816042_How to configure an authoritative time server in Windows
Server 2003

--
Posted using the http://www.windowsforumz.com interface, at author's
request
Articles individually checked for conformance to usenet standards
Topic URL:
http://www.windowsforumz.com/Impact-moving-FSMO-site-ftopict437952.html
Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.windowsforumz.com/eform.php?p=1475956
 
Back
Top