1. Run the ENow Admin Console. You can find the following shortcut in the Windows Server 2008 editions Start Menu:
Start > Programs > ENow > ENow Admin Console
Or
Start > ENow > ENow Admin Console
If you are running Windows Server 2012, then you can use the search and type “ENow” and select the ENow Admin Console.
2. Install Clients on all of the servers that you intend to monitor with the ENow Management System. Please plan to use the ENow Client Remote Installer to install the clients and note that you will need to run it once for each feature of the EMS web server that you intend to enable. For example: if you want to monitor Domain Controllers, Exchange & Lync servers the ENow Remote Installer should be run a total of 3 separate times where the selection of the server type is either Domain Controller, Exchange server, or Lync server. When deploying to Domain Controllers, we require that Local System be selected instead of a domain account. For all other server types, we require domain accounts that are configured to logon as a service and have the correct permissions granted as outlined in the EMS web server prerequisites document. Note: for the ENow Remote Installer to function fully, the following services will be required to run on the Web server and the remote target servers when the Windows Firewall is enabled:
Computer Browser (set to disabled by default)
DHCP Client (set to automatic by default)
DNS Client (set to automatic trigger start by default)
Function Discovery Resource Publication (set to manual by default)
Network Connections (set to manual by default)
Network Location Awareness (set to automatic by default)
Remote Procedure Call (RPC) (set to automatic by default)
Server (set to automatic by default)
SSDP Discovery (set to disabled by default)
TCP/IP NetBIOS helper (set to automatic trigger start by default)
UPnP Device Host (set to disabled by default)
Workstation (set to automatic by default)
In addition, we require that Network discovery be enabled on the EMS web server and remote target servers. The EMS web server will specifically require file sharing to be enabled. The remote target servers will all require .NET 2.0 (.NET 3.5 for Windows Server 2012 editions) to be enabled. Windows Servers running 2003 editions and Windows Servers located in a DMZ are not supported by the ENow Remote Installer and will require a local installation of the ENow Client Setup to be performed.
3. Please verify the URL of the Web server and location of the MailscapeAgent.msi file, then select Next.
4. Please plan to ignore the notes about the Admin Service and review the EMS web server prerequisites (or feature specific prerequisites guide) for details about the permissions required by the ENow Client and Admin services. Then proceed to configure the service account intended for the remote target servers and select Next.
5. Select Add to begin adding the remote target servers.
6. The Exchange role will be selected by default.
7. To change this, select the drop down arrow to the right of Exchange and then only select the specific server role you intend to deploy to.
8. Afterwards, select to the right of Name to begin performing a look up of the server names that align with the server roles selection.
9. In the windows that opens, first select the correct domain using the drop down box and then check the appropriate box to filter the server names that will be presented in the box located at the top. Once you have identified the name of a server that will be monitored, select OK and repeat steps 5 to 9 until all of the remote target servers have been added.
10. Select Install to launch the remote deployment of the ENow Client.
11. The ENow Client Remote Installer status window will be presented and provide details about the installation for each server. Please review to verify the installation completed successfully for all the remote target servers. If any errors are reported, please feel free to contact support@enowsoftware.com for assistance. When you have completed the review, select finish. If you need to perform a remote installation for another set of servers, please launch the ENow Remote Installer again and repeat steps 3 to 11.
This concludes the ENow Client Remote Installer Guide. If you need to perform an installation of the ENow Client locally on a server, then please refer to the ENow Client Setup Guide.