Creating Private Sites

Guided site installation

Guided site installations are recommended to deploy a site when you are starting.

Why choose this method?

• A guided installation is wizard-driven and walks you through the process. It helps ensure your network configuration is correct and assists with setting up your first security keys.

• Guided installations require the Management Client, which you'll need to validate sensor setups.

Installation steps

1. From the machine you want to install a Private Site to, download and start the Management Client. Refer to Exoprise Management Client.

2. Sign in to Exoprise.

3. Navigate to Sites > Deploy. Click the Guided Installation tab, then click Get Started Installing a Private Site.

4. On the Configure Keys step, click Next to create a public-private key pair automatically if you don't have any yet.

5. On the Service Account step, configure how you want to run the service (the account that the service will run as). If you are not using a proxy or don't know if you are, select Local System. For Proxy PAC and WPAD configurations, refer to Proxy setup, requirements, and firewall exclusions. If you plan on deploying many locations, then you may want to create a domain service account.

6. Once you've chosen the account setup, click Next.

7. Depending on whether a proxy is detected, you may have to configure the proxy settings for the service setup. Refer to Proxy setup, requirements, and firewall exclusions.

8. On the final installation step, you should see a successful installation.

   If the service is unable to contact the Exoprise servers, you may see an error and reason code. Usually, it's to do with proxies and authorization, or some kind of permissions problem. If the installation fails, you may need to uninstall the service from the Windows Control Panel.

Pre-configured site installation

You can configure and download a site installation that is tied to your Exoprise tenant. This is useful for sharing a setup with a coworker who can then install it on a machine that you may not have access to. The coworker will be able to install the site, and it will be ready and attached to your Exoprise tenant. The coworker doesn't even have to have login rights to the Exoprise platform.

Why choose this method?

• A pre-configured setup enables you to easily deploy many Private Sites.

• Pre-configured setups can be shared with others to install or packaged as a sub-installer. The installation is linked to your tenant automatically.

• You don't have to download the Management Client separately.

• Once a site is deployed, you can add sensors from any machine.

Installation steps

1. Click Add New Install Key to create an install key that securely identifies the setup to your account. You can later delete the install key to block an installation that's been shared.

2. Configure the various account and proxy options for the setup. You can also configure what interactive installer options are available during setup for possibly overriding configuration options.

3. Download and copy the setup to the machine where you'd like to install the site, and then run it.

Proxy setup, requirements, and firewall exclusions

Private sites and Service Watch Desktop installations support operating behind all kinds of proxies, proxy configurations, and firewalls. Depending on your proxy configuration, there are several recommended ways to set up sites or installations to support proxies.

When you start with a guided installation to set up a Private Site, the proxy configuration will be read from the Management Client. If you choose to deploy as Local System, and your environment requires a proxy, you may have to explicitly set a fixed proxy for the site.

For private sites or Service Watch desktop installations to work, and to set up sensors, two or three DNS names need to be allowed through the proxy, firewall, or any network path blocking that might be in place:

• secure.exoprise.com: For Management Client access.

• service.exoprise.com: For Private Site access.

• pubsub.exoprise.com: For Private Site alarm logging. This is optional.

Management Client proxy settings

By default, when you install the Management Client to set up a site, the client will recognize that the desktop you are using is behind a proxy and will automatically utilize the same proxy that is configured for the desktop. Most network tools work this way.

To check your proxy configuration, open Settings on your computer and navigate to Network & internet > Proxy. From here, you can see whether you are using a proxy that is automatically configured within your environment or if a specific proxy is set.

To override the proxy that a Management Client is using, follow these steps:

1. From the Management Client, click the green Tools icon in the upper left (or press Alt-F), then click Preferences.

2. In the Settings dialog, click the Proxy tab.

3. From here, you can change the proxy preferences for the Management Client. If you were explicitly prompted for proxy credentials, you will see that a proxy server was chosen.

Proxy PAC or proxy WPAD Configurations

If your environment uses proxy PAC files or automatic WPAD configurations, the Management Client should natively support them upon startup. The Private Site (Windows Service) will need to be set to run as a non-Local System account (that is, Service Account) for it to be able to leverage a proxy PAC or WPAD configuration.

Change the proxy setup for a site

If you have a Private Site configured to use a fixed proxy, it can be changed from the Manage Local Site page using the Management Client on the machine that is running the service.

1. Open the Management Client and sign in.

2. Navigate to Sites > Manage Local Site. where you will see a status page for the Private Site.

3. In the Change drop-down list in the middle of the screen, click the entry Service Proxy Settings to display the proxy settings dialog.

4. Enter the new proxy information and click Update. The service should now be stopped and restarted with the new proxy settings.