EPM for Windows Local AD Connector failing on activation

Question

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?

Jens Hansen · Answer

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