{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":31359,"path":"it-operations-management/service-mapping/mapping-services-citrix.md","title":"Mapping Citrix XenApp and Presentation Server services","bundle":null,"doc_type":null,"release":"australia","body":"\n# Mapping Citrix XenApp and Presentation Server services\n\nService Mapping can discover application services containing Citrix XenApp, Presentation Server, and Citrix Usage Collector.\n\n## Discovered components\n\n<table id=\"table_vnn_x21_4fb\"><thead><tr><th>\n\nName\n\n</th><th>\n\nPlatform\n\n</th><th>\n\nVersion\n\n</th><th>\n\nProtocol\n\n</th><th>\n\nDiscovery type\n\n</th><th>\n\nPattern \\(or probe if indicated\\)\n\n</th></tr></thead><tbody><tr><td>\n\nCitrix XenApp Server\n\n</td><td>\n\nWindows\n\n</td><td>\n\n6.x&gt;6.5, 7.x&lt;7.6\n\n</td><td>\n\nWMI\n\n WinRM\n\n</td><td>\n\nHorizontal and top-down\n\n</td><td>\n\nCitrix XenApp or Presentation Server\n\n</td></tr><tr><td>\n\nCitrix Presentation Server\n\n</td><td>\n\nWindows\n\n</td><td>\n\n4.x, 5.x, 6.x&lt;6.5\n\n</td><td>\n\nWMI\n\n WinRM\n\n</td><td>\n\nHorizontal and top-down\n\n</td><td>\n\nCitrix XenApp or Presentation Server\n\n</td></tr><tr><td>\n\nCitrix Usage Collector\n\n</td><td>\n\nWindows\n\n</td><td>\n\n7.x&gt;7.5, 8.x\n\n</td><td>\n\nWMI\n\n WinRM\n\n</td><td>\n\nTop-down\n\n</td><td>\n\nCitrix Collector\n\n</td></tr><tr><td>\n\nGeneric application based on the Icon Path\n\n</td><td>\n\nWindows\n\n</td><td>\n\n-\n\n</td><td>\n\nWMI\n\n WinRM\n\n</td><td>\n\nTop-down\n\n</td><td>\n\nCitrix Application Icon Path\n\n</td></tr></tbody>\n</table>**Parent Topic:**[Map a single application service using classic Service Mapping](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/service-mapping/t_DefineNewBusinessService.md)\n\n## Map Citrix XenApp and Presentation Server services\n\nMap an application service containing Citrix XenApps, Presentation Servers, and Citrix Usage Collectors and verify that Service Mapping discovered all Citrix components correctly.\n\n### Before you begin\n\n-   Provide a user with permissions to read and query the Citrix repository:\n    -   For versions 4.5 and later, a PowerShell script from the XenApp server.\n    -   For versions earlier than 4.5, a Microsoft Visual Basic Script \\(VBScript\\) from the Citrix Presentation Server\n-   On the ServiceNow AI Platform, configure a domain user for accessing the Windows OS as described in [Windows credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r_WindowsCredentialsForm.md).\n\n    **Note:** To use this credential later for XenAPP, set the **Credential alias** attribute to cmdb\\_ci\\_appl\\_citrix\\_xenapp. To use this credential later for Citrix, set the **Credential alias** attribute to cmdb\\_ci\\_appl\\_citrix\\_collector.\n\n-   \\(Optional\\) To discover using the WinRM protocol, see [Configure WinRM trusted hosts on MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/enable-winRM-MID-servers.md)\n-   Configure a user with permissions to run PowerShell commands on the Citrix server.\n-   \\(For discovery of Citrix Presentation Server only\\) Find out the icon path for the entry point:\n    1.  In the Citrix Access Management Console, navigate to **Presentation Server** &gt; **Applications**.\n    2.  Locate the Icon Path folder in the navigation tree.\n    3.  Right-click the Icon Path folder and click **Copy path**.\n-   \\(For discovery of Citrix XenApp Server only\\) Find out the icon path for the entry point by checking the Distinguish Name attribute for the Icon Path.\n\nRole required: service\\_mapping\\_admin\n\n### Procedure\n\n1.  Create a service instance.\n\n    1.  Navigate to **All** &gt; **Service Mapping** &gt; **Service Instances**.\n\n    2.  Select **New**.\n\n        The **Discoverable by Service Mapping** option is selected by default.\n\n    3.  In the **Name** field, enter a descriptive name for the service instance.\n\n2.  Define the entry point for this service instance:\n\n    1.  Select the **Citrix XenApp** tile.\n\n    2.  Define entry point attributes.\n\n        |Attribute|Description|\n        |---------|-----------|\n        |Host|The URL of the Citrix XenApp or Presentation Server. The URL must contain a VIP IP or a physical host.|\n        |Port|The port that the Citrix XenApp or Presentation Server uses on the host.|\n        |Icon Path|The path to the logical application location as it appears in the Citrix Access Management Console. The path must start with the Applications folder. For example, /Application/Jane/Windows Media Player.|\n        |URL|The URL must contain a VIP IP or a physical host. For example, http://&lt;host&gt;/Citrix/StoreWeb.|\n\n    3.  Click **Add**.\n\n    4.  Click **Save**.\n\n3.  Click **Additional Info** on the left and clear the **Traffic based discovery** check box.\n\n4.  Click **Update**.\n\n5.  Verify that the mapping result is satisfactory:\n\n    1.  Click **View map** and wait until the mapping is complete.\n\n        It may take a few minutes.\n\n    2.  Review the application service map and make sure that it resembles in the following example.\n\n        \\[Omitted image \"Citrix-XenApp-top-down-map.png\"\\] Alt text: Check the result of mapping an application service containing the XenApp Servers and other environment components.\n\n\nIf the mapping result is not as you expected, perform basic troubleshooting.\n\n<table id=\"table_kjv_sdkwo0_3556\"><thead><tr><th>\n\nSymptom\n\n</th><th>\n\nCause\n\n</th><th>\n\nSolution\n\n</th></tr></thead><tbody><tr><td>\n\nDiscovery failed. The discovery log displays the message that starts with the following text: You do not have sufficient permissions.\n\n</td><td>\n\nThe indication sections of the pattern fail, because the user does not have permissions for running PowerShell commands.\n\n</td><td>\n\nMake sure that you provided a user with permissions to run PowerShell commands on servers that host Citrix XenApp, Presentation Server, or Citrix Usage Collector.\n\n</td></tr><tr><td>\n\nDiscovery failed. The discovery log displays the error message that includes the following text:CategoryInfo : NotSpecified: \\(:\\) \\[\\], PSSecurityException+ FullyQualifiedErrorId : RuntimeException\n\n</td><td>\n\nThe MID Server cannot run PowerShell commands remotely, because the execution policy is set to RemoteSigned on the target servers.\n\n</td><td>\n\nUse the `set-executionpolicy remotesigned` command on the target servers to enable the MID Server to successfully run PowerShell commands.\n\n</td></tr><tr><td>\n\nDiscovery failed. The discovery log displays the error message that includes the following text:Import-XAFarm : The Citrix Common Commands PowerShell Snapin is not installed\n\n</td><td>\n\nThe target host does not have this PowerShell library: Citrix Common Commands PowerShell Snapin.\n\n</td><td>\n\nDownload and install PowerShell SDK for Citrix XenApp on all servers hosting Citrix XenApp, Presentation Server, or Citrix Usage Collector.\n\n</td></tr><tr><td>\n\nThe application service map shows the Citrix Delivery Controller, but does not include the Citrix XenApp, Citrix Presentation Server or Citrix Usage Collector.\n\n</td><td>\n\nThe icon path you defined is incorrect.\n\n</td><td>\n\nVerify the icon path and reenter it in the entry point attributes for the application service.\n\n</td></tr></tbody>\n</table>"}}