Skip to main content
Veteran
March 5, 2026
Question

EPM for Windows Local AD Connector failing on activation

  • March 5, 2026
  • 7 replies
  • 100 views

I tried to install my EPM for Windows Local AD connector on a server but it failed on the activation part.

Error is:

[ERR] [BT.LocalAdConnector.Services.ActivationService] [9] Activation failed.
System.Net.Http.HttpRequestException: No such host is known. (xxxxxx-xxxxxxxxx-services.pm.beyondtrustcloud.com:443)
 ---> System.Net.Sockets.SocketException (11001): No such host is known.

 

My server is connected to my proxy server for external access and I have the policy opened from my server to xxxxxx-xxxxxxxxx-services.pm.beyondtrustcloud.com but it is not getting triggered at all. 

Am I missing something here? do I need any additional URL for the activation of the AD connector?

    7 replies

    Guru
    March 5, 2026

    The AD Connector uses the same URL to authenticate to as your Windows desktop clients.

    Check NSLookup for the URL, There is a slight change the is your proxy, I don’t think I have seen anything related to making the AD-Connector Proxy aware similar to the Console Adapter and Package Manager.

    Included a couple of KB with issues that does occur when behind the proxy.

    Then I wonder if the KB0019358 can be configured for your AD Connector process in a similar way.
    It’s worth a shot.

    https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0019358

    https://beyondtrustcorp.service-now.com/csm?id=kb_article_view&sysparm_article=KB0022879

    Guru
    March 16, 2026

    I tried to install my EPM for Windows Local AD connector on a server but it failed on the activation part.

    Error is:

    [ERR] [BT.LocalAdConnector.Services.ActivationService] [9] Activation failed.
    System.Net.Http.HttpRequestException: No such host is known. (xxxxxx-xxxxxxxxx-services.pm.beyondtrustcloud.com:443)
     ---> System.Net.Sockets.SocketException (11001): No such host is known.

     

    My server is connected to my proxy server for external access and I have the policy opened from my server to xxxxxx-xxxxxxxxx-services.pm.beyondtrustcloud.com but it is not getting triggered at all. 

    Am I missing something here? do I need any additional URL for the activation of the AD connector?

    Did you ever get your AD connector to work?

    Was thinking you could change the HOSTS file and see if that would work as a temp workaround.
    ping your instance YourInstance-services.pm.beyondtrustcloud.com and grab the IP to make an entry in your HOSTS files.

    Kind regards
    Jens

    JasperAuthor
    Veteran
    March 18, 2026

    @Jens Hansen , no, my local AD connector still is not showing up in the PM Console after the install. It gets installed on the server but won’t get activated.

    Guru
    March 19, 2026

    Did you attempt to use any of the KB above? and did you raise a ticket with BT.

    Then just an FYI. the AD Connector can be installed on any Windows system and just allows you to browse your AD. You can install it on your own laptop if needed.

    Jens

    JasperAuthor
    Veteran
    March 20, 2026

    @Jens Hansen , I did try the KB article you mentioned. I am not 100% sure though about the KB0022879 since the install is for the local AD connector itself.

    Guru
    March 20, 2026

    KB002879 was more me thinking it would have the same issue as the Package Manager, as both connect to the same url. 

    Try a local install on your workstation, and make sure you can configure the service, as it does not need to run always, it’s more for you when changing the filters on Workstyles of App Rules.

    It just need access to read the domain, so if home a VPN is needed.

    Kind regards
    Jens

     

     

    JasperAuthor
    Veteran
    March 26, 2026

    KB002879 was more me thinking it would have the same issue as the Package Manager, as both connect to the same url. 

    Try a local install on your workstation, and make sure you can configure the service, as it does not need to run always, it’s more for you when changing the filters on Workstyles of App Rules.

    It just need access to read the domain, so if home a VPN is needed.

    Kind regards
    Jens

     

     

    @Jens Hansen installing on my workstation is fine. I just want to install it on a server so others from my team would be able to update my filters even when I am not around, as that would mean my workstation is also offline at that time