On Windows XP clients that are deployed by a OSD task sequence with the SCCM client as a task the regstration of the Config Mgr client with the management point fails with the following error. ClientIDManagerStartup.log: RegTask: Client is not registered. Sending registration request... RegTask: Server rejected registration request: 3 On the management point in the MP_RegistrationManager.log the following lines: Certificate issued to 'SMS' has expired.MP Reg: Registration request body is invalid. MP Reg: Registration failed. The site mode is mixed. Clients are Windows XP service pack 2. The certificate store on the client contains a SMScontainer with two certificates valid until 2108. Push installationto other workstations clients works fine and as expected. No idea yet what causes the rejectionand how to solve it.

Same happened in my environment today too... Possible bug?

Fixed in my environment, by opening "Certificates" console for local computer on Client PC, and deletedtwo (?)SMS certificates. Repaired the client and its ok now.

Ankr, thanks for figuring this out. I still like to what's the reason for the expired certificates. [MSFT]? If we know the reason, we canmake sure this doesn't happenanymore instead of solve itby removing the certificates. Is it possible that there are some some leftovers of a ConfigMgr client installation (read: certificates) in the OS image?

Maybe you have used TS to capture an image of your Windows XP? Those certificates as I understand, should be removed before sysprep task by step "Prepare ConfigMgr Client". Maybe you skipped this step? Just a guess, I think it works like this.

There is not much to configure in the Prepare ConfigMgr task. Do you mean there are manual steps involved like removing of the certificates during the capture phase in Win PE? IMHO that's whats the Prepare ConfigMgr task should do.

I thought maybe you dont have this step at all. But it seems like you had it. No ideas for now...

I have had this problem and if you look in the ClientIDManagerStartup.log on the client. It seemed as If the "Block Client" action was invoked from the SCCM console. Follow these steps below on the client that is giving you problems. this should fix it for you What you need to do is take a look at the certificate on the client - Just load up the MMC Console and Add/Remove Snapin - Select Certificates - Select local computer - Locate the SMS folder and double click the signing certificate and take a look at the certificate. Validate that the certificate has not expired (more than likely it has). Hope this helps JoeJoe Assad