Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS 2.0SR5 Client Recognition Problem

Status
Not open for further replies.

dfmoyer

Programmer
Aug 26, 2003
1
US
We are running SMS 2.0 SR5 on a Win2K3 server.

Boundries are set up correctly and the CAP has the correct settings.

Client installs, though, are not working correctly. On about 40 of 200 systems the client gets pushed out and the install files are on the remote computer. Unfortuantely, the SMS console is reporting the client is not installed and so does not assign it to a site or domain. Attempts to remotely access the systems returns the error "Operating System may be incompatible". All of the systems are Win2k so they should be compatible.

The one thing I have seen that is different than any other post in either these forums or MS support pages is the following errors on most, but not all, of the systems in clicore.log:

Warning - insufficient rights to install C:\WINNT\MS\SMS\core\bin\smscfg.cpl

Warning - insufficient rights to install C:\WINNT\System32\smscfg.cpl

Warning - couldn't update C:\WINNT\MS\SMS\core\bin\cliunins.exe

Not replacing mlaunch.dll; user context has insufficient rights to replace file

The install is running under a local administrator account, so there should not be a problem. When the systems reporting this problem are checked, the files actually are installed and the DLL appears to have been updated.

On quite a few of the systems, but, again, not all, the CliService and CliToken Local accounts are set up but the third account, the CliToken account is not.

Any help you can give is greatfully accepted in advance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top