drewtown Posted September 6, 2013 Report post Posted September 6, 2013 After moving the SCCM 2012 SP1 VM to a new host clients are no longer able to communicate with the MP. This is an intranet site with HTTP or HTTPS enabled. I've tried reinstalling MP Reinstalling Client Clean install of client (uninstall, delete certs and folders, reinstall) I can access http://mp/sms_mp/.sms_aut?mplist and http://mp/sms_mp/.sms_aut?mpcert from the client machines. Any help appreciated. Thanks ClientIDManagerStartup.log [RegTask] - Client is not registered. Sending registration request for GUID:E1DE3B01-ABEB-49E3-9571-70EBF9F8E052 ... ClientIDManagerStartup 9/6/2013 1:23:17 PM 56724 (0xDD94)RegTask: Failed to send registration request message. Error: 0x87d00309 ClientIDManagerStartup 9/6/2013 1:23:17 PM 56724 (0xDD94)RegTask: Failed to send registration request. Error: 0x87d00309 ClientIDManagerStartup 9/6/2013 1:23:17 PM 56724 (0xDD94)CertificateMaintenance.log Failed to verify signature of message received from MP using name 'MP.domain.local' CertificateMaintenance 9/6/2013 1:24:17 PM 56724 (0xDD94)Failed to verify signature of message received from MP using name 'MP.domain.local' CertificateMaintenance 9/6/2013 1:25:17 PM 56724 (0xDD94) ClientLocation.log Rotating assigned management point, new management point [1] is: MP.domain.local (7804) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 9/6/2013 1:23:17 PM 56724 (0xDD94)Assigned MP changed from <MP.domain.local> to <MP.domain.local>. ClientLocation 9/6/2013 1:23:17 PM 56724 (0xDD94) LocationServices.log CCMVerifyMsgSignature failed. LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)Failed to verify received message 0x80090006 LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)CCMVerify failed with 0x80090006 LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)Failed to verify message. Could not retrieve certificate from MPCERT. LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)MPCERT requests are throttled for 00:00:59 LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)Failed to verify message. Sending MP [MP] not in cached MPLIST. LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94)MPLIST requests are throttled for 00:55:59 LocationServices 9/6/2013 1:27:18 PM 56724 (0xDD94) Quote Share this post Link to post Share on other sites More sharing options...
Canada Jack Posted September 9, 2013 Report post Posted September 9, 2013 It's seems Certificate issue. Quote Share this post Link to post Share on other sites More sharing options...
drewtown Posted September 9, 2013 Report post Posted September 9, 2013 It's seems Certificate issue. Yes, that appears to be the case but I am running in HTTP or HTTPS mode. Also this was working fine until I moved it to a new VM host. Quote Share this post Link to post Share on other sites More sharing options...
drewtown Posted September 10, 2013 Report post Posted September 10, 2013 I continue to have trouble with this. I've uninstalled IIS, MP and then reinstalled IIS and MP. Didn't work. Reinstalling client with RESETKEYINFORMATION. Didn't work. Anybody? Quote Share this post Link to post Share on other sites More sharing options...
jorlando Posted September 12, 2013 Report post Posted September 12, 2013 If you look under the General Tab for Configuration Manger in the Control Panel there is a Client Certificate value. What does that say? I know you have tried to setup with HTTP or HTTPS, but I am wondering if the client is configured for PKI. When you set the MP to HTTP the client may still be trying to use PKI. And if you set the MP to HTTPS maybe the PKI infrastructure is not properly setup. Would start with HTTP and make sure the Client is configured for that. Quote Share this post Link to post Share on other sites More sharing options...
Andev Posted June 10, 2014 Report post Posted June 10, 2014 Hello, did you solve this problem? I have a same issue. Quote Share this post Link to post Share on other sites More sharing options...
Vishwa Posted October 3 Report post Posted October 3 Hi, Did anyone solve this. Getting same error after migrated to new hardware (New hardware created with same Hostname and IP address) Quote Share this post Link to post Share on other sites More sharing options...