Private Sites

Overview

Private Sites are instances of the Exoprise Secure Service (that is, agent) that you install on your own computers or virtual machines wherever you want to get the end-user perspective of cloud services and test the health of the network.

  • Private Sites can be deployed anywhere, within any network, including LAN, WAN, Wi-Fi, MPLS, and SD-WAN.

  • Measure end-user experience from anywhere, under any condition.

  • Private Sites can be installed as Local System, or configured with a domain or local Service Account.

The sensors that a Private Site runs are sometimes referred to as Private Sensors.

Features

  • Private Sites run sensors that emulate the end-user perspective for monitoring cloud apps and services.

  • Private Sites are easy to set up and maintain. A site is self-updating after extensive testing periods. You can also accelerate the updating of a Private Site from the Manage page under Sites.

  • A Private Site can be downloaded and is pre-configured for your account so that you can give the installation to someone. This can be handy for installations at remote sites.

Where to install Private Sites

  • Since sites run sensors that provide the end-user perspective, ideally, you should install Private Sites in network conditions similar to those of your end users.

  • Private Sites can run alongside any workload and can even be installed alongside an end-user's desktops or laptops. Resource requirements are minimal, so sensors can be run anywhere.

  • Ideally, Private Sites should be deployed wherever you have varied network conditions.

  • Private Sites are straightforward to deploy and maintain. After a Private Site is initially deployed, it requires no maintenance; Private Sites update themselves.

Requirements

Exoprise has very minimal installation requirements:

  • Operating system: Any Windows® OS; 10, 11, Server versions.

  • Private Sites and the sensors can run alongside almost any workload. You can safely deploy on a user's machine, a server, a BDC, or PDC.

  • CPU: If creating a Private Site on a virtual machine, we recommend allocating at least two cores for the CPU. Since 2012, most smartphones are no longer single-core. If you are trying to emulate end-user environments, their machines are most definitely multi-core.

  • RAM: Machines or VMs with as little as 1 GB of RAM can easily run 10 sensors, but it also depends on the sensor types. Some sensors, such as RDP, Teams AV, or browser-based sensors require more system resources.

  • Disk: Between 30-100 MB, depending on the number and types of sensors deployed.

Logon identity

A Private Site (Windows Service) can be installed to run as Local System or configured to run with an account, typically called a Service Account. The default installation chooses Local System because it is easiest to get started with.

Consider using a Service Account in the following scenarios:

  • Deploying many sites.

  • Requiring more control and consistency with the installations.

  • Using a proxy, SSL inspection, Proxy PAC, or WPAD.

Proxy PAC and automated configuration mechanisms like WPAD are typically not configured for Local System, so it is easier to use a Service Account.

Installation methods

Refer to Creating Private Sites.