Private Sites are instances of the Exoprise Secure Service (aka 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; LAN, WAN, Wi-Fi, MPLS, SD-WAN. Measure end-user experience from anywhere, any condition. Private Sites can be installed as Local System or configured with a domain or local Service Account.
We sometimes refer to the sensors that a Private Site runs as Private Sensors.
- 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.
- A Private Site can be downloaded that 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
- Ideally, since sites run sensors that give you the end-user perspective, you want to install Private Sites in similar network conditions that your end-users operate under.
- 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.
- Private Sites, ideally, should be deployed wherever you have varied network conditions.
- Private sites are straightforward to deploy and maintain. After a private is initially deployed, it requires no maintenance. Private sites update themselves.
Exoprise has very minimal installation requirements:
- 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. Anything.
- If creating a Private Site on a Virtual Machine, we recommend allocating at least 2 cores for the CPU. Since 2012, most smartphones are no longer single-core. And if you are trying to emulate end-user environments, their machines are most definitely multicore.
- 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 horsepower.
- DISK: Between 30-100 MB, depending on the number and types of sensors deployed.
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 if you are deploying:
- Deploying many sites
- Want 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.
Different Installation Methods
Read more about the different installation methods