Product Documentation

Monitor and troubleshoot

Jun 11, 2014

If you are new to System Center Configuration Manager, be aware that Configuration Manager operations typically take a while and few operations occur immediately. For example:

  • Application deployment can take an hour or more.
  • By default, the Configuration Manager client runs the following operations once a week: Hardware and software inventory, software metering, software updates, and software deployments.
  • By default, the Configuration Manager client checks for new applications and software updates every hour.
Caution: Although you can change Configuration Manager client defaults, make sure that you understand the implications of any changes. For example, increasing the frequency of some operations can result in endpoints running out of memory. Be sure to test all changes in a non-production environment.

To view Configuration Manager client settings, go to Administration > Client Settings.

The Connector synchronization, orchestration, and publishing tasks run on the schedule specified in the Connector configuration wizard Advanced Properties. You can also manually run the Connector tasks from the Start screen or menu.

This section provides information to help you:

  • Monitor application deployment and publishing
  • Use Configuration Manager and Connector log files to troubleshoot a variety of issues
  • Troubleshoot issues related to operational speed and incorrect setup

Monitor application deployment

After you deploy an application, monitor its progress as follows:

  1. In the Configuration Manager console, click Monitoring > Deployments, right-click the application, and then choose View Status.


    Deployment status example

    If the deployment is not yet successful, check the other tabs for status information.

  2. To force a status update for the deployment, click Run Summarization, wait awhile, and then click Refresh.

    After the application deploys, the In Progress tab lists the clones of managed images, with a status of "Waiting For Orchestration."

    This information is also available from the Application Compliance Report in Monitoring > Reporting > Reports > Software Distribution - Application Monitoring.

Monitor application publishing

After you publish an application, monitor its progress in the Properties dialog box for the publication as described in the following steps. This table describes the publishing status messages and how to resolve publishing issues.

Publishing status message Resolution
App is scheduled for publishing to Citrix Delivery Site name. The Citrix Connector will update this status message after processing the application publishing request. The publishing task has not yet run. If this message remains after the publishing task should have completed, verify that the VDA is configured correctly on the session machines.
App did not publish to Citrix Delivery Site name

Reason: The Citrix Connector will publish the application only when all active XenApp or XenDesktop workers that are not in maintenance mode report to Configuration Manager that the application is successfully deployed.

Ensure that the application is successfully deployed to all targeted XenApp or XenDesktop workers. When deploying to an image-managed catalog (MCS or Provisioning Services), use Citrix Studio to update the catalog with the new image after the application is successfully deployed to the designated update device.
App did not publish to Citrix Delivery Site name

Reason: The application is no longer published to a Delivery Group.

Ensure that the application is published to a Delivery Group. Check whether any Delivery Groups to which this publication was previously targeted were subsequently deleted.
App did not publish to Citrix Delivery Site name

Reason: Another publication with the same administrator-facing name already exists in the Citrix Delivery Site name.

Use the XenApp 7.5 and XenDesktop 7.5 Publishing Wizard in the Configuration Manager console to give the new application publication a unique name, or use Citrix Studio to give the existing application publication a unique name.
App did not publish to the Citrix Delivery Site name because the Site does not include the targeted Delivery Groups. The application was published to multiple Delivery Sites and this site does not include the targeted Delivery Groups. The application was not published to the site, as expected. Select other sites for their publishing status.
The publishing task encountered an error when trying to publish App to Citrix Delivery Site name.

Reason: Generic or unknown failure.

To troubleshoot the issue, look at the log on the server where the Connector Service is installed. By default, the log files are located at %ProgramFiles%\Citrix\Connector for ConfigMgr\Connector Service\Logs\.
  1. In the Configuration Manager console, expand Application Management and then click Citrix Application Publications.
  2. Right-click the application you published and review the messages in the Publishing status area of the Properties dialog box.


    Publishing status example

Configure Connector logging

The Connector creates log files for the following:

  • Connector service, Connector agent, and Citrix deployment handler installation
  • Connector service tasks, including orchestration, publishing, and synchronization

    Log files are updated as the tasks run.

The Connector extends the tracing capabilities provided by Configuration Manager by using standard .NET listeners and registering a CDF module. You can use CDFMonitor, the Configuration Manager log viewer tool CMTrace (in C:\Program Files\Microsoft Configuration Manager\tools), or other third-party tools to view trace information. For detailed information about CDFMonitor, refer to CDFMonitor.

Log files are named as follows:

  • ComponentName.CreationTimeStamp.log. For example, log files for the component Citrix.ConfigMgr.PublishingTask.exe are named Citrix.ConfigMgr.PublishingTask.CreationTimeStamp.log.
  • CDF modules use the naming convention ConfigMgr_ModuleName.

Configuration files are located under the Connector installation folder: %ProgramFiles%\Citrix\Connector for ConfigMgr\component\ComponentName.exe.config

To specify logging features, update the following properties in the configuration files:

Property Description
baseFilename Default log file name
enabled Whether a listener is enabled

By default the SMS Provider listener is enabled and the CDF listener is disabled.

appendMode For an existing log file, whether to append log messages or overwrite the file
sizeLimit Maximum file size, in MBs
trailCount Number of time stamped files to retain

Use log files to troubleshoot

The following table lists the Configuration Manager and Connector log files that can help you troubleshoot a variety of issues.

The default installPath to Connector log files is %ProgramFiles%\Citrix\Connector for ConfigMgr.

Issue Log file
Configuration Manager console operation C:\Program Files(x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\SMSAdminUI
Connector Configuration installPath\Config Wizard\Logs\Citrix.ConfigMgr.ConfigWizard
Connector task scheduling installPath\Connector Service\Logs\Citrix.ConfigMgr.XenDesktopConnector
Synchronization with XenApp or XenDesktop installPath\Connector Service\Logs\Citrix.ConfigMgr.SynchronizationTask
Application deployments installPath\Connector Service\Logs\Citrix.ConfigMgr.OrchestrationTask
Application publishing installPath\Connector Service\Logs\Citrix.PublishingTask
On master images and session machines: Group policies; maintenance windows; deployment status installPath\Connector Agent\Logs\Citrix.ConfigMgr.XenDesktopAgent
On master images, session machines, and user devices: Application detection; installation and uninstallation of publications installPath\DT Handler\Logs\Citrix.ConfigMgr.XenDesktopDTHandler

C:\Windows\CCM\Logs\AppDiscovery

C:\Windows\CCM\Logs\AppEnforce

On user devices: Hardware and software inventory C:\Windows\CCM\Logs\InventoryAgent.log
Machine catalog properties, publishing wizard, and other functionality provided by the Connector console extension C:\Program Files(x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\Citrix.ConfigMgr.XenDesktopDT

For more information about Configuration Manager logging, refer to:

Technical Reference for Log Files in Configuration Manager

Configuring Reporting in Configuration Manager

Troubleshoot issues

Issue Description and resolution
The Citrix Delivery Sites folder is missing from Device Collections The Connector console extension is not installed or configured.
After installing the Connector, the synchronization task takes a while and the CPU load on the SQL host increases A machine catalog with more than 1000 machines increases the CPU load as the Connector synchronizes Configuration Manager with the Citrix Delivery Controller.
Connector tasks do not run The Connector service must be able to run with the user credentials specified in the Connector configuration wizard.
  • Verify that the computer on which the Connector service is installed allows storage of passwords and credentials for network authentication.
  • Verify that the computer policy Do not allow storage of passwords and credentials for network authentication is disabled.
Machines are missing from the Assets and Compliance > Devices list Configuration Manager has not discovered the device.

If machine clones are missing from the Devices list, you can force the discovery of new machines by running the AD System Discovery in Configuration Manager:

  1. Navigate to Administration > Hierarchy Configuration > Discovery Methods.
  2. Right-click Active Directory System Discovery and then choose Run Full Discovery Now.

If master images are missing from the Devices list:

  1. Log on to the VM containing the master image.
  2. In the Control Panel open Configuration Manager.
  3. Click the Actions tab, select Hardware Inventory Cycle, and then click Run Now.
Machine catalogs or Delivery Groups are missing from the Configuration Manager console Changes to XenApp or XenDesktop machine catalogs and Delivery Groups do not appear in Configuration Manager until the Connector synchronization task runs.

To update device collections and user collections, run the Citrix Connector 7.5 Synchronization Task located in Citrix > Citrix Connector 7.5 for Configuration Manager under All Programs or Apps.

Refresh the Configuration Manager console to view the synchronized items.

The Machine Catalog count property does not match the device collection member count property These two count properties will not match if provisioned machine clones have not yet booted or if Configuration Manager has not completed synchronizing the device collection.
The virtual desktop properties for a session machine does not include all values If some properties are missing, verify that the machine is assigned to a Delivery Group.

If all properties are missing, review the hardware inventory log (C:\Windows\CCM\Logs\InventoryAgent.log) to discover why the Citrix WMI properties of the VDA are not populated in Configuration Manager.

Although a particular machine is in a machine catalog in Studio, it does not appear in the machine catalog collection in the Configuration Manager console In the Configuration Manager console, verify that the machine is listed in Assets and Compliance > Devices and that the Configuration Manager client is installed and active on the machine. The Connector synchronization task log may contain additional helpful information, such as the log message: Not adding XenApp/XenDesktop Worker machine name to collection machine catalog collection name because it is currently not in the "All Systems" collection.
After choosing a device or user collection in the Deploy Software Wizard, this message appears: The selected collection name does not contain any members If you chose a device collection, the message indicates that there are no machines assigned to the machine catalog. If you chose a user collection, the message indicates that there are no users assigned to the Delivery Group.

Use Studio to complete the configuration.

In the Deployment Status page, the Requirements Not Met tab includes the requirement Existential of Citrix XenApp Server Version Not Equal to 0 This status indicates that you used a deployment type that includes a Requirement with the global condition named Citrix XenApp Server Version. That global condition forces the application to install on the XenApp 6.5 farm and so is not valid for deployment to a Citrix Delivery Site.

Edit the deployment type for the application to remove the XenApp-specific global condition.

The Designate Update Device verification does not complete because Configuration Manager cannot contact the device If Configuration Manager cannot contact the device, it displays an error message and prompts you to continue with designating the device as a master image or canceling. If you choose to continue, be aware that you must fix the issue preventing communication between Configuration Manager and the device before the Connector can orchestrate deployments.

Verify that the WMI-In rule is enabled in Windows firewall and that the master image VM is running. Also check for other networking issues.

The compliance status for a deployment has remained as "Waiting For Orchestration" for a long time

The status "Waiting for Orchestration" appears for machines that are in idle policy mode and have not rebooted. The following situations can result in a stalled or failed orchestration:

  • An application is deployed to an MCS or Provisioning Services managed machine catalog without first designating an update device for the catalog. For more information, refer to Deploy applications to machine catalogs.
  • Machine clones are powered off. The Configuration Manager client cannot obtain status information from a machine that is powered off. Use Studio to power on MCS managed machine clones.
The Publication Wizard pre-flight check indicates that an application is not deployed to a machine catalog device collection although Configuration Manager reports 100% compliance

or

The Connector synchronization task log consistently shows an exception following three "Loaded: PowerShell snapin/module" messages tagged with Component "SynchronizationWorkerXD"

On Windows Server 2008 R2, the default maximum PowerShell memory per shell is 150 MB. The Connector requires at least 1024 MB of memory per shell to synchronize with the Delivery Controller.

Configure the MaxMemoryPerShellMB setting as described in Prepare for installation.