Client initialization RegTask Error

Question

Hello,
new year, new problems :-)
After a client of mine upgraded his VMware environment and moved the ConfigMgr Servers, he's been having trouble with his ConfigMgr environment. The main problem being an utterly slow OSD. He has a ConfigMGr 2012 R2 CU3 environment with all needed Patches
and Updates installed. 
So what's the problem? During a Tasksequence, after the client installation step (on a Win7 SP1 Enterprise x86 system), the client needs about 30 Minutes to initialize. I was able to track down the error in ClientIDManagerStartup.log - the client cannot
register itself with the MP: "RegTask: Failed to send registration request message. Error: 0x8000000a"
After n retries, the client can suddenly register and the tasksequence continues, until the next reboot causes the next client initialization. 
I initially checked the Primary Site Server and found out that the customer had activated HTTPS only without adding any kindof PKI certificate. I switched everything back to HTTP but that did not solve the problem.
I've checked google and I've found a couple of blogs describing the same or similar problems:
Blog #1
Blog #2
When querying the Primary Site for MP information, as stated on Blog #2, the Primary Site responds with both MPs in the customers environment as follows:
- <MPList>
- <MP Name=”server.corp.domain.com” FQDN=”server.corp.domain.com“>
<Version>7958</Version>
- <Capabilities SchemaVersion=”1.0“>
<Property Name=”SSLState” Version=”0″ />
</Capabilities>
</MP>
</MPList>
I have also added the parameters SMSMP=server.corp.domain.com and SMSDIRECTORYLOOKUP=NOWINS, but that hasn't changed anything either.
At this point, the only other advice I've found, is to uninstall the MP and reinstall it. I'm reluctant to do this, as we're working in a productive environment and I'd rather try something more subtle, than breaking out the sledge hammer...
I've no idea whtat else to try at the moment. Does anyone here have any ideas?
Thanks,
Fred

Answer 1

Short Update on this one:
I've installed a completely new ConfigMgr 2012 R2 CU3 Environment on a brand new Server 2012 R2 in the customer's environment. The SQL Server is a stand alone server also running on Server 2012 R2, with SQL Server 2012 SP1. Communication between both Site
Servers is fine, I can run a build & capture TS on a VM (vSphere 5.5) without any problems.
Only common component between the "old" and "new" ConfigMgr is Active Directory. I double checked that it's been correctly extended and also checked the System Management Container entries - no problems. Checking the MP response via "http://<MP
name>/sms_mp/.sms_aut?mplist" & "http://<MP name>/sms_mp/.sms_aut?mpcert" shows a correct response, as stated above.
However, as soon as I try to install a Notebook (in this case an HP EliteBook 840 G1) with Windows 7 (fully patched image), I still get the above "error"... right now I'm not really sure what to check... I'll be completing the following tests tomorrow:
- Install different Notebook Model
- Change Server NIC to E1000 (from VMXNET3)
I'll keep this thread updated, but am also thankful for any input on this matter.
Cheers,
Fred