Virtual Ivanti EPMM requirements
If you are installing a virtual Ivanti EPMM, you need to ensure that the minimum requirements are met. This section lists the requirements for Ivanti EPMM.
Other topics in this section include:
- Storage devices
- Minimum memory and CPU for Ivanti EPMM (VMware, Hyper-V)
- Minimum specification (VMware, Hyper-V)
- Gather required Ivanti EPMM information
The following table lists the virtual Ivanti EPMM requirements. (Alternative memory and CPU configurations are not covered by the Ivanti EPMM product warranty.)
Components |
Requirements |
Hard drive |
Ivanti recommends configuring only one hard drive on the virtual machine. System performance is directly related to hard disk drive performance. We recommend using only high-performance tier I storage products. |
Backup VMware |
Ivanti recommends taking periodic .vmdk backups of your Virtual Appliance as part of your system maintenance. Use VMware VCB or another VMware-supported backup system. A backup of the full virtual disk is recommended; VMware snapshots are not sufficient. |
VMware |
We currently support the LSI logic SAS or Parallel SCSI controllers; para-virtualized controllers are not supported. Alternative memory and CPU configurations are not covered by the Ivanti EPMM product warranty |
Hyper-V |
Microsoft Hyper-V Server 2008 requires a legacy network adapter. New features in Microsoft Hyper-V Server 2016 (discrete device assignment, shielded virtual machines, disk encryption, secure boot, etc.) are not supported. |
Kernel-based Virtual Machine (KVM) |
For more information about setting up a Kernel-based Virtual Machine (KVM), see https://help.ubuntu.com/community/KVM. |
Storage devices
The following table lists the requirements for storage devices.
Operation |
Min IOPS |
Bandwidth |
90% Operations < xxx mS |
Random Read |
400 |
3 MBps |
10 mS |
Random Write |
900* |
15 MBps |
4 mS |
Storage device notes
- Ivanti recommends configuring only one storage device per virtual machine.
- RAID controller may have to be specifically configured in order to achieve high Random Write IOPS (For example: Disk Cache: Enabled, Default Write: Write Back with BBU).
- System performance is directly related to storage device performance. We recommend using only high-performance tier 1 storage products.
Minimum memory and CPU for Ivanti EPMM (VMware, Hyper-V)
The following table captures the minimum memory and CPU recommendations based on devices tested by Ivanti.
These recommendations are based on internal tests performed by Ivanti and may vary with real-time deployments. The performance might change depending on an individual use case and work load for an environment.
If you observe performance issues in your environment, Ivanti recommends using the next set of values.
Maximum Devices |
Memory |
Virtual CPU / Min Clock Rate |
Total Available Storage Capacity |
Min Storage IOPS (Random Read) |
Min Storage IOPS (Random Write) |
< 5,000 |
8 GB RAM* |
Qty 2 / 2.13 GHz processors** |
80 to 250GB SAS |
400 |
1000 |
< 20,000 |
16 GB RAM* |
Qty 4 / 2.13 GHz processors** |
250 GB SAS |
400 |
1000 |
< 50,000 |
32 GB RAM* |
Qty 8 / 2.13 GHz processors** |
500 GB SAS |
400 |
1000 |
< 100,000 |
64 GB RAM* |
Qty 16 / 2.13 GHz processors** |
1TB SAS |
400 |
1000 |
* Resource allocation - no ballooning allowed
** Resource allocation - no sharing allowed with other VMs
Minimum specification (VMware, Hyper-V)
The following minimum specification does not include significant use of the app store or Ivanti Docs@Work.
Maximum devices |
Memory |
Virtual CPUs |
Disk |
< 500 |
8 GB RAM* |
1 x 2.13GHz processors** |
80 to 250GB SAS |
Random Write |
900* |
15 MBps |
4 mS |
*Guaranteed resource allocation - no ballooning allowed
**Guaranteed resource allocation - no sharing allowed with other VMs
Gather required Ivanti EPMM information
Use the following table to gather and record Ivanti EPMM information before installation.
Item |
Description |
Values |
Licensing agreement information |
The company name, contact person name, and contact person email address for the end-user licensing agreement. |
|
Ivanti EPMM Server IP Address |
Static IP address for portal access. |
|
External Hostname |
Fully-qualified domain name for Ivanti EPMM. Do not use an internal hostname. Managed devices must be able to access Ivanti EPMM from the Internet. |
|
The Ivanti EPMM password to be defined for enabling access to Privileged and Configuration modes. |
|
|
Administrator User Name |
The user name to define for the Ivanti EPMM Administrator. Do not use root or ha_admin. |
|
Administrator Password |
The Ivanti EPMM Administrator password must contain the following elements:
Users cannot change a password more than once during a 24 hour period. |
|
Physical Interface |
The physical interface to use on the appliance. Enter a or b. You can configure additional physical interfaces later using the System Manager. |
|
Netmask |
The IP address and netmask of the physical network interface. |
|
The IP address of the router used to forward traffic to destinations outside of the local network or subnet. |
|
|
The IP address of a network name server (i.e., DNS server). You must specify at least one name server. |
|
|
Specifies whether you want to configure remote shell access via SSH. |
|
|
Specifies the IP address of an optional reliable time source. We recommend specifying an NTP server. If you do not, you will have the opportunity to set the system clock and date. |
|