Re: Our first secondary site

Tech-Archive recommends: Fix windows errors by optimizing your registry

What Kim said. :-)

Also, however you configure it, remember never to overlap your boundaries,
even/especially if you have secondary sites. Sites should never include
boundaries of other sites, even child secondary sites.

--
Cathy Moya, CISSP, MCSE: Security
Lead Technical Writer SMS v4, Management & Solutions Division User
Assistance

Check out the SMS v4 Documentation on TechNet:
http://www.microsoft.com/technet/sms/2007/evaluate/default.mspx
This posting is provided AS IS with no warranties and confers no rights.

"Kim Oppalfens [MVP]" <""Kim dot Oppalfens\"@google mail.com"> wrote in
message news:egQEwGR3HHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Matthew Hudson wrote:
If you want the computers to ONLY talk to the Secondary then you need to
add all the subnets and check the box to make it protected. Otherwise
the clients will pull from the primary site across the DS3 link. Yes you
could put in there 10.200.0.0 and it will grab every subnet there. if
you are the only company on the private subnet then there is not a
problem.

Set the secondar sites boundaries to 172.19.0.0 and set as protected so
they will be forced to use the secondary. Set the roaming boundaries as
the primary so if a laptop is moved to the primary site for a meeting it
will talk to the primary and again not go down the DS3 link to the
secondary. Does that all make sense ?

Erm, I disagree here, sms does a string comparison on the exact subnet, so
the subnets have to be exact which means you have to put them in.

Alternatively you could add 10.200.0.0 to an active directory site, and
use active directory site names for your boundaries.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx


.

Quantcast