/build/static/layout/Breadcrumb_cap_w.png

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!

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Tone 16 years ago
Second Degree Blue Belt
0
I would make sure you shops are in a remote boundary, in case you ever need to send anything to them..
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ