Help installing SCCM Agent

Question

We are trying to figure out why we aren't able to install the SCCM Agent on some of our systems. The errors we found in the logs haven't helped us resolve this ourselves.

Running on platform X64 ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Updated security on object C:\Windows\ccmsetup\cache. ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Launch from folder C:\Windows\ccmsetup\ ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
CcmSetup version: 5.0.9078.1005 ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
In ServiceMain ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 0 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
[DHICKMAN-W10] Running on 'Microsoft Windows 10 Pro' (10.0.19044). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ignoreskipupgrade /config:MobileClient.tcf ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
SslState value: 224 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMHTTPPORT: 80 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMHTTPSPORT: 443 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMHTTPSSTATE: 1248 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMHTTPSCERTNAME: ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
FSP: ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMCERTSTORE: MY ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMFIRSTCERT: 1 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CCMPKICERTOPTIONS: 1 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
MANAGEDINSTALLER: 0 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin searching client certificates based on Certificate Issuers ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Completed searching client certificates based on Certificate Issuers ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin to select client certificate ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
1 certificate(s) found in the 'MY' certificate store. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Only one certificate present in the certificate store. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin validation of Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' is self-signed and not valid for ConfigMgr usage. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Completed validation of Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Failed to read assigned site code from registry. Error code = 0x80070002 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Unable to load profiler: 0x80070002 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=COV))' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
OperationalXml '<ClientOperationalSettings><Version>5.00.9078.1000</Version><SecurityConfiguration><SecurityModeMask>1024</SecurityModeMask><SecurityModeMaskEx>1248</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><PKICertOptions>1</PKICertOptions><SiteSigningCert>308202F7308201DFA00302010202106ED568D9278DFBBD41CCAD756C7FD058300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3138313032313139303833325A180F32313138303932383139303833325A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100EE205CFA9326BE6D29010B287D97E7E535245F426EFA0BB37A15796F6AFE58DB0B17A0953C6E217AE56FFAB8FF5C61895662F3412D8C46245F0DABACE2B12E5A57B8BD6A9057175A48CFD41A5A9B93C2CC06A7E3A9CCF8CD5CE9D3BDD7101640A4767CD13EBA9FD2E6774D4BA79086FCC130BF19F152BC38784219762571394494654DB6F592BCA373B21621C52B2F7A273D4D69A8BEBF8F9E18F7EDEA23841799821657511275EDF29B7402B05B54AC2F82C6B7F673963AE879ACDAE95B2720DD5F689A87933BA9C5BA3CC97F77387FE32C51F7FC7909B9558DDFE6EE16516140DF04B103B02A88541FBA4C7ED6689EB2825AD4E6067C64609B4CFA4B02BD9D0203010001A33F303D30250603551D11041E301C821A43564E545554494C49545930312E636F76656E7472792E6E657430140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100622B6ED9C487D8E686F4DE7DD1A0C57BE2E827F8AA8F8436BFC921EC29551860CEA8A13C74C7729192E9EE29B7EC72313092493C794FCF834A01F7313E992071BCFDFDE6A61C33175ED7A0E5C92E2D74201DF371BCD41183C896659A1999255A0B962C88CF641D576728A1E0A806CAFA6D52D280D60AE0D4788F4C8BFD254697D93BF6793B26F2C7643FF522BABE25B42794693B3E9413077FB0E9AD95CA431AFDF0ADE6D4576F7A833415D73B786C6284A1490600170A754D099D9FDB1311CD67E0003DEF8EAC8F126B7D0FD0E9F642A5B4F6B05A65CD0C7AD129FD5C76D98AFB39616951FA07D3D7AFD27E622152220B34BA6C0A9937042D541E52CAD2A978</SiteSigningCert></SecurityConfiguration><RootSiteCode>COV</RootSiteCode><CCM> <CommandLine>SMSSITECODE=COV</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState" Value="63" /></Capabilities><Domain Value="coventry.net" /><Forest Value="coventry.net" /><AADConfig Version="1.0"><Tenants><Tenant ID="F9830C34-73CC-4F6F-B7D6-D4B870D50E17" Name="coventry" UserAuthReady="1"><ResourceUri>https://ConfigMgrService</ResourceUri><ClientId>ce7dde25-8da1-4ba2-91e6-3548f4d57db2</ClientId><ClientReplyUrl>ms-appx-web://Microsoft.AAD.BrokerPlugin/ce7dde25-8da1-4ba2-91e6-3548f4d57db2</ClientReplyUrl><AuthUrl>https://login.microsoftonline.com/</AuthUrl></Tenant></Tenants></AADConfig></ClientOperationalSettings>' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
The MP name retrieved is 'CVNTUTILITY01.coventry.net' with version '9078' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
MP 'CVNTUTILITY01.coventry.net' is not compatible ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Retrieved 0 MP records from AD for site 'COV' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
WPJ Certificate not found ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Device is not AAD joined. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Updating AAD onboarding info to ClientAppId '', ResourceUri '', AADAuthUrl '', UserAuthReady 1 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Persisted AAD on-boarding info. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
FromAD: command line = SMSSITECODE=COV ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Local Machine is joined to an AD domain ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Current AD forest name is coventry.net, domain name is coventry.net ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Domain joined client is in Intranet ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CMPInfoFromADCache requests are throttled for 01:07:09 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Successfully refresh bootstrap information from AD. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin searching client certificates based on Certificate Issuers ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Completed searching client certificates based on Certificate Issuers ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin to select client certificate ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
1 certificate(s) found in the 'MY' certificate store. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Only one certificate present in the certificate store. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Begin validation of Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' is self-signed and not valid for ConfigMgr usage. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Completed validation of Certificate [Thumbprint EF65F557A7A9F1465E758A53F9322457F311FFD8] issued to 'DHICKMAN-W10' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
MP 'HTTPS://CVNTUTILITY01.coventry.net' is HTTPS. Client does not allow to use PKI issued cert and is not AAD capable. Ignoring this MP. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Looking for MPs from AD... ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CMPInfoFromADCache requests are throttled for 01:07:09 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
WPJ Certificate not found ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Device is not AAD joined. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Updating AAD onboarding info to ClientAppId '', ResourceUri '', AADAuthUrl '', UserAuthReady 1 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Persisted AAD on-boarding info. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
FromAD: command line = SMSSITECODE=COV ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Current AD forest name is coventry.net, domain name is coventry.net ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Domain joined client is in Intranet ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
CMPInfoFromADCache requests are throttled for 01:07:09 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
No valid source or MP locations ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Sending state '322'... ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2147500037 ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
[] Params to send '5.0.9078.1005 Deployment "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ignoreskipupgrade /config:MobileClient.tcf' ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
A Fallback Status Point has not been specified and no client was installed. Message with STATEID='322' will not be sent. ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Failed to send status 322. Error (87D00215) ccmsetup 7/6/2022 2:26:50 PM 20576 (0x5060)
Failed to connect to policy namespace. Error 0x8004100e ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Sending state '301'... ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2147500037 ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)
CcmSetup failed with error code 0x80004005 ccmsetup 7/6/2022 2:26:50 PM 27148 (0x6A0C)

Answer 1

"No valid source or MP locations"

Based on your installation line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ignoreskipupgrade /config:MobileClient.tcf "

You are NOT explicitly defining a Management Point or Source. That's perfectly fine... if this client is joined to the domain, your company HAS extended the active directory schema for CM, and your CM infrastructure servers have rights to YourDomain/System/System Management container... so your environment can properly update the entries in that location.

You see, clients on that same domain, 'in general' will ask active directory "ok, so... what Management Point should I use?" Start there... the log to look at is SiteComp.log on your Server, you should see it referencing the System Management container.

If that all looks perfectly lovely... my next guess is boundaries. Boundaries are something that can be easily misconfigured (or not configured at all). It's possible the former employee was only "testing" ?? and only added in boundaries for a test / pilot location? But this is just a wild guess....