Re: Move SMS 2003 to another server

"Lisa@" <Lisa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:49D1D92E-E7B5-40B2-B600-8727AAD890DF@xxxxxxxxxxxxxxxx
HI - thank you for responding to my plea! It appears that SMS client is
installed on the clients. In Admin Tools >> Services on an XP
workstation,
SMS Agent Host and SMS Remote Control Agent are both automatic starts.
The
collection "All Windows XP Systems" does show a significant number of
clients; I have not taken the time to compare them to a current list from
active directory, but I recognize most of the computer names to be
installed
on our campus. (We have just over 150 workstations.)

OK

I think the previous IT Director made this particular server a domain
controller *after* many of the applications were installed - we have a
very
limited budget and apparently this server was the best of the bunch when
another one went down. Not only is it the domain controller, but it is
also
the primary DNS server and DHCP and WINS. I just have to believe that he
never got back to SMS after all that and had forgotten that SMS should be
on
it's own box. In fact, this is a great blessing to me, because I get to
learn SMS from scratch and make it my own!

Absolutely, it's all good (as they say :)

Our SQL Server 2000 (ver 8.00.761) server does contain the current SMS
database along with several of the institutions specialized database
applications. I wasn't planning on putting SMS on it, I have another box
that will suffice. I know I have a lot to learn, but I assumed I would be
creating some sort of ODBC connection from the new server to the SQL
server.
My main goal is to keep the network stable...I'm not planning on messing
with
SQL server right now. By the way, the current SMS database is just over
750
meg.

In the Deinstallation program, there is a checked box beside "Delete SMS
site database". Since the database is on a different server, do you still
recommend that I accept that default? Would there be any advantages to
keeping it and unchecking that box?

I'd probably not choose that option (it may not work for a remote database
anyway), after the site is de-installed, delete the sms database (and files)
from SQL Server.

Finally, I don't understand about the instruction to "change the sms site
assignment to the new sms site server." If at all possible, I don't want
to
touch these 150 clients individually. I can, but that seems contrary to
the
whole purpose of installing and configuring SMS.

You're asking the right questions, there is no way I'm recommending touching
that many devices individually. It's all about automation...

There are two ways you can go with a new install; since you have a number of
clients already assigned, it may make sense to install SMS with the same
site code as defined before.

If you install SMS with a different site code, you can migrate the clients
from the old site to the new... by doing so, you know that these clients are
properly communicating and participating in the new site. Migration can be
accomplished with machine startup GPO using a vbscript like the one I posted
here:
http://www.myitforum.com/articles/8/view.asp?id=8404

BTW, that site has a lot of great SMS related information. Also, another
great jumping off point:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828368

Plus, I haven't run across
any of those procedures yet, so, as you can see, I have a lot more to
learn.
Thanks for your advice and taking the time to help me!!

No problem!

Steve


.

Relevant Pages

  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: Help need desperately!
    ... > Have you given your SMS Server's machine account FULL CONTROL of the Systems ... > machines are already discovered or you wouldn't be able to push to them. ... > Check through the SMS Server logs, ... All clients are discovered, assigned and have successfully installed the ...
    (microsoft.public.sms.inventory)
  • RE: Advanced client cannot auto discover management point
    ... then was to delete the site boundary from the central site and correctly ... have SMS clients that are getting site assignments, ... child site server. ...
    (microsoft.public.sms.admin)
  • Re: Backup and reinstall
    ... correctly provided site code & site server name. ... MVP SMS ... > Your clients will be assigned to the site if you create the same boundaries. ... > Lars Norman Søndergaard ...
    (microsoft.public.sms.setup)
Loading