Private Last Mile system requirements

Private Last Mile is designed to use minimal resources on the host system.

Resource usage

The resource requirements are as follows:

Disk usage

Private Last Mile installations typically require a maximum of 100 MB of disk space. Test data is not saved to disk, so the disk usage tends to be stable.

If you install the private peer that includes a built-in virtual machine, available by request from Customer Support, enabling Internet Explorer Native Browser Agent support requires up to 2 GB of additional disk space.

Processor

A 1-GHz Pentium IV or better CPU is required.

Under typical circumstances, Private Last Mile spends much of its time idle. Most operations are network-bound, occurring when the poll message is sent to query for tests, while the test is being executed, and when the polling is periodically updated. The application runs at a reduced priority on the user's operating system, making it an early candidate for preemption when other processes are waiting to run.

Memory

The minimum RAM requirement is 512 MB; 2 GB is recommended to enable the Internet Explorer Native Browser Agent.

Process size is typically a maximum of 35 MB, but size may vary depending on test load. If you install the private peer that includes a built-in virtual machine, enabling the Internet Explorer Native Browser Agent involves a Virtual Machine instance, which can use up to an additional 700 MB of memory during heavy tests.

Network bandwidth

Network bandwidth usage is a function of the complexity and frequency of tests sent to the peer. In most cases, bandwidth is negligible. If, however, the peer is scheduled to test consistently, network usage would be similar to an Internet browser in constant use.

Supported operating systems

Private Last Mile is supported with the following operating systems:

  • Windows XP
  • Windows 2003
  • Windows Vista
  • Windows 2008
  • Windows 7
  • Windows Server 2012
  • Windows 8
  • Windows 10

If you experience issues running IE Agent tests on Windows 10, make sure Internet Explorer 11 is enabled:

  1. Press the Windows key to display the Start menu.
  2. In the Search Programs and Files field, type Turn Windows features on or off, then press Enter.
  3. If you are prompted for User Account Control, enter your admin password to proceed.
  4. Make sure Internet Explorer 11 is selected (enabled), then click OK.

Private Last Mile no longer supports execution of IE tests on the following (end-of-life) operating systems: Windows 2000, Windows XP, Windows Vista, Windows Server 2003 R2.

Supported browsers

Private Peers leverage Firefox 24 and Chrome 34 and support Internet Explorer 8, 10, and 11.

Windows permissions

The Private Peer service (gomezpeer) must run under a Windows administrator account. If you need to start/stop the service through the Private Last Mile UI and your login for the host machine does not have Windows administrator permissions, then start the Private Last Mile executable by right-clicking the executable in Windows Explorer, selecting Run as… from the context menu, and providing a username and password with administrator privileges.

The Private Last Mile UI does not require Windows administrator permissions. It can run under either a local user or a Windows domain user.

As of the May 2016 release, the IE Native Browser Agent does not require Windows administrator permissions. Any DOMAIN\user account can use this agent. However, the Internet Explorer browser cache is shared with the user account that is configured for Private Last Mile. If that user frequently uses Internet Explorer on the machine where Private Last Mile is installed, the user's updates to the cache and the IE Agent's clearing of the cache may cause varying results in the Private Last Mile data. Therefore, we recommend assigning a dedicated user account to the private peer.

Private peer VM support

The private peer is supported to run on a physical machine or on a virtual machine.

If you require an installation of Private Last Mile that includes a built-in virtual machine within the private peer, contact Customer Support for assistance. The VM private peer uses VMware Player 2.5.3. Windows XP 32-bit with Internet Explorer 8 runs within the VM - there is no newer OS/Browser version available with the VM.

Because the VM private peer has a built-in virtual machine, it is designed to be installed on a physical machine. It is not supported on a virtual machine, because one machine can only have one VM.

Using the private peer through a firewall

When setting up Private Last Mile software on an internal machine, the following domain names and IP addresses should be permitted by the firewall (and any other content filtering tools within the company) on the standard ports 80 (HTTP) and 443 (HTTPS):

  • 69.84.209.207
  • 69.84.209.208
  • 69.84.209.209

The following applications need to be added as approved to the firewall software for the Private Peer to communicate:

  • Java.exe
  • PrivatePeer.exe