We had our
server that ran SMS and held database crash. When the hard drive was checked
it was unrepairable and had to be replaced. On rebuild we found we could not
get the new server to accept the old database. We therefore installed SMS on
another server and allowed it to run free, but because SMS is already on the
LAN PCs, the new installation will not recognise the PCs except on those put
on the LAN after the original installation crashed.
Is there anyway to get the new SMS to recognise all the LAN PCs without
visiting every PC to delete the previous installation and registry entries?
Also does anyone have any tips to ease the burden should a complete
uninstall be necessary.
From the microsoft.public.sms.misc
newsgroup
When you reinstalled, did you use the same site code, or a new one? If you
used a new one, the clients think they are members of the original site
code, and know nothing about the new one. To remedy that, you'd need to kick
off an installation method for the new site, either 'smsls.bat'
or 'smsman.exe'.
If it is the same site code, then when you reinstalled, SMS created a new 'SMSClient_sitecode'
account. Even though the site code is the same, SMS created a new password
for that account. The clients know that account with the old password, but
your CAPs (reinstalled when you reinstalled the site server) know the
account with the new password. Thus, the clients are now orphaned. To fix
this, you also need to have the clients download the account and password,
from a logon point. That means running 'smsls.bat'
or 'smsman.exe'
on the clients.
To prevent the second case from occurring again should you ever need to
reinstall again, you should manually create your own SMS Client Connection
account (as a Domain User), then tell SMS about it (Site
Settings | Connection Accounts | Client).
Then, if you ever reinstall and use the same site code, you can just add
this admin created/controlled account to the new site, and the clients can
use that account to access the CAPs, from which they'd download the updated
'SMSClient_sitecode'
account credentials.
This is pretty well documented in the SMS 2.0 SP2 and later release notes,
as well as I believe in the SMS Security Essentials white paper.
|
