Re: SMS_MP_CONTROL_MANAGER, MessageID: 5443

If it was a previous client, it probably has sent its public key in the SMS
database.
Then, if it was reinstalled, the same identity was preserved but it now has
a new public key.
Now, the authentication checks in the mp are failing because what is written
in the DB doesn't match with what the client is now sending.
You can delete the keys in the ClientKeyData table in the DB. Once deleted
you no longer will get these rejections.
(Heartbeat discovery will repopulate the this table with the new public
keys.)

--
Thanks,
Joseph Calabig

This posting is provided "AS IS" with no warranties, and confers no rights.

"RudyM" <RudyM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B297E9C6-9CF8-4205-9286-EC28CD4C4E32@xxxxxxxxxxxxxxxx
> Hi all,
>
> During test of our client upgrade process i stumbled into the following
> message in the SMS_MP_CONTROL_MANAGER logs:
>
> 'MP has rejected a message from client
> GUID:C61476EC-9311-446E-8747-B86C11894AD5 because it was signed with a
> public
> key that does not match the key published in the database.
>
> Possible causes: The client is incorrectly identifying itself, or the
> client's signing certificate was re-created, resulting in a new public
> key.'
>
> This doesn't happen when we perform a fresh upgrade of an SMS client.
> It only happens after a re-install of an SMS client that was previously
> assigned to the SMS2003 site, without first removing the SMS2003 client.
> In
> fact we use an unattended setup procedure to re-stage the PC into the old
> SMS2.0 environment and then deploy our client upgrade script again. We
> always
> use the same PC in our tests.
>
> Anyone any idea why this happens?
>
> brgds,
> Rudy


.

Relevant Pages

  • RE: SMS Advanced Client refuses to do its job
    ... [Configuration - Client Properties] ... SMS SMBIOS Serial Number Identifier=43004E0055003700340034003000460050004A00 ... SMS Hardware Identifier=4BE9C601019A00EA ... policy update with 0 assignments" This is correct as there are no adv's for ...
    (microsoft.public.sms.swdist)
  • RE: SMS Advanced Client refuses to do its job
    ... Advanced tab? ... does it have a value for SMS Unique ... SMS client preloaded; you should have run stopped the SMS Client server, ... policy update with 0 assignments" This is correct as there are no adv's for ...
    (microsoft.public.sms.swdist)
  • RE: SMS Advanced Client refuses to do its job
    ... Advanced tab? ... does it have a value for SMS Unique ... SMS client preloaded; you should have run stopped the SMS Client server, ... policy update with 0 assignments" This is correct as there are no adv's for ...
    (microsoft.public.sms.swdist)
  • Error Advanced Client setup
    ... I'm having a problem installing the SMS advanced client on certain servers. ... Action start 16:07:53: INSTALL. ...
    (microsoft.public.sms.setup)
  • Re: Forcibly move Client out of a collection w/o deleting ??
    ... In AD, I moved the client to the proper OU and the client showed up fine in Collection Y, which is a sub collection of Collection X. ... If this is dynamic collection than there is now way of doing this without either deleting the machine from the database or making sure it doesn't meet the criteria anymore. ... Kim Oppalfens - Sms Expert for lack of any other expertise ...
    (microsoft.public.sms.admin)
Loading