Re: AD Site Consolidation

Outstanding. Thank you all for your feedback and input.

"Dean Wells (MVP)" wrote:

.... missed the lsat question. Yes, im my opinion, a reasonably
available 100Mb pipe is going to more than suffice.

--
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?






.

Relevant Pages

  • Re: Universal Group Membership Caching
    ... Dean Wells [MVP / Directory Services] ... since all KDC are DCs and all DCs maintain a config. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Universal Group Membership Caching
    ... Dean Wells [MVP / Directory Services] ... since all KDC are DCs and all DCs maintain a config. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Local SID v. Domain SID.
    ... This is not true for the relationship between any 2 workstations regardless of whether they have the same SID, are members of the same domain, trusted domains or if they exist in the same or even different workgroups. ... Dean Wells [MVP / Directory Services] ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Site Consolidation
    ... Dean Wells [MVP / Directory Services] ... SiteA and SiteB are connected by a high speed WAN link. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Redirecting the users and computers containers in Windows Serv
    ... they will be created in whatever OU or container you ... Dean Wells [MVP / Directory Services] ...
    (microsoft.public.windows.server.active_directory)