|
I've rebuilt an SMS2.0 SP2 server the same
way as it was before. The clients are now not making there way back to the new
server. After looking at the client logs it states that it cannot locate the
\\CAP server. Everything was setup the same as the last one, so why can't the
clients now locate the SMS Server, and secondly how can this be fixed? The problem might be that the clients are still
using the old Client Connection Account (defined in your previous site). This
information is in each clients registry under 'HKLM\Software\Microsoft\NAL\AbExprtDB' - it
contains encrypted information to allow the client to access a CAP. To get it
working :
- De-install the client completely and remove
any remaining registry entries under 'HKLM\Software\Microsoft\NAL'
and '\SMS'. Also
delete the 'SMSCFG.INI'
files from '\systemroot\.'
- Reinstall the client. If that still doesn't work:
- De-install the client again.
- Create a new connection account on your
SMS server (to replace 'SMSClient_sitecode')
To do this you must:
- First create the account on the domain
(make it a member of 'Domain Users') and give it a password.
- Open the SMS 2.0 Administrator console
and go to 'Site Settings | Connection
Accounts.' Create a new entry here using the
account you just created.
- Re-install the client.
Knowledge Base Article
237759
'SMS:
Avoiding Client Lockouts When Using Client Connection Accounts' details
this problem.
After sometime your clients should start to be discovered
and installed. Once the new account information has replicated through your SMS structure
you can delete the old account. The old account may lock out as clients having
the old account/password information try to connect to a CAP.
Note: You should activate (if not already the case)
the Windows Networking Logon Client Installation method so that *existing*
clients can pick up the new Connection Account information. They won't see the
new account if you are only using the Windows NT Remote Client installation
method.
|
