Symptoms
If an application installation is in progress when ccmsetup upgrades the Microsoft System Center Configuration Manager client, the application installation may fail post-upgrade.
Note New application deployments are not affected.
For applications that have their content request data deleted, application installations fail, and the following error message is logged in the AppEnforce.log file:
++++++ Failed to enforce app. Error 0x87d01106.
++++++ AppEnforce date time 8128 (0x1FC0)Cause
This issue occurs because the content request data is deleted during the upgrade because of a schema change.
The following class tracks content requests that are made during an application installation. This class is deleted during a client upgrade:
root\ccm\softmgmtagent:DownloadContentRequestEx2
Is my environment affected?
To determine whether this issue exists in your environment, run the following query on your site server database:
select cia.AssignmentName, col.CollectionName from CI_CurrentErrorDetails ced
join CI_ConfigurationItems ci on ci.CI_ID = ced.CI_ID
join CI_AssignmentTargetedCIs cat on cat.CI_ID = ci.CI_ID
join CI_CIAssignments cia on cia.AssignmentID = cat.AssignmentID
join Collections_G col on col.CollectionID = cia.TargetCollectionID
where ced.ErrorCode in ( -2016407290)
group by cia.AssignmentName, col.CollectionName
If the query returns results that resemble the following, your environment is affected.
AssignmentName |
CollectionName |
Adobe via CMD_All Systems_Install |
All Systems |
Resolution
This issue is fixed in the globally available version of 1702 and in the following update for 1702 first wave:
4018732 Update for System Center Configuration Manager version 1702, first wave
Note This update will prevent the issue that is mentioned in the "Symptoms" section from occurring when ccmsetup upgrades the Configuration Manager client. However, if the issue has already occurred, this update will not fix the issue. To fix the issue after it has occurred, follow the steps that are listed in the "Workaround" section.
Workaround
To work around this issue, use one of the following methods:
-
Untarget and retarget the affected applications.
-
Use a RunOnce cleanup task immediately after the upgrade completes. To do this, follow these steps:
-
Create a software distribution package and program by using the following command: powershell -executionpolicy bypass -noprofile -command "& {$query=gwmi -class CCM_CITask -namespace root\ccm\citasks; $query| rwmi}"
-
Set the installation to run one time (preferably when no users are logged on).
-
Deploy to all affected systems.
-
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Affected products
This article also applies to:
-
Microsoft System Center Configuration Manager (current branch - version 1702)