Re: SMS 2003 design - help requested

Thanks for your quick and detailed reply Kim, the info was very useful.

If I could clarify a couple of the points:

>> *** Yups, no secondary sites in these environments means no proxy management
>> points which means clients send this data to the assigned management point.
>> This doesn't necesarily make your design invalid, but you have to account
>> for this network traffic. (Inventory files are delta files, and status
>> messages are relatively small).

Based on the proxy management not being locally available to the Office
Locations and therefore having no advantages, I'm thinking it would
make sense to add all of the Office Locations to the HQ's primary site
server boundaries. Is this recommended?

Based on your feedback on point 3 of alternative designs, I think I
could justify doubling the secondary servers from 4 to 8. This would
allow for a secondary server in all of the locations where the head
count is over 60.


>> I have my doubts with the 2 additional protected dp's at the HQ, if the
>> local protected dp isn't available then afaic no distribution happens
>> period.
>> My doubts sterm from the fact that I am not 100% positive that the clients
>> will use their local dp, instead of loadbalancing between the local & the 2
>> HQ protected dp's which is not what you want.
>> Also keep in mind that once you go for protected dp's that you can better do
>> it for all dp's including the one's at HQ. And protected dp's are not
>> accessible by Legacy clients.

I'm a little confused here. When I wrote my original post I wasn't
planning on making the HQ's first DP protected. I was thinking that
this DP would really be designed to serve the HQ's local clients, as
well as the Office Locations that don't have a local DP. I was then
thinking of adding 2 Protected DP's to the site where I would add the
subnets of all of the Branch Office locations. Having read your post
it becomes clear that if I don't Protect the first DP, then there's
nothing stopping the Branch Office locations from using it.

So let's say I make the HQ's first DP protected and add the local
subnet at the HQ as well as the subnets for the Office locations that
don't have a local DP - making sure that I leave out the subnets for
all of the branch office locations. Then on the two additional
Protected DP's, I add the subnets of the Branch Offices. Are you
saying here that the clients local to the HQ site (subnet) may try and
load balance between all three DP's rather than going to just the first
one? Also that leaves in question the behavior of the Office Locations
that are not local to the HQ - will they be able to stick to the first
Protected DP at HQ too?. Lastly, the Branch Office locations, will
they be able to ignore the Protected DP (since they are not local to
it) and connect to one of the two additional Protected DP's?

I don't plan on having any legacy clients so don't have to worry about
them not being able to access the Protected DP's.


Thanks for all your help,

Pete.

.

Relevant Pages

  • Re: SMS 2003 design - help requested
    ... Subnets need to be added to the local sms site. ... > well as the Office Locations that don't have a local DP. ... > it becomes clear that if I don't Protect the first DP, ...
    (microsoft.public.sms.setup)
  • Re: AntiVirus
    ... centralized management which would include auto updating of virus definition ... If this is not an issue then going for something like Trend Server Protect ... We used it that way while our clients were protected with ...
    (Security-Basics)
  • Re: How is a software f/w inferior to a hardware f/w?
    ... >If ZAP will only protect the computer it's on, ... Requests from the clients are also blocked to ... firewalls are necessarily bridging or, more rarely, routing. ... boxes to your network and then not connect anything to it. ...
    (comp.security.firewalls)
  • Re: How to protect the VFP codes - Visual Sourcesafe
    ... i never leave source code on a clients machine. ... I like to protect my VFP project. ...
    (microsoft.public.fox.helpwanted)
  • Re: Another funny verizon trick. RANT WARNING!!
    ... I know some of you will say "Yeah, maybe you're right, ... but the companies HAD TO put all that crap in there ... they have to protect themselves from???? ... clients... ...
    (alt.cellular.verizon)