Issues with System Center 2012 Configuration Manager Application Evaluation if a third party deployment type is not registered properly on a client

Symptoms

Using System Center 2012 Configuration Manager, an application is targeted with a third party deployment type but application evaluation ceases to process for all application deployments on the client. You may see a generic error similar to the following in the CIAgent.log file:

DCM::LanternUtils::ScopeAndBindPolicies - Failed to start enactment (0x80041010).

There may be other causes for this error that are not related to this issue, but the error code will help to identify the issue described here.

Cause

This can occur if an application is targeted with a third party deployment type and the corresponding handler has not been pre-installed on the machine. In a case such as this, the application evaluation ceases to process all future application deployments on that client.

In this scenario :

  • Deployments of any applications to this machine will not be processed until the third party deployment type handler is deployed, or until all applications with third party deployment types are un-deployed to those machines.
  • Application management can't be used to deploy a third party deployment type until the third party deployment type handler is deployed or the application with the third party deployment types are un-deployed to those machines.

The only way to discover if the client is in this condition is through the Application infrastructure errors Report.

Resolution

To prevent this scenario, all third party deployment type handlers must be pre-deployed to all machines where the corresponding application will be deployed.

 To fix this scenario, either of the following methods can be used:

  • Un-install the offending third-party deployment.  Once the deployment has been removed, pre-deploy the needed deployment type handler prior to the application deployment.
  • Install or register the third-party deployment type handler.  Application Evaluation will begin to work correctly again after the next global deployment re-evaluation cycle.
Properties

Article ID: 2756110 - Last Review: Apr 2, 2015 - Revision: 1

Feedback