How to Monitor VPN Profiles in Configuration Manager

 

Updated: May 14, 2015

Applies To: System Center 2012 Configuration Manager SP2, System Center 2012 R2 Configuration Manager, System Center 2012 R2 Configuration Manager SP1

Note

The information in this topic applies only to System Center 2012 R2 Configuration Manager versions only.

After you have deployed System Center 2012 Configuration Manager VPN profiles to devices in your hierarchy, you can use the following procedures to monitor the compliance status of the VPN profile:

How to View Compliance Results in the Configuration Manager Console

Use this procedure to view details about the compliance of deployed VPN profiles in the Configuration Manager console.

To view compliance results in the Configuration Manager console

  1. In the Configuration Manager console, click Monitoring.

  2. In the Monitoring workspace, click Deployments.

  3. In the Deployments list, select the VPN profile deployment for which you want to review compliance information.

  4. You can review summary information about the compliance of the VPN profile deployment on the main page. To view more detailed information, select the VPN profile deployment, and then on the Home tab, in the Deployment group, click View Status to open the Deployment Status page.

    The Deployment Status page contains the following tabs:

    - **Compliant:** Displays the compliance of the VPN profile that is based on the number of affected assets. You can double-click a rule to create a temporary node under the **Users** node in the **Assets and Compliance** workspace, which contains all users that are compliant with this profile. The **Asset Details** pane displays the users that are compliant with the VPN profile. Double-click a user in the list to display additional information.
    
      <div class="alert">
    
    
      > [!IMPORTANT]
      > <P>A VPN profile is not evaluated if it is not applicable on a client device; however, it is returned as compliant.</P>
    
    
      </div>
    
    - **Error:** Displays a list of all errors for the selected VPN profile deployment that is based on the number of affected assets. You can double-click a rule to create a temporary node under the **Users** node of the **Assets and Compliance** workspace, which contains all users that generated errors with this profile. When you select a user, the **Asset Details** pane displays the users that are affected by the selected issue. Double-click a user in the list to display additional information about the issue.
    
    - **Non-Compliant:** Displays a list of all noncompliant rules within the VPN profile that are based on the number of affected assets. You can double-click a rule to create a temporary node under the **Users** node of the **Assets and Compliance** workspace, which contains all users that are not compliant with this profile. When you select a user, the **Asset Details** pane displays the users that are affected by the selected issue. Double-click a user in the list to display further information about the issue.
    
    - **Unknown:** Displays a list of all users that did not report compliance for the selected VPN profile deployment together with the current client status of the devices.
    
  5. On the Deployment Status page, you can review detailed information about the compliance of the deployed VPN profile. A temporary node is created under the Deployments node that helps you find this information again quickly.

    Important

    For devices running Windows 8.1 and later, you may obtain a compliance error stating that the Check Point VPN deployment failed due to an issue with the fingerprint feature. This error can be safely ignored, as the fingerprint feature is specific to iOS, and the deployment will have succeeded.

How to View Compliance Results by Using Reports

Compliance settings, which include VPN profiles in Configuration Manager, also includes a number of built-in reports that let you monitor information about VPN profiles. These reports have the report category of Compliance and Settings Management.

Important

You must use a wildcard (%) character when you use the parameters Device filter and User filter in the compliance settings reports.

For more information about how to configure reporting in Configuration Manager, see Reporting in Configuration Manager.