Release Notes
In brief
The release notes now document task sequence status-message failures after Windows PE when boot media uses CNG/KSP certificates, and content download failures with HTTP 403.7 from PKI HTTPS distribution points. Workarounds and diagnostic details were added.
What Intune admins need to know
Affected administrators should recreate boot media with a legacy CSP-backed RSA certificate. For distribution point issues, temporarily adjust IIS client-certificate settings for diagnosis and do not leave enforcement disabled.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
To resolve this issue, install the update rollup for Configuration Manager version 2603 (KB39169655) or update to Configuration Manager version 2609, which also includes this fix.
OS deployment
Task sequence status messages fail in the full OS with CNG/KSP boot media certificates
Applies to: version 2609
After you upgrade to Configuration Manager version 2609, task sequences that use boot media with an imported public key infrastructure (PKI) certificate backed by a Cryptography Next Generation (CNG) key storage provider (KSP) might fail to send status messages after restarting from Windows PE into the full Windows OS.
smsts.log records error 0x80072f9a (ERROR_WINHTTP_CLIENT_CERT_NO_ACCESS_PRIVATE_KEY). Each failed attempt to send a status message is retried, adding delays to OS deployment. The Windows PE phase isn't affected.
To work around this issue, import the certificate's private key into a legacy cryptographic service provider (CSP), export the certificate and private key to a new Personal Information Exchange (PFX) file, and recreate the bootable media.
Use an RSA certificate with an exportable private key. Protect the PFX files and their passwords from unauthorized access.
Open a Command Prompt window in the folder that contains the original PFX file. Run the following command to import the certificate into the current user's Personal certificate store by using the Microsoft Enhanced RSA and AES Cryptographic Provider:
certutil -user -csp "Microsoft Enhanced RSA and AES Cryptographic Provider" -p "<pfxpassword>" -importPFX My boot-media-original.pfxReplace
<pfxpassword>with the original PFX file's password andboot-media-original.pfxwith its file name.Run
certmgr.mscto open the certificate management console for the current user. Expand Personal, and then select Certificates.Right-click the imported certificate, select All Tasks, and then select Export. In the Certificate Export Wizard, select Next.
Select Yes, export the private key, and then select Next. Select Personal Information Exchange - PKCS #12 (.PFX) and Include all certificates in the certification path if possible, and then select Next.
Select Password, enter and confirm a strong password, and then select Next. Specify a new file name, such as
boot-media-legacy-csp.pfx, select Next, and then select Finish.Verify the exported PFX file by running the following command. Replace
<pfxpassword>with the new PFX file's password:certutil -p "<pfxpassword>" -dump boot-media-legacy-csp.pfxVerify that the provider is Microsoft Enhanced RSA and AES Cryptographic Provider before you use the certificate to create media.
Create new bootable media. On the Security page of the Create Task Sequence Media Wizard, select Import PKI certificate and specify the new PFX file
boot-media-legacy-csp.pfxand its password. Use the new media for subsequent deployments.
For more information, see certutil and Export a certificate with its private key.
Content management
Content downloads fail with HTTP 403.7 from PKI HTTPS distribution points
Applies to: version 2609
After you upgrade to Configuration Manager version 2609, clients and pull-distribution points might fail to download content from HTTPS distribution points that use public key infrastructure (PKI) certificates. Downloads can fail even when the downloading client or pull-distribution point has a valid client certificate.
The source distribution point's IIS log records HTTP status 403.7. DataTransferService.log and, for pull-distribution points, PullDP.log can record error 0x80190193. Not all downloads are affected; connections that have already negotiated a valid client certificate might succeed.
To identify whether a failed content download is affected by this issue, update the SSL settings on the affected distribution point and retry the download:
Important
This procedure briefly changes client certificate enforcement. Don't leave Client certificates set to Accept.
- On the affected distribution point server, open Internet Information Services (IIS) Manager as an administrator.
- In the Connections pane, expand the server, expand Sites, and then expand the website that hosts the distribution point virtual directories. Select SMS_DP_SMSPKG$.
- In Features View, double-click SSL Settings.
- On the SSL Settings page, verify that Require SSL is selected. Under Client certificates, select Accept, and then select Apply in the Actions pane.
- Under Client certificates, select Require, and then select Apply in the Actions pane. Keep Require SSL selected.
- Select the SMS_DP_SMSSIG$ virtual directory and repeat steps 3 through 5.
- Retry the previously failed content download from the same distribution point. If the download succeeds after you apply these settings, this result confirms the issue described in this release note.
This change isn't permanent. Configuration Manager reapplies the affected settings every 48 hours and when the distribution point is reconfigured or upgraded.
For more information, see Configure client certificates in IIS.
Client authentication and registration
Microsoft Entra token validation fails when the management point can't access the internet
Cloud services
CMG update to version 2609 fails when Azure permissions or resource provider registration are missingshared key access changes
Applies to: version 2609 updates with an existing cloud management gateway
Starting in version 2609, Configuration ManagerVersion 2609 automatically disables shared-shared key access for cloud management gateway (CMG)CMG storage. Existing CMGsThe CMG enhanced security workflow prepares the Azure prerequisites and configures the content uploader to use Microsoft Entra authentication instead of shared key authentication.
Before updating, consider enabling CMG enhanced security with an authorized Azure administrator. For a running virtual machine scale set CMG, use the following steps when the action is available:
- In the Configuration Manager console, go to the Administration workspace, expand Cloud Services, and select Cloud Management Gateway.
- Select the CMG, then select CMG enhanced security. For more information, see CMG enhanced security option.
- Select the appropriate tenant and sign in with an Azure account authorized to assign the required roles at the CMG resource group and register resource providers in the subscription. Select Update and verify that
previously used shared-the workflow completes successfully. - Allow any resulting CMG deployment work and permission propagation to complete. Verify the server application's Azure RBAC permissions and the required resource provider registration.
If you don't enable enhanced security before updating, the transition away from shared key access also requirecan result in either of the following scenarios. Use the symptoms and logs to identify the applicable guidance.
CMG update to version 2609 fails when Azure role-assignment permissions andor resource provider registration for this transition. A successful deployment on an earlier version doesn't confirm that these prerequisites are met.missing
If the CMG server application's service principal can't create the required storage role assignments, theExisting CMG deployment updateupdates can fail.fail if Azure permissions or resource provider registration required for the transition are missing.
To address this failure, verify both prerequisites, even if you've run the CMG enhanced security workflow:
- Azure role-assignment permissions: CloudMgr.log can report HTTP
403,DeploymentFailed, and a deniedMicrosoft.Authorization/roleAssignments/writeaction.MissingMicrosoft.Maintenanceresource provider registration can also causeConfigure thedeployment update to fail.Before updating, verify the CMGserver application'seffectivepermissionsat each CMG resource group. Theas described in Configure Azure RBAC permissions for the server app. Contributorrolealone doesn't grantstoragerole-assignmentpermissions, and the signed-in administrator's permissions don't establish that the CMG application has access. Use the constrained role-assignment configuration described in Configure Azure RBAC permissions for the server app, rather than granting unrestricted administratorpermissions.Also verify that - Microsoft.Maintenance registration: Verify that this resource provider is
registeredRegistered inevery Azureeach subscription that hosts a CMG.Registration in a staging subscription doesn't register the provider in a different production subscription.Have an authorized Azure administrator complete any missing registration. For instructions, see Configure Azure resource providers.
Allow permission changes and registration to complete, then verify the CMG deployment update and client communication. See Verify CMG deployment and client communication.
Content uploads to existing CMGs fail after updating to version 2609
Packages and applications might fail to upload to an existing content-enabled CMG or repeatedly retry. This scenario can affect CMGs created before version 2409 that haven't had enhanced security enabled. The site-side content uploader can continue using shared key authentication after the Azure storage account has disabled it.
Unlike the deployment update failure, content uploads can fail even when the CMG deployment update completes and the Azure prerequisites are met. Previously uploaded content isn't necessarily unavailable to clients.
PkgXferMgr.log can record storage account key retrieval followed by errors similar to the following:
Resource Manager - Key retrieved for storage service
Getting container Ids for StorageAccount: ...
CheckServiceStatus() failed
Failed to distribute content to the cloud DP.
Sending failed. Failure count = ...
The preferred workaround for an affected, running virtual machine scale set CMG is to enable CMG enhanced security, when the action is available, by using the procedure earlier in this section. After the workflow and any resulting deployment work complete, retry content distribution and verify successful package uploads.
Important
This workflow is expected to correct the authentication setting, but recovery hasn't been validated for every affected configuration. The action might be unavailable, including when the CMG is in an error state. If it isn't available or doesn't restore content uploads, contact Microsoft Support for recovery guidance. Don't directly modify the Configuration Manager database or re-enable shared key access in Azure.
\ No newline at end of file
Verify recovery through PkgXferMgr.log and Monitor content you distribute.
\ No newline at end of file
\ No newline at end of file
@@ -16,7 +16,7 @@ ms.reviewer: - hugowu - qiani description: Learn about urgent issues that aren't yet fixed in the product or covered in a Microsoft Support knowledge base article.-ms.date: 2026-11-11T00:00:00.0000000Z+ms.date: 2026-11-16T00:00:00.0000000Z ms.subservice: core-infra ms.topic: release-notes ms.collection: tier3@@ -38,10 +38,10 @@ item_type: Content source_path: intune/configmgr/core/servers/deploy/install/release-notes.md cmProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/4c50f262-d533-4ba4-9d4a-08899ec3a3d1-- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/57eae307-c3a1-4cac-b645-1a899934bac8+- https://authoring-docs-microsoft.poolparty.biz/devrel/bcbcbad5-4208-4783-8035-8481272c98b8 spProducts: - https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/6a8c83be-f1de-4e90-bde0-bd097999a60c-- https://microsoft-devrel.poolparty.biz/DevRelOfferingOntology/ee561821-1ac7-45a8-9409-6ba5eb7a5b97+- https://authoring-docs-microsoft.poolparty.biz/devrel/43b2e5aa-8a6d-4de2-a252-692232e5edc8 platformId: 6d4ce334-3afa-92d0-7981-3abf49ff1bb0 --- @@ -93,6 +93,70 @@ Perfsetup can also exit with code `1000`. The affected component name in the reg
To resolve this issue, install the [update rollup for Configuration Manager version 2603 (KB39169655)](../../../../hotfix/2603/39169655) or update to Configuration Manager version 2609, which also includes this fix.
+## OS deployment
+
+### Task sequence status messages fail in the full OS with CNG/KSP boot media certificates
+
+*Applies to: version 2609*
+
+After you upgrade to Configuration Manager version 2609, task sequences that use boot media with an imported public key infrastructure (PKI) certificate backed by a Cryptography Next Generation (CNG) key storage provider (KSP) might fail to send status messages after restarting from Windows PE into the full Windows OS.
+
+**smsts.log** records error `0x80072f9a` (`ERROR_WINHTTP_CLIENT_CERT_NO_ACCESS_PRIVATE_KEY`). Each failed attempt to send a status message is retried, adding delays to OS deployment. The Windows PE phase isn't affected.
+
+To work around this issue, import the certificate's private key into a legacy cryptographic service provider (CSP), export the certificate and private key to a new Personal Information Exchange (PFX) file, and recreate the bootable media.
+
+Use an RSA certificate with an exportable private key. Protect the PFX files and their passwords from unauthorized access.
+
+1. Open a Command Prompt window in the folder that contains the original PFX file. Run the following command to import the certificate into the current user's **Personal** certificate store by using the **Microsoft Enhanced RSA and AES Cryptographic Provider**:
+
+ ```console
+ certutil -user -csp "Microsoft Enhanced RSA and AES Cryptographic Provider" -p "<pfxpassword>" -importPFX My boot-media-original.pfx
+ ```
+
+ Replace `<pfxpassword>` with the original PFX file's password and `boot-media-original.pfx` with its file name.
+2. Run `certmgr.msc` to open the certificate management console for the current user. Expand **Personal**, and then select **Certificates**.
+3. Right-click the imported certificate, select **All Tasks**, and then select **Export**. In the Certificate Export Wizard, select **Next**.
+4. Select **Yes, export the private key**, and then select **Next**. Select **Personal Information Exchange - PKCS #12 (.PFX)** and **Include all certificates in the certification path if possible**, and then select **Next**.
+5. Select **Password**, enter and confirm a strong password, and then select **Next**. Specify a new file name, such as `boot-media-legacy-csp.pfx`, select **Next**, and then select **Finish**.
+6. Verify the exported PFX file by running the following command. Replace `<pfxpassword>` with the new PFX file's password:
+
+ ```console
+ certutil -p "<pfxpassword>" -dump boot-media-legacy-csp.pfx
+ ```
+
+ Verify that the provider is **Microsoft Enhanced RSA and AES Cryptographic Provider** before you use the certificate to create media.
+7. [Create new bootable media](../../../../osd/deploy-use/create-bootable-media#process). On the **Security** page of the Create Task Sequence Media Wizard, select **Import PKI certificate** and specify the new PFX file `boot-media-legacy-csp.pfx` and its password. Use the new media for subsequent deployments.
+
+For more information, see [certutil](/en-us/windows-server/administration/windows-commands/certutil) and [Export a certificate with its private key](/en-us/windows-server/identity/ad-cs/export-certificate-private-key).
+
+## Content management
+
+### Content downloads fail with HTTP 403.7 from PKI HTTPS distribution points
+
+*Applies to: version 2609*
+
+After you upgrade to Configuration Manager version 2609, clients and pull-distribution points might fail to download content from HTTPS distribution points that use public key infrastructure (PKI) certificates. Downloads can fail even when the downloading client or pull-distribution point has a valid client certificate.
+
+The source distribution point's IIS log records HTTP status `403.7`. **DataTransferService.log** and, for pull-distribution points, **PullDP.log** can record error `0x80190193`. Not all downloads are affected; connections that have already negotiated a valid client certificate might succeed.
+
+To identify whether a failed content download is affected by this issue, update the SSL settings on the affected distribution point and retry the download:
+
+Important
+
+This procedure briefly changes client certificate enforcement. Don't leave **Client certificates** set to **Accept**.
+
+1. On the affected distribution point server, open **Internet Information Services (IIS) Manager** as an administrator.
+2. In the **Connections** pane, expand the server, expand **Sites**, and then expand the website that hosts the distribution point virtual directories. Select **SMS\_DP\_SMSPKG$**.
+3. In **Features View**, double-click **SSL Settings**.
+4. On the **SSL Settings** page, verify that **Require SSL** is selected. Under **Client certificates**, select **Accept**, and then select **Apply** in the **Actions** pane.
+5. Under **Client certificates**, select **Require**, and then select **Apply** in the **Actions** pane. Keep **Require SSL** selected.
+6. Select the **SMS\_DP\_SMSSIG$** virtual directory and repeat steps 3 through 5.
+7. Retry the previously failed content download from the same distribution point. If the download succeeds after you apply these settings, this result confirms the issue described in this release note.
+
+This change isn't permanent. Configuration Manager reapplies the affected settings every 48 hours and when the distribution point is reconfigured or upgraded.
+
+For more information, see [Configure client certificates in IIS](/en-us/iis/application-frameworks/scenario-build-an-aspnet-website-on-iis/configuring-step-4-configure-application-security#client-certificates).
+
## Client authentication and registration
### Microsoft Entra token validation fails when the management point can't access the internet
@@ -175,14 +239,52 @@ Removing SUP role in Admin Console doesn't reset the superseding age property in
## Cloud services
-### CMG update to version 2609 fails when Azure permissions or resource provider registration are missing
+### CMG shared key access changes
*Applies to: version 2609 updates with an existing cloud management gateway*
-Starting in version 2609, Configuration Manager automatically disables shared-key access for cloud management gateway (CMG) storage. Existing CMGs that previously used shared-key access also require Azure role-assignment permissions and resource provider registration for this transition. A successful deployment on an earlier version doesn't confirm that these prerequisites are met.
+Version 2609 automatically disables shared key access for CMG storage. The [CMG enhanced security](../../../plan-design/changes/whats-new-in-version-2409#cmg-enhanced-security-option) workflow prepares the Azure prerequisites and configures the content uploader to use Microsoft Entra authentication instead of shared key authentication.
+
+Before updating, consider enabling **CMG enhanced security** with an authorized Azure administrator. For a running virtual machine scale set CMG, use the following steps when the action is available:
+
+1. In the Configuration Manager console, go to the **Administration** workspace, expand **Cloud Services**, and select **Cloud Management Gateway**.
+2. Select the CMG, then select **CMG enhanced security**. For more information, see [CMG enhanced security option](../../../plan-design/changes/whats-new-in-version-2409#cmg-enhanced-security-option).
+3. Select the appropriate tenant and sign in with an Azure account authorized to assign the required roles at the CMG resource group and register resource providers in the subscription. Select **Update** and verify that the workflow completes successfully.
+4. Allow any resulting CMG deployment work and permission propagation to complete. Verify the server application's [Azure RBAC permissions](../../../clients/manage/cmg/configure-azure-ad#configure-azure-rbac-permissions-for-the-server-app) and the [required resource provider registration](../../../clients/manage/cmg/configure-azure-ad#configure-azure-resource-providers).
+
+If you don't enable enhanced security before updating, the transition away from shared key access can result in either of the following scenarios. Use the symptoms and logs to identify the applicable guidance.
+
+#### CMG update to version 2609 fails when Azure permissions or resource provider registration are missing
+
+Existing CMG deployment updates can fail if Azure permissions or resource provider registration required for the transition are missing.
+
+To address this failure, verify both prerequisites, even if you've run the **CMG enhanced security** workflow:
-If the CMG server application's service principal can't create the required storage role assignments, the CMG deployment update can fail. **CloudMgr.log** can report HTTP `403`, `DeploymentFailed`, and a denied `Microsoft.Authorization/roleAssignments/write` action. Missing **Microsoft.Maintenance** resource provider registration can also cause the deployment update to fail.
+- **Azure role-assignment permissions:** **CloudMgr.log** can report HTTP `403`, `DeploymentFailed`, and a denied `Microsoft.Authorization/roleAssignments/write` action. Configure the server application's permissions as described in [Configure Azure RBAC permissions for the server app](../../../clients/manage/cmg/configure-azure-ad#configure-azure-rbac-permissions-for-the-server-app). **Contributor** alone doesn't grant role-assignment permissions.
+- **Microsoft.Maintenance registration:** Verify that this resource provider is **Registered** in each subscription that hosts a CMG. Have an authorized Azure administrator complete any missing registration. For instructions, see [Configure Azure resource providers](../../../clients/manage/cmg/configure-azure-ad#configure-azure-resource-providers).
+
+Allow permission changes and registration to complete, then verify the CMG deployment update and client communication. See [Verify CMG deployment and client communication](../../manage/checklist-for-installing-update-2609#verify-cmg-deployment-and-client-communication).
+
+#### Content uploads to existing CMGs fail after updating to version 2609
+
+Packages and applications might fail to upload to an existing content-enabled CMG or repeatedly retry. This scenario can affect CMGs created before version 2409 that haven't had enhanced security enabled. The site-side content uploader can continue using shared key authentication after the Azure storage account has disabled it.
+
+Unlike the deployment update failure, content uploads can fail even when the CMG deployment update completes and the Azure prerequisites are met. Previously uploaded content isn't necessarily unavailable to clients.
+
+**PkgXferMgr.log** can record storage account key retrieval followed by errors similar to the following:
+
+```text
+Resource Manager - Key retrieved for storage service
+Getting container Ids for StorageAccount: ...
+CheckServiceStatus() failed
+Failed to distribute content to the cloud DP.
+Sending failed. Failure count = ...
+```
+
+The preferred workaround for an affected, running virtual machine scale set CMG is to enable **CMG enhanced security**, when the action is available, by using the procedure earlier in this section. After the workflow and any resulting deployment work complete, retry content distribution and verify successful package uploads.
+
+Important
-Before updating, verify the CMG server application's effective permissions at each CMG resource group. The **Contributor** role alone doesn't grant storage role-assignment permissions, and the signed-in administrator's permissions don't establish that the CMG application has access. Use the constrained role-assignment configuration described in [Configure Azure RBAC permissions for the server app](../../../clients/manage/cmg/configure-azure-ad#configure-azure-rbac-permissions-for-the-server-app), rather than granting unrestricted administrator permissions.
+This workflow is expected to correct the authentication setting, but recovery hasn't been validated for every affected configuration. The action might be unavailable, including when the CMG is in an error state. If it isn't available or doesn't restore content uploads, contact Microsoft Support for recovery guidance. Don't directly modify the Configuration Manager database or re-enable shared key access in Azure.
-Also verify that **Microsoft.Maintenance** is registered in every Azure subscription that hosts a CMG. Registration in a staging subscription doesn't register the provider in a different production subscription. For instructions, see [Configure Azure resource providers](../../../clients/manage/cmg/configure-azure-ad#configure-azure-resource-providers).\ No newline at end of file+Verify recovery through **PkgXferMgr.log** and [Monitor content you distribute](../configure/monitor-content-you-have-distributed).\ No newline at end of file