Re: Move SMS 2003 to another server

Hey - I've been doing some reading since your questions and my reply to it.

Regarding the issue of SQL Server 2000, since we do have it on another
server, do I have to have it on the SMS server too??? This link makes it
appear that I need it on my SMS server:
http://www.microsoft.com/smserver/evaluation/sysreqs/default.mspx - look in
Server Compnents.

How can this be?

"Steve Thompson" wrote:

Lisa,

You don't mention whether your clients have the SMS client installed? You do
state that the servers are in the collection, but that could be the result
of AD discovery.

Since you indicate that you have not really used the existing site for
anything, I would recommend simply de-installing SMS from your domain
controller (which by the way is a poor server role to choose). Use the setup
option, from the Programs>SMS option, choose remove this site.

If you have not (assuming you have implement an Active Directory), Extend
your Active Directory for the SMS extensions. Then, re-install your new SMS
site on the server with SQL Server. I'd probably choose a new SMS site code.
Configure the SMS site properties; hardware, software, software
distribution, etc.

Now, for clients that do not have the SMS client installed, simply deploy
the client. For existing clients, change the sms site assignment to the new
sms site server.

Steve

"Lisa@" <Lisa@@discussions.microsoft.com> wrote in message
news:4FC0EB3B-3766-4099-A1F1-B309DE7F3DAC@xxxxxxxxxxxxxxxx
Hi, I have an issue that must be quite unique, because I cannot seem to
find
any relevant references to uninstalling SMS and moving it to another
server.


I am new to this position, and although I love the concepts, I have never
really worked with SMS. There are 15 or so W2K3 servers here and about
150
XP clients. It is a small and stable network, and my desire is to keep it
that way!! There are just 4 of us here in IT, and we want to use SMS for
remote control and updating client software via package pushes. All the
rest
of the administrative functions and reporting possibilities are projects
in
the distant future as I learn and understand SMS.

We have SMS Server 2003 (version 2.50.3174.1018) installed on a domain
controller that is running out of space. It was installed by the previous
IT
director in 2004. SMS apparently has never been utilized, configured, or
managed. However, it does appear to be functional- the MMC screen comes
up
just fine and there is old but relevant data in the Site Hierarchy,
Collections, System Status and other areas. We also have a separate SQL
server that apparently holds the SMS database.

I have configured another Windows 2003 server specifically for SMS
purposes
and would really like to just transfer the whole installation from the
domain
controller over to the new application server. The new server I just
created
is listed in Collections > All Windows Server 2003 Systems, so SMS is
doing
something to search and find new client to add. I can only assume that
all
the clients listed in the different collections have a client service that
"points" them to this current installation.

So, where can I get information and procedures on how to properly move or
uninstall/re-install SMS in the best, most efficient and most economical
way?
I have honestly searched the SMS sites and various documentation and
online
books for over a week now - I've found a lot of interesting info and know
that I need to learn alot during this planning and deployment process.

My main desire is to free up space on the server that SMS is currently
residing on, and it's not a huge hurry-up-we-gotta-do-it-now project. We
most likely have 4 - 6 months before there's a desparate need for space.
Also, just for your info, we also have no money to send me to a week long
SMS
Admin class.

If I have to un-install SMS and lose everything, that's OK...once I get
space on this server, I can take my time and plan the re-installation and
deployment. But if there's a way to "move" the application and keep the
data
and the client "pointers" without causing grief with network traffic, that
would be better. At any rate, those are my uneducated, unexperienced
thoughts.

Have I given you enough info to point me in the right direction? What is
the best way to proceed?




.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
  • Re: Installation of Client
    ... SmsDetectDowngrade_ErrorMessage = A newer version of the SMS ... Advanced Client is already installed ... I also manually added the WINS information into the WINS server that both ... cannot get the client to properly install. ...
    (microsoft.public.sms.setup)
Loading