Re: AD Site Consolidation
- From: "Dean Wells \(MVP\)" <dwells@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 May 2008 16:29:06 -0400
Like Herb - Exchange isn't my thing ... here's a snippet from a
colleague re: your post -
"If Exchange is in the site they are collapsing the DCs to they are
good. If in both, they could have issues until Exchange figures out
that stuff has moved. I would shut down the exchange server during the
move, let it come up when everything has settled down so it can reread
the topology. Exchange will fail the domain NC connections pretty
easily to another site, the config connections don't want to fail out of
site to save its life. As soon as the DC stops responding to pings it
should fail over but I have seen exchange sending config requests to DCs
that have been demoted and then bounced. It didn't figure it out for
some time."
HTH
--
Dean Wells [MVP / Directory Services]
MSEtechnology
[[ Please respond to the Newsgroup only regarding posts ]]
R e m o v e t h e m a s k t o s e n d e m a i l
"Craig Johnson" <CraigJohnson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:FA59C252-6397-41DE-8B9A-ED17286D2DB4@xxxxxxxxxxxxxxxx
Thank you. I appreciate the script. However, I can be patient.
So, this should not have any affect on our existing Exchange
enviroment?
Also, we have an under utilized 100 meg link between sites, would this
be
adaquate?
"Dean Wells (MVP)" wrote:
Select one of the two sites in order to deem one as 'retired'. Move
the
DCs from the retired site to the remaining/other site. Reassociate
the
subnet objects such that they're no longer linked to the retired site
and are now associated wth the remaining site.
NOTE - if the scale is appropriate and patience is not one of your
virtues - force replication and trigger the KCC across the affected
DCs
(that may equate to every DC you've got) ... this is by no means a
requirment, I'm just the impatient type. If you're interested, I
wrote
a script to do just that ... but under NO CIRCUMSTANCES should this
script be executed in a production environment unless you're
confident
that the replication load caused by it can be readily sustained by
your
infrastructure ... there are no throttles, no regard for the size of
the
forest, nothing, nada, zip --- it'll just cause everyone to replicate
everything configuration related everywhere ASAP followed by numerous
service restarts and resulting registration/sync. events --- you've
been
warned :0)
It's available here -
ftp://falcon.msetechnology.com/scripts/fba.cmd.txt
--
Dean Wells [MVP / Directory Services]
MSEtechnology
[[ Please respond to the Newsgroup only regarding posts ]]
R e m o v e t h e m a s k t o s e n d e m a i l
"Craig Johnson" <CraigJohnson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:565965B1-3871-47E9-AE30-04DAD1C3D8FB@xxxxxxxxxxxxxxxx
Our environment consists of 3 physical locations with 3 AD sites
and
subnets.
SiteA and SiteB are connected by a high speed WAN link. Both SiteA
and
SiteB
host an exchange server.
We would like to consolidate AD SiteA and SiteB to implement
Exchange
multi-site CCR. It requires one AD site to function.
What would be involved in consolidating two sites into one?
.
- References:
- AD Site Consolidation
- From: Craig Johnson
- Re: AD Site Consolidation
- From: Dean Wells \(MVP\)
- Re: AD Site Consolidation
- From: Craig Johnson
- AD Site Consolidation
- Prev by Date: ADFS Identity Single Sign On Identity
- Next by Date: Re: AD Site Consolidation
- Previous by thread: Re: AD Site Consolidation
- Next by thread: Re: AD Site Consolidation
- Index(es):
Relevant Pages
|
