• Identify a server where the Data Collector software will be installed. Server requirements include:

• 64-bit OS. See the APTARE Certified Configurations Guide for additional information.

• Support Java Runtime Environment (JRE) 1.8.

• For performance reasons, APTARE recommends that you do not install Data Collectors on the same server as the Portal. However, if you must have both on the same server, verify that the Portal and Data Collector software do not reside in the same directory.

• Install only one Data Collector on a server (or OS instance).

• The collector must have WMI network access to the Hyper-V servers. User credentials must allow access to the root\cimv2, root\virtualization\v2 and root\MSCluster WMI namespaces.

• The Data Collector Service that is initially installed uses the Local System as the Log in account. Sometimes this account does not have permissions to run remote WMI commands. You should instead change the Service configuration to use a Log in account that has Local Administrative privileges.

• The collector uses a PowerShell script that uses WMI to communicate with the Hyper-V, and makes a number of read-only calls to gather the information. PowerShell script execution must be enabled on the system running this script. The version of PowerShell on the system must be 5.0 or above.

• A full collection path to Hyper-V server attached SAN or NAS storage requires that Host Resource collection be run first against the Hyper-V servers.

• WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM’s service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service.