Hi all

I'm busy with the design phase for an SMS 2003 project for a customer. I'm rather novice when it comes to 2003 (have experience with SMS 2.0).

HQ: 1500 XP SP2 clients, 1 LAN network
Remote: 250 XP SP2 clients situated in shops, each shop has 2 computers and is connected to HQ with 256 Kb line.

Currently they use SMS 2.0 with 1 site server, 1 distribution point and 10 CAPs.

For SMS 2003 I would simply use 1 site server which also functions as DP, CAP and Management point. That's it.

Am I right if I would say: no more than just this? Will performance (sending inventory data, site updates, ...) be OK for those shop pc's? Software distribution is not done for those shop pc's.

Any other remarks or suggestions?

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Hello, the following three links (though not specific to SMS 2003) may provide a little guidance :

SMS Network Traffic Considerations
SMS Network Traffic Considerations Part 2
SMS Network Traffic Considerations Part 3

Apologies if you have already reviewed these.


Answered 06/07/2007 by: spartacus
Fifth Degree Brown Belt

Please log in to comment
thanks for those links!

2003 is more efficient than 2.0 right?

would like to see some personal opinions.
Answered 06/07/2007 by: renio
Senior Yellow Belt

Please log in to comment
How many remote sites do you have? You may want to at least setup secondary site servers at your remote sites so clients don't have to cross the pipe to report back to the management point. Or at the least setup servers in the remote sites to just act as distribution points. Don't know how much bandwidth you have but doing this would definately reduce the amount of traffic going across the pipe.
Answered 06/15/2007 by: danr29
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity