Newly installed ENow Client does not appear in the Authorize Servers screen

Symptom

After installing the ENow Client on an Exchange server or domain controller, the server does not appear in the ENow Admin Console for authorization.

Cause

Most commonly, the client configuration holds the wrong web server URL. The client is running, but it is reporting to an address that does not answer, so the web server never learns it exists and it never appears in the authorization list.

Resolution

Check and correct the web server URL in MailscapeAgent.config on the affected client.

1. On the affected client, open Notepad as an administrator. The file is in a protected location, so an ordinary Notepad session will not be able to save changes.
2. In Notepad, go to File > Open.
3. Navigate to the Mailscape Agent folder. The default path is:

   C:\Program Files (x86)\ENow\Mailscape Agent

4. Open MailscapeAgent.config.
5. Find the <Web> key and note the URL it holds.
6. Check that URL against your actual ENow web server. The default port for the ENow web service is 20080, so the URL normally looks like:

   http://<your-web-server>:20080/MailscapeWeb

   If your web server is configured for HTTPS, the port is dropped and the scheme is https.

7. If the URL is wrong, correct it and save the file.

Confirm the fix

Paste the URL from the config file into a browser on the client machine itself — not on the web server. If it is correct, the ENow OneLook Dashboard loads. Testing from the client is the point: it proves the client can reach the address, which is what was failing.

The client should then appear for authorization under Server > Deployment > Security in the ENow Admin Console.

Applies to

Observed in EMS 7.13 CU1 (build 7.13.1.232) and later. Earlier versions may also be affected.