RE: Reinstall



Hi,

Thank you for posting.
This is Lee and I am glad to meet you in the newsgroup.

Based on your description, my understanding of the issue is:
You had a SMS 2003 RTM server.
Now you do not need this server any more and you want to install a new SMS
2003 SP1 site server on the SQL computer.
So you like to have some information regarding uninstallation and
reinstallation of the SMS site server.
If I have misunderstood your concern, please let me know.

To this issue, I would like to recommend you perform the following steps:

1. Uninstall the SMS clients from the subnet first.
For detail steps, please refer to the following URL:
826842 How to remove a Systems Management Server 2003 client
http://support.microsoft.com/?id=826842

You can deploy the CCMclean.exe with group policy or current SMS to
uninstall the SMS client first.

2. Then uninstall the SMS site server and delete the DB on the SQL server.

Note: After we remove the SMS 2003 server from the add/remove programs, you
need to delete the following items to completely remove SMS from a site
server
computer:

<operating system drive>:\SMSSetup.log
%Windir%\System32\smsmsgs
%Windir%\System32\smsexec_PROCHIST.DAT
%Windir%\SMSCfg.ini (if SMS 2003 client components are not installed on the
computer)
C:\Documents and Settings - all profiles with an SMS prefix (if the
computer is not an SMS 2003 Legacy Client)
%Windir%\Help\sms

The SMS_CCM folder in the SMS installation drive (if the computer is not an
SMS 2003 Advanced Client)
The SMSPKG folder (compressed package folder) on the SMS installation drive

HKLM\SYSTEM\CurrentControlSet\Services - all entries with an SMS prefix
such as SMS_DISCOVERY_DATA_MANAGER, SMS_INVENTORY_DATA_LOADER,
SMS_LAN_SENDER, SMS_SOFTWARE_INVENTORY_PROCESSOR,
SMS_SOFTWARE_METERING_PROCESSOR, and SMS_STATUS_MANAGER

HKLM\SOFTWARE\Microsoft\SMS (if an SMS 2003 client is not installed on the
computer)

HKLM\SOFTWARE\Microsoft\NAL (if an SMS 2003 client is not installed on the
computer)

The SMS namespace from WMI (Root\SMS)

Depending on the SMS 2003 security mode, the domain or local computer might
contain various accounts that are related to SMS. The number and type of
accounts depends on the security mode that the site was configured with. A
site configured with standard security generates more accounts than a site
configured with advanced security. Remove the following accounts (which
exist for either security mode): SMS Admins, SMS Reporting Users (if an SMS
reporting point was created),

SMS_SiteSystemToSiteServerConnection_sitecode,
SMS_SiteSystemToSQLConnection_sitecode, and
SMS_SiteToSiteConnection_sitecode.

If the site was configured with standard security, then there might be
additional SMS user accounts (such as the SMS Service account (SMSService
by default), SMSClient_sitecode, and
SMSServer_sitecode).

3. Then clean the aged entried in AD if you had published to AD in the
previous.
Open the "Active Directory Users and Computers" MMC.
Select View > Advanced Features, expand the <DOMAIN> and select the System
Management container.
Delete the enties in this container.

4. Now you can install the SMS site server on the SQL computer.
If you had extend the AD schema in the previous, it is not necessary for
you to extend it again.

Hope the above information helps. Have a nice day!

Sincerely,

Lee Li
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • 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)
  • Re: Cannot make SMS clients install; SMS_HIERARCHY_MANAGER problem
    ... you tried to push the client on, so I would first check the smsprov.log file ... Secondly, if SMS provider generate the CCR records successfully, then CCM is ... second log at server side to check would be ccm.log. ... > The only method I've tried to install the client with is by using a Client ...
    (microsoft.public.sms.setup)
  • 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: Sms 2003 - Advance client
    ... Microsoft MVP - SMS ... >> we have installed sms 2003 server in our office and Advance client ... >> try to install advance client manually also it is not replicated to sms ...
    (microsoft.public.sms.admin)
  • Error Advanced Client setup
    ... I'm having a problem installing the SMS advanced client on certain servers. ... Action start 16:07:53: INSTALL. ...
    (microsoft.public.sms.setup)

Loading