Forget the manuals. Buy Brian's book. Regards,
Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Tuesday, September 13, 2011 4:06 PM To: NT System Admin Issues Subject: Re: Q about AD sites Clearly it's time to break out some manuals and update my knowledge. On Mon, Sep 12, 2011 at 18:13, Brian Desmond <[email protected]> wrote: > Well, if the subnet is linked to a site which does not contain any DCs, the > Auto Site Coverage process will kick in, and AD will look at site link costs > and so forth to determine what DCs from another site should cover this > DC-less site. This means you just need site links in place that match what > you want. You can work around auto site coverage by disabling it and manually > populating the site coverage reg key on the DCs you want to cover this site, > but, that's obviously a less than ideal solution. > > Thanks, > Brian Desmond > [email protected] > > w – 312.625.1438 | c – 312.731.3132 > > -----Original Message----- > From: Kurt Buff [mailto:[email protected]] > Sent: Monday, September 12, 2011 3:40 PM > To: NT System Admin Issues > Subject: Re: Q about AD sites > > On Mon, Sep 12, 2011 at 13:26, John Cook <[email protected]> wrote: >> We’re about to do a restructuring of our sites and two of them will >> not have a DC on site anymore. I know you can have multiple subnets in >> a site that contains a DC but is it possible (or even necessary) to >> link these standalone sites to a DC in another site? > > AIUI, if you don't link a subnet to a site to with a DC in it, logons > (workstation and user) in that subnet will randomly connect to any site that > responds, and there will exist the potential for some random weirdness that > will frustrate folks. > > If I were in your shoes, I'd choose a site with a DC that has a relatively > high capacity link between it and the orphan subnet, and make the orphan > subnet a part of the that site. > > But, someone with more experience will probably chime in with better advice. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
