DX Unified Infrastructure Management

  • 1.  Xenapp probe not discovering workers

    Posted Oct 20, 2016 03:05 AM

    Hi,

    I have installed latest xenapp probe on top of one server robot where citrix managemente is installed. Workers group are not discovered. Xenapp version is 6.5 on 2008 R2

    on the log I see this error while starting

     

    Oct 20 09:03:51:497 [main, xenapp] ****************[ Starting ]****************
    Oct 20 09:03:51:497 [main, xenapp] ERROR: could not find pom.properties: /META-INF/maven/com.nimsoft/xenapp/pom.properties
    Oct 20 09:03:51:497 [main, xenapp] CA Technologies



  • 2.  Re: Xenapp probe not discovering workers

    Posted Oct 20, 2016 10:45 AM

    This is most likely a false error and can be ignored.
    ERROR: could not find pom.properties: /META-INF/maven/com.nimsoft/xenapp/pom.properties

     

    Perhaps increasing the logging level will give some insight as to the cause of the connection problem.
    Go to IM > select the xenapp probe > Shift + right mouse click > Raw Configuration > setup > loglevel > Edit Key > Value 5 > OK > Apply > restart

     

    The log is Nimsoft\probes\application\xenapp\xenapp.log

     

    Also here are some more security possibilities.
    Verify PowerShell Access
    If the XenApp Monitoring probe cannot connect to the XenApp server, it may be because remote access to PowerShell on the XenApp server is restricted. Verify that the correct access is set for PowerShell on the XenApp server.
    Follow these steps:
    1. Open a PowerShell window on the XenApp server and enter the following command:
    Get-ExecutionPolicy
    2. If the response says Restricted, you must change the setting to Unrestricted or RemoteSigned. For example, to set it to RemoteSigned:
    * Enter the following command:
          Set-ExecutionPolicy RemoteSigned
    * Enter Y to accept the policy.
    * Enter the Get-ExecutionPolicy command again to verify the setting.
    Set Up Multi-Hop Authentication
    If the XenApp Monitoring probe cannot connect to the XenApp server, it may be because credentials must be delegated across multiple remote computers in your environment. In this case, you must configure WinRM to use Credential Security Service Provider (CredSSP) to provide multi-hop support for authentication. Kerberos delegation is not supported by the XenApp Monitoring probe.
    Follow these steps:
    Note: If any of the following commands having single quotations fail, then try to run the command without the quotation marks.
    1. Enable CredSSP on the WinRM client system, either by setting it manually or through a Group Policy setting.
    To set it manually enter the following command:
    winrm set winrm/config/client/auth '@{CredSSP="true"}'
    To set it through a Group Policy, follow these steps:
    1. Enter the following command in a Command Prompt window to open the Group Policy dialog:
    gpedit.msc
    2. Navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client.
    3. Double-click on the Allow CredSSP authentication policy in the right pane to open its configuration dialog.
    4. Edit the policy as necessary.
    2. Enable CredSSP on the WinRM service, either by setting it manually or through a Group Policy setting.
    To set it manually enter the following command:
    winrm set winrm/config/service/auth '@{CredSSP="true"}'
    To set it through a Group Policy, follow these steps:
    1. Enter the following command in a Command Prompt window to open the Group Policy dialog:
    gpedit.msc
    2. Navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service.
    3. Double-click on the Allow CredSSP authentication policy in the right pane to open its configuration dialog.
    4. Edit the policy as necessary.



  • 3.  Re: Xenapp probe not discovering workers

    Posted Oct 20, 2016 12:00 PM

    Hi,

     

    This same problem was reported under support case 00533990, and after several investigations we found out a potential connectivity issue that was preventing the probe from monitoring the Citrix when trying to stablish a connection from the localhost. Deploying the xenapp probe to the hub the robot was reporting to did resolve the issue, and this workaround was accepted by the customer.

     

    Regards,

    David