internet clients failing to install updates/autoupgrade via CMG after CM upgrade to v2303

JG 396 Reputation points
2023-08-31T15:32:40.35+00:00

I upgraded CM v2203 to v2303 on 1st August. I have a CMG and all was working as expected before this upgrade- client on the internet would pickup software updates policy from the CMG and download and install software updates from MS and all was working as expected.

On 1st August i installed v2303 +hotfix rollup KB21010486

since then (i have 4 machines that i am looking at and were working as expected prior to upgrade) these internet only based machines are not installing updates. The CMG is working fine as i can request a hw scan (via client notification) and these clients are appearing online in the console using the cmg

I orginailly had my new client version in pre-prod but have now made it the production client.

These 4 internet based clients- none of them are installing updates or updating their client version via automatic upgrade. (I thought that the CMG supported client upgrade.)

error in updatesdeplyment log show: GetUpdateInfo - failed to get targeted update, error = 0x87d00215.

all these clients are showing as client check passed/active in the deployments monitoring ( so it seems they are not downloaing the new policy for new updates)

I then enabled the CMG as a CDP and checked that the client package is there (even updated the DPs) and also deployed a small test package to test the CDP.

I have enabled using a CDP in the client settings for these machines.

i can see the package in software centre, but when i try and run it it says :The software could not be found on any servers at this time. (Not sure if this issue is realted because the client is having issues communicating with the site)

it seems that the old client (v2203) isnt communicating with the new site v2303 somehow

included attached are snippets from some of the logs (sanitized)

Please help- it seems like a bug and these internet based clients are not installing updates

thanks

cmgissue.txt

Microsoft Security | Intune | Configuration Manager | Other
{count} votes

Accepted answer
  1. Anonymous
    2023-09-26T13:42:09.4566667+00:00

    I created a MS support case for this issue, but found this threads on Reddit today:

    https://www.reddit.com/r/SCCM/comments/14zit9o/upgraded_to_2303_and_updates_are_stuck_i
    https://www.reddit.com/r/SCCM/comments/16jfypn/cmg_and_clients_not_in_boundary_groups_cant/

    User's image

    Have tested it and it has solved our issue, waiting now for confirmation of MS if that is the right way to fix it.

    2 people found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. XinGuo-MSFT 22,231 Reputation points
    2023-09-01T07:48:57.4733333+00:00

    Hi,

    It appears that you are facing issues with your internet-based clients not installing updates or upgrading their client version after upgrading Configuration Manager to v2303.

    Client is on internet	ccmsetup	29/08/2023 09:13:26	17832 (0x45A8)
    Client is set to use webproxy if available.	ccmsetup	29/08/2023 09:13:26	17832 (0x45A8)
    Client is not allowed to use or doesn't have PKI cert while talking to HTTPS server.	ccmsetup	29/08/2023 09:13:26	17832 (0x45A8)
    [CCMHTTP] ERROR: URL=https://CMG01/CCM_Proxy_MutualAuth/ServiceMetadata, Port=0, Options=1216, Code=0, Text=CCM_E_NO_CLIENT_PKI_CERT	ccmsetup	29/08/2023 09:13:26	17832 (0x45A8)
    

    The error message "Client is not allowed to use or doesn't have PKI cert while talking to HTTPS server" suggests that there is an issue with the client's ability to authenticate with an HTTPS server that requires a Public Key Infrastructure (PKI) certificate for secure communication.



  2. XinGuo-MSFT 22,231 Reputation points
    2023-09-05T07:21:24.3666667+00:00

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".


  3. JG 396 Reputation points
    2023-09-12T13:05:56.59+00:00

    OK- so there's an update. I had to update the certificate for my CMG and that recreates the VM. Since then, 2 of my test clients have updated their client version over the CMG. (i manually updated one (which wasnt updating but did that to check if it was an issue with getting software updates) client, but one other still hasnt updated

    However, They are all still giving the same error with updates-

    GetUpdateInfo - failed to get targeted update, error = 0x87d00215. UpdatesDeploymentAgent 12/09/2023 12:58:15 3040 (0x0BE0)

    *spUpdatesManager->GetUpdateInfo((*it).sUpdateId, (it).sVersion, eUpdateState, eApplicability, eUpdateStatus, bIsSuperseded, hrError), HRESULT=87d00215 (K:\dbs\sh\cmgm\0405_083130\cmd\x\src\client\UpdatesMgMt\DeploymentAgent\updatesassignment.cpp,1189) UpdatesDeploymentAgent 12/09/2023 12:58:15 3040 (0x0BE0)

    GetTargetedUpdate( sUpdateId, spManageUpdate ), HRESULT=87d00215 (K:\dbs\sh\cmgm\0405_083130\cmd\x\src\client\UpdatesMgMt\DeploymentAgent\updatesmanager.cpp,1365) UpdatesDeploymentAgent 12/09/2023 12:58:15 3040 (0x0BE0)

    I have just logged into the VPN on one test client and done a scan and deployment evaulation and immediately its picked up the updates its supposed to- so it appears that after the upgrade to 2303 clients dont seem to be picking up software update policies(actionable?) through the CMG.

    This means that clients are now not installing security updates when not on LAN/VPN

    These clients all worked off LAN/VPN before the upgrade fine and CMG connection analyser is good

    .... and on another (less important) note -none of them are pulling my software package (notepad++) from the Cloud DP either

    Its distributed to the CDP, clients have the setting enabled in clients settings to use CDP but when i try and run it it says this:

    LS Request CorrelationID {549CC2E5-3CB8-473A-9369-AB7390A5707B} - LSSendLocationRequestSync sending location request message ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    LS Request CorrelationID {549CC2E5-3CB8-473A-9369-AB7390A5707B} - No reply received for location request ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    hr, HRESULT=80004005 (K:\dbs\sh\cmgm\0405_083130\cmd\1d\src\Framework\LocationServices\LSInterface\ccmpkglocation.cpp,196) ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    LS Request CorrelationID {549CC2E5-3CB8-473A-9369-AB7390A5707B} - Failed to create Location Request Message body ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    RequestLocationsSync(sContentID, sContentVersion, Type, ulPriority, ui64DeploymentFlags, ulTimeoutMilliseconds, ulClientInOperation, pl, paDP, pContentInfo), HRESULT=80004005 (K:\dbs\sh\cmgm\0405_083130\cmd\1d\src\Framework\LocationServices\LSInterface\ccmpkglocation.cpp,609) ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    spICCMPkgLocation->GetLocationsSyncEx3( pwszContentId, pwszContentVersion, eContentType, dwLSPriority, ui64DeploymentFlags, dwLocationTimeoutInSeconds1000, 0xFFFFFFFF, &ulDPCount, &paDP, pContentInfo), HRESULT=80004005 (K:\dbs\sh\cmgm\0405_083130\cmd\m\src\client\SoftMgmtAgent\ContentAccess\ContentAccessService.cpp,1393) ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)*

    GetLocationSyncEx3 for content 00100430.3 failed with error 0x80004005 ContentAccess 12/09/2023 13:39:50 17596 (0x44BC)

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.