Hi,

 

Are there some precausions i should take before reinstalling an Xp pro client?

We have RIS for reinstalling XP and SMS2003 for redeploying software.

So far a client can be reinstalled under the same name in Active Directory, The sms client is being installed trough GPO. But after that the software isn’t going to be reinstalled by sms.

In the System management properties of the SMS client, only Discovery data collection cycle and File collection cycle is present. Even when in advanced tab the sms site code is reconnized correctly (discover button).

 

I thought that when a XP client dies and is being built up by RIS the sms2003 server would reconized the sms client and would redeploy all software. What am I doing wrong?

 

Best regards,

Marco

 

Edit: Ik seems Management point has stopped responding to advanced clients.. It worked perfect, but suddenly stopped.. Help.. What can i do to fix this?

When you RIS a system that used to be a SMS client, it should show up as obsolete after the new client is installed provided all is the same such as system name, but tends to be true.

There can be a lot of problems with a MP. What error messages are in the mpcontrol.log file on the MP? If you are getting the HTTP 200 OK messages, you are probably good to go..

Hi Brian,

Yesterday I discovered that another System administrator decided last wheek in his wishdom to install WINS in behalf of Exchange Server. Sins than client logs report that they can’t find the MP in WINS database.

I think the problem rests there. Clients don't look futher in AD, and hang. You don't notice it until you reinstall a new client and it can’t get his policy upated. Http 200 doesn't work either.

Removing WINS doen't solve the problem, i tried that. Is there something i have to put into Wins or DHCP to point to de SMS MP? Is there a workaround?

 

Thnx

Marco

 

WINS is required for Exchange (at least it was a few years ago when I last worked with it). The problem is not WINS and it's not required for SMS clients unless the AD schema has not been extended. Sound slike your MP is more of the issue at this point. If the MP is down, so are all your clients that report to it. Make sure your MP is listed in the System / Systems Management container in AD. if not, then you did not successfully extend the schema or the MP does not have the proper permission to add to that container in AD. If you KNOW that that's setup correctly, then check the locationservices.log on the clients and see if they see which MP to report to. If that works, then your MP is the issue. Any errors / fails in the mpcontrol.log file on the server?

Hi Brian

Ad schema was extended succesfully. Strange thing whas that on de client logs on the time the trouble started the date and time started to go all wrong. 00:00 for time and 00-00-36 for date for all logs from the time the trouble started.

I still find it strange that the strange log time, not connecting to MP all started at the exact time WINS was installed.