Definitely WMI related. Using the Error lookup feature in CMTrace, 0x80040154 translates to “Class not registered”.
Nice function Jeff, I’ll try it out next time I have WMI issues. While nuking it from orbit is the only way to be sure, sometimes a more surgical approach can help too. Thanks. Todd From: [email protected] [mailto:[email protected]] On Behalf Of Krueger, Jeff Sent: Friday, June 5, 2015 7:57 AM To: [email protected] Subject: RE: [mssms] Problem getting a client registered Instead of going to the nuclear option and blowing away the repository first, try running mofcomp. When clients won’t register (usually see errors in ClienIDStartupManager.log) we’ve had pretty good success with repairing WMI by running mofcomp with the below script. Function FixWMI (){ Set-Service -Name Winmgmt -StartupType Disabled Stop-Service -Name Winmgmt -Force $wbem = 'C:\Windows\System32\wbem' Set-Service -Name Winmgmt -StartupType Automatic Start-Service -Name Winmgmt Start-Sleep -Seconds 10 $mofget = Get-ChildItem -Path $wbem -Name '*.mof' Foreach ($mof in $mofget) { & c:\windows\system32\wbem\mofcomp.exe "$wbem\$mof"} } From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, June 4, 2015 7:22 PM To: '[email protected]' Subject: RE: [mssms] Problem getting a client registered If the ccmexec key is missing is definitely not getting policy. Perhaps corrupt wmi? Blow away the CCM repository. -----Original Message----- From: Heaton, Joseph@Wildlife [[email protected]<mailto:[email protected]>] Sent: Thursday, June 04, 2015 06:59 PM Eastern Standard Time To: '[email protected]' Subject: RE: [mssms] Problem getting a client registered Looking at HKLM\Software\Microsoft\CCM, there is no CcmExec key, nor a ProvisioningMode value. I pushed the client from SCCM console. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, June 04, 2015 3:39 PM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] Problem getting a client registered Provisioning mode? -----Original Message----- From: Heaton, Joseph@Wildlife [[email protected]<mailto:[email protected]>] Sent: Thursday, June 04, 2015 05:55 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: [mssms] Problem getting a client registered SCCM 2012 SP1 ~3200 clients – only having this problem with one client. I have a laptop that a field support called me about today. Look it up in SCCM, and it shows that it has been Inactive for 323 days. It belongs to a scientist, who is in the field a lot. However, she does log into the network from home, through our VPN, so it doesn’t make sense that it hasn’t been talking back to the server. I decide to do a complete uninstall/reinstall, just because that usually clears up pretty much any problem I’m having, and it doesn’t take that long. After the reinstall, it still doesn’t look like it is completing the registration process. In the client window, it is only showing 2 actions on the actions tab, and on the components tab, they’re all showing Installed, but not Enabled. So, I start looking at logs. From the ClientIDManagerStartup.log: [RegTask] - Client is not registered. Sending registration request for GUID: RegTask: Failed to send registration request message. Error: 0x80040154 RegTask: Failed to send registration request. Error: 0x80040154 [RegTask] - Sleeping for 240 seconds ... From the LocationServices.log: Attempting to retrieve local MPs from the assigned MP Current AD site of machine is Stockton Failed to send management point list Location Request Message to HQSCCM…. Current AD site of machine is Stockton Failed to send portal info Location Request Message From the CCMMessaging.log: Error obtaining message hook object 'zlib-compress'. Code 0x80040154 ***This is repeated every 2 minutes*** From ccmperf.log: Failed to add instance _Total Failed to add instance UpdatesDeploymentAgent Failed to add instance UpdatesDeploymentAgent Failed to add instance _Total Failed to add instance ScanAgent Failed to add instance ScanAgent Failed to add instance PeerDPManager Failed to add instance _Total Failed to add instance SrcUpdateMgr Failed to add instance SrcUpdateMgr Failed to add instance _Total Failed to add instance PwrMgmt Failed to add instance PwrMgmt Failed to add instance _Total Failed to add instance LS_ReplyLocations Failed to add instance LS_ReplyLocations Failed to add instance _Total Failed to add instance CIDownloaderDtsReply Failed to add instance CIDownloaderDtsReply Failed to add instance CIStore Failed to add instance _Total Failed to add instance BgbAgent Failed to add instance BgbAgent Failed to add instance _Total Failed to add instance CertificateMaintenanceEndpoint Failed to add instance CertificateMaintenanceEndpoint Failed to add instance _Total Failed to add instance OOBMgmt Failed to add instance OOBMgmt Failed to add instance _Total Failed to add instance PolicyAgent_PolicyDownload Failed to add instance PolicyAgent_PolicyDownload Failed to add instance _Total Failed to add instance SWMTRReportGen Failed to add instance SWMTRReportGen Failed to add instance _Total Failed to add instance PolicyAgent_PolicyEvaluator Failed to add instance PolicyAgent_PolicyEvaluator Failed to add instance _Total Failed to add instance InventoryAgent Failed to add instance InventoryAgent Failed to add instance _Total Failed to add instance MtrMgr Failed to add instance MtrMgr Failed to add instance _Total Failed to add instance StateMessageManager Failed to add instance StateMessageManager Failed to add instance _Total Failed to add instance CTMDTSReply Failed to add instance CTMDTSReply Failed to add instance _Total Failed to add instance execmgr Failed to add instance execmgr Failed to add instance LS_NetworkConfig Failed to add instance _Total Failed to add instance PolicyAgent_RequestAssignments Failed to add instance PolicyAgent_RequestAssignments Failed to add instance RebootCoord Failed to add instance SrvWinMgr Failed to add instance _Total Failed to add instance ClientRegistration Failed to add instance ClientRegistration Failed to add instance _Total Failed to add instance EndpointProtectionAgent Failed to add instance EndpointProtectionAgent Failed to add instance _Total Failed to add instance LS_ScheduledCleanup Failed to add instance LS_ScheduledCleanup Failed to add instance PolicyAgent_ReRequestPolicy Failed to add instance _Total Failed to add instance PolicyAgent_Cleanup Failed to add instance PolicyAgent_Cleanup Failed to add instance _Total Failed to add instance DCMAgent Failed to add instance DCMAgent Failed to add instance CITaskMgr Failed to add instance RemoteToolsAgent Failed to add instance _Total Failed to add instance ExternalEventAgent Failed to add instance ExternalEventAgent Failed to add instance SCUpdateMgr Failed to add instance updatesmgr Failed to add instance _Total Failed to add instance UpdateStore Failed to add instance UpdateStore Failed to add instance SCEndpoint Failed to add instance _Total Failed to add instance PolicyAgent_ReplyAssignments Failed to add instance PolicyAgent_ReplyAssignments Failed to add instance _Total Failed to add instance SMSSHA Failed to add instance SMSSHA I’ve Googled most of these errors, with no luck. I’ve checked the local Windows Firewall: it has the rule that we push out through GP, that allows pretty much anything to and from the PC, to and from the SCCM Primary server. The Primary site server is a local admin on the box. DNS records are accurate, including PTR record. Everything that we normally see hasn’t been the issue with this one. I’m pretty much at a loss at this point. Any ideas? Thanks, Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284 Every Californian should conserve water. Find out how at: [SaveOurWater_Logo]<https://urldefense.proofpoint.com/v2/url?u=http-3A__saveourwater.com_&d=AwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=clN79r1X96OAvT4RttcbL_b7tYJewO0Zp90IOsShfmE&s=WR6KsVy_OYNbVDhmTq2PvVqgeIsMueomTMVghXLAcBI&e=> SaveOurWater.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__saveourwater.com_&d=AwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=clN79r1X96OAvT4RttcbL_b7tYJewO0Zp90IOsShfmE&s=WR6KsVy_OYNbVDhmTq2PvVqgeIsMueomTMVghXLAcBI&e=> · Drought.CA.gov<https://urldefense.proofpoint.com/v2/url?u=http-3A__drought.ca.gov_&d=AwMGaQ&c=aLnS6P8Ng0zSNhCF04OWImQ_He2L69sNWG3PbxeyieE&r=pQGVi_ygWZb0EWR_EeMFzgKJCQ8AFTQI7Ck6iiIPItI&m=clN79r1X96OAvT4RttcbL_b7tYJewO0Zp90IOsShfmE&s=fre8pWyN5VSc6GgxRdLctdyQKjDiUVzQ1rCynePh2zs&e=> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by reply email, delete the email from your computer system and shred any paper copies. Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. See our Privacy & Security page on www.henryford.com<http://www.henryford.com> for more detailed information as well as information concerning MyChart, our new patient portal. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
