Windows Server 2003
1833768 Members
2100 Online
110063 Solutions
New Discussion

SMS (System Management Server)

 

SMS (System Management Server)

hi experts
can any body guide me to the procedure of installing and configuring the SMS server
on windows 2003 enterprice edition 32-bit os

we have here around 10 domains and all the clients (around 800 no:s )are member of individual domain(no trusting between the domains)

With thanks and regards
Anith Prabhakar.C
4 REPLIES 4
Igor Karasik
Honored Contributor

Re: SMS (System Management Server)

Anith,
you need to write more details about your network structure, clients OS,....
IMHO, generally speaking, you need to install sms2003 primary server on your "central" domain and probably install sms2003 secondary sites on rest of domains (depends on number of clients on each domain, network bandwidth, software distribution packages size,...)

AFAIK, trust is not required. You can use any account valid on the server you are
connecting to - either local to the server or account valid in the destination domain. (you will define that account in SMS site address)

"Systems Management Server 2003 Concepts, Planning, and Deployment Guide" is a good place to learn
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/cpdg/default.mspx?mfr=true
and SMS newsgroup
http://groups.google.com/group/microsoft.public.sms.admin?hl=en
is a good place to ask SMS questions

Re: SMS (System Management Server)

hi

here we are using individual domains that means there is no primary-secondary or parent-child domain consept.

our clients are windows2000-pro and windows-xp-pro

how to create the primary sms doamain and secondary domain

we just need a simple configuration setup in the initial stage

pls revert back

With Thanks and regards
Anith Prabhakar.C

Igor Karasik
Honored Contributor

Re: SMS (System Management Server)

>>here we are using individual domains that means there is no primary-secondary or parent-child domain consept.

I mean primary-secondary in terms of sms2003 sites.

>>our clients are windows2000-pro and windows-xp-pro

So you can use sms2003 advanced clients, more stable and easy clients

>>we just need a simple configuration setup in the initial stage

I think you need to read and understand concepts of sms2003 before planning and install. There is no general way to install SMS, every site design is a bit different.
I suggest "Scenarios and Procedures for Systems Management Server 2003: Planning and Deployment"
http://www.microsoft.com/downloads/details.aspx?familyid=E0644BB4-2336-4254-8A18-9BC180713F7E&displaylang=en
as step-by-step guide. Document have 400+ pages but you probably don't need to read all pages.
Some useful tips you can found here:
http://myitforum.com/articles/8/view.asp?id=6385


Alan_152
Honored Contributor

Re: SMS (System Management Server)

First of all, I'm going to assume that you are installing SMS2k03 in an active directory environment (BTW, if you are, then you should know that win2k server and beyond with AD will perform the grand majority of SMS's functions for far less cost). By AD Envirnoment, I mean a full version, not a hybrid PDC/BDC emulation environment. I'm also talking about a single domain, not a tree or forest.

1st, you'll need at least 1 big piece of hardware to run a domain controller, crystal reports, SQL+server, and the SMS server package. Those servers will have to have a lot of bandwidth. The number of servers is determined by the physical size and distribution of your domain.

2nd, you'll need to set up some replication of the sms client scripts across all the domain controllers (not just the DCs with SMS server on it).

3rd, you need to create an SMS client install and startup script, and tie it into all the login scripts used by users. You'll need to take into consideration platforms, OSs, and bandwidth of all your clients (for example, you don't want to do a full client install over a dialup or vpn). You'll probably want to learn Kixtart or VBscript for this.

4th, depending on what you'll actually be using SMS for, you'll need to be familiar with one or more of the following:

* SMS Installer
* Crystal Reports
* SNMP
* HPOV quicktools
* SMI
* MIBs
* silent package installation and creation
* inventory filters

Not to scare you off, but SMS administrators are a dying breed. I charge quite a bit for the rather low skill level I have, and I am thankful that AD is actually easier to deal with for most of SMS's chores.