Symantec Privileged Access Management

Expand all | Collapse all

Issue While installing Windows Proxy (CA PAM)

Jump to Best Answer
  • 1.  Issue While installing Windows Proxy (CA PAM)

    Posted 10-16-2017 04:03 AM



    We are trying to install CA privileged access management's component : Windows Proxy.

     Installation went without any issue but when we try to 

    Authenticate the Windows Proxy with two commands (Given in the documentation), it fails.

    Any possible cause , please help ?


    C:\Windows\system32>set CP=%CPA_AGENT_HOME%\cspmclient\lib\cspmclient.jar;%CPA_A


    C:\Windows\system32>java -classpath %CP% com.cloakware.cspm.client.ClientDaemonM
    anager authagent c:\cspm\cloakware\cspmclient\config\cspm_client_c
    onfig.xml (The system cannot find the path specified)
    at Method)
    at<init>(Unknown Source)
    at com.cloakware.cspm.client.Configuration.initConfig(SourceFile:162)
    at com.cloakware.cspm.client.Configuration.<init>(SourceFile:82)
    at com.cloakware.cspm.client.c.<init>(SourceFile:18)
    at com.cloakware.cspm.client.ClientDaemonManager.main(SourceFile:19)


    Thanks in advance.




  • 2.  Re: Issue While installing Windows Proxy (CA PAM)

    Posted 10-16-2017 09:20 AM

    Hello, which version of the PAM docs are you looking at? These instructions were in older doc versions, but they are wrong and have since been removed. You should not find these in the latest 2.8 or 3.0 docs such as at

  • 3.  Re: Issue While installing Windows Proxy (CA PAM)

    Posted 10-17-2017 04:55 AM

    So, I think our installation is fine, we have started the service as well.

    Now, when we create endpoint account, application and policies (all actions)

    When RDP session is initiated, we get error popup like


    Unable to connect to backend device. please contact administrator.





  • 4.  Re: Issue While installing Windows Proxy (CA PAM)
    Best Answer

    Posted 10-17-2017 01:21 PM

    For this type of RDP error, you want to ensure the IP address or name is correct for the target device.  Also, check firewall between PAM and the endpoint.  You can use Config -> Tools to test if port 3389 is open between PAM and the target device for RDP.