SMS 2003 implementation project
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).
Situation:
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?
Thanks!
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).
Situation:
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?
Thanks!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Tone
17 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.