Re: Documentatio abouth how to deploy step by step SMS 2003

Microsoft has many documents on their website, plus there are documents that
come with SMS itself. However SMS can be a complex product that you should
know and understand before thinking you can just put in the cd and install
it. There's a ton of features to it, things it can do but it can also hurt
your environment if not done correctly.

If you want to do it yourself, first I'd suggest determining who's going to
be the sms administrator after it is up.
Figure out who also will play a part, who will be part of designing it, the
networking guys, the desktop guys, ..
designate a project manager for the project.
Send the team to classes, maybe have one attend a design class, one an
administrative class, etc..
Start gathering your documentation from Microsoft's website, myitforum.com,
and any place else.
Setup a test lab and walk through the exercises, try to understand the
concepts so you know which ones apply to you.
Run through things in the lab several times until you are sure of your
design and configuration settings. Trust me there's a lot. hundreds and
hundreds of different things you can configure.
Create your project plan for the rollout. SMS has really three parts to a
rollout. Getting the servers in place and configured. Discovering the
potential client. Deploying the client agent to the ones you want to have
it.
When doing all this there's several things that can come up though. Be
ready to troubleshoot and find assistance. Microsoft support is about $200
per incident. But you will definitely need some on your first go at this.
Remember no matter how close you try to get your lab environment to
represent your production environment it will never be exactly, especially
when it comes to the client machines. You will run into many problem
machines where you simply can't get the sms client to install or work
correctly. You'll need to research those and figure them out.
Once you do finally get it place you have to administer it and use it daily.
You'll need to come up with processes and procedures for doing different
tasks.

Anyway my recommendation is to hire a professional who has done other sms
designs and installs. Make sure if you do that they are not just some guy
who also will just plop in the cd and hit the next button. See references.
Talk to them find out exactly what they will do. They should be creating a
design and configuration for everything based on your environment. There
should be discovery involved especially around your lan\wan infrastructure.
They should give you a lot of documentation on why things should be designed
or configured like they are suggesting. At the end you can also have them
do a little internal training for you and your group, maybe put together a
guide for you at the end. daily, weekly, monthly, as needed tasks, etc...
how to do backups, how to create a package... etc.. I don't have any idea
the size or complexity of your environment but expect this to be at least 4
weeks if you are a small simple company.

If you need any ideas on who to hire or that sort of thing let me know my
email is mattw112 at hotmail.

Oh and by the way for future this newsgroup you posted to is for a product
called "SMS installer" it is a repackaging tool. You'll find the most
helpful newsgroups to be sms.admin and sms.general. And then depending on
what piece of SMS you are working on there are several others. like I
mentioned above www.myitforum.com is also the #1 resource for sms on the
web, they have forums there too.

Terry


"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B37A4856-DAAE-4E61-8686-17B6CD5C4C71@xxxxxxxxxxxxxxxx
Hello friends

We want to have to deploy of SMS 2003 with SP2 on our organization, but do
you have any documentation abouth which is all the procedure for to
deployment SMS 2003? Do you have a step by step about how to install a
SMS,
Clients and how to configure the five components that have SMS 2003.

Thank very much


.

Loading