Re: Splitting Part of existing site off into smaller subnet range
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 7 Feb 2007 11:19:01 -0600
"forrestsjs" <forrestsjs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:894A10BC-61E6-4689-809D-84E670C67BC1@xxxxxxxxxxxxxxxx
Thank you very much for your quick response. I saw similar questions you
answered on the list, but wanted to make sure it would be fine in this
particular case before asking for the switch to be pulled in production
;).
It is hard to truly replicate the complex network etc. in a vm environment
so
your insight is truly helpful.
Just make sure every Site has at least one Subnet which defines it
correctly.
That every Site has at least one SiteLink to another Site, so that all
sites are in a "fully linked network" (i.e., no isolated islands.)
Generally eash site should have specific sites links and be removed from
the "Default-IP-Site-Link" --- but do what makes sense in describing
your network.
Every DC needs to be MOVED to the correct site, if the site was created
or configured AFTER the DC was installed. (DCs try to put themselves
in the correct site, but only during their initial installation setup.)
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- Re: Splitting Part of existing site off into smaller subnet range
- From: Herb Martin
- Re: Splitting Part of existing site off into smaller subnet range
- From: forrestsjs
- Re: Splitting Part of existing site off into smaller subnet range
- Prev by Date: AD design question (OUs and groups)
- Next by Date: Event for Password Changes
- Previous by thread: Re: Splitting Part of existing site off into smaller subnet range
- Next by thread: Re: Can a 2k member server coexist in a 2003 domain/forest
- Index(es):
Relevant Pages
|
