After upgrading certain PC on my network to Windows XP they are not being discovered properly. I have them listed in my Systems but the remote tool is not installing correctly on about half of them. Any ideas why this is happening? And how do I go about fixing these systems?
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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Client and Remote not installing correctly on XP clients
- Thread starter FCoda10
- Start date
- Thread starter
- #3
I have a similiar problem, so I'm intested if anyone can enlighten. after upgrading to SP5 I realized i had forgotten to put the SMSCliToknLocalAcct& in the Group Policy to give Administrative Rights to that local account. So on PCs that went through the upgrade, got the new core files, but the local account was not created. in the SMSCLREG.log I'm getting a ComponentInstallCompleteI returned error 5 for component SMS Client Base Components which i'm guessing is an Access Denied message, and the base components don't install
- Thread starter
- #6
I've found that if I'm logged on as an account with local admin rights, SMS discovers the PC. I think it's because the SMSCliToknLocalAcct& account is not a local administrator. Is there anyway of remotely adding this account to the local admins group? (Probably a question for another forum.)
Check you smsls.bat
There you will that, windows xp operating systems will be skipped for discovery and installation...
Take Care
eViLSeeD
There you will that, windows xp operating systems will be skipped for discovery and installation...
Take Care
eViLSeeD
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question