1-800-691-1991 | 9am - 8pm ET
EN

Veeam Management Pack v6 Required Ports and Permissions

KB ID: 1759
Product: Veeam Management Pack for Microsoft System Center
Version: v6.x
Published: 2013-05-31
Last Modified: 2020-08-28
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Solution

Required Permissions

Connection to Virtual Servers

VI Object Required Permissions

vCenter,
ESX(i) Host

 
  • Read-Only1
  • Host.CIM.CIM Interaction2
  • Datastore.Browse Datastore3
  • Datastore.Configure Datastore3
  • Datastore Cluster.Browse Datastore Cluster3

1 Minimum required permission over the entire vCenter topology.
2 Required for direct gathering of vSphere host hardware data.
3 Required in order to run the Scan Datastores for Unknown Files task.

OpsMgr Agent Operation

The OpsMgr agent action account must be an Administrator on the server where the Veeam component(s) (Veeam Collector or Veeam Virtualization Extensions Service) are running.


Veeam Virtualization Extensions Service Account

The Veeam Virtualization Extensions service account must have Administrator privileges on the computer where this service runs.

Veeam VMware Collector Service Account

The Veeam VMware Collector service account must be:

  • An Administrator on the server where the Veeam VMware Collector service is running.
  • A member of the Veeam Virtualization Extensions for VMware Users local security group on the server running the Veeam Virtualization Extensions for System Center service.
Connection to Veeam Virtualization Extensions UI

To access the Veeam Extensions UI (for addition/removal of vCenter connections, configuring Veeam Collector settings etc.), users must be included in the local group named Veeam Virtualization Extensions for VMware Users. This local group is created during Veeam Extensions Service installation.


Required Ports

From To Protocol Port Notes

Veeam Collector
 

vCenter
 

HTTPS
 

443
 

Required for Veeam Collector to gather 
monitoring data. To check the current 
API port open in vCenter, see the 
VMware documentation.
 

Veeam
Virtualization
Extensions
Service

 

vCenter
 

HTTPS
 

443
 

Required to connect to vCenter from 
the Veeam Virtualization Extensions UI.
 

Veeam Collector
 

vSphere Host
 

HTTP
 

5989
 

Required for gathering of SMASH 
hardware sensors via CIM-XML. 
Connection though proxy server is not 
supported, this must be a direct 
connection.
 

Veeam Collector
 

Veeam
Virtualization
Extensions
Service
 

Secured
TCP

 

8084
 

Required for Veeam Virtualization 
Extensions Service to authenticate the 
Collectors, receive heartbeats, and to 
distribute licenses and other 
configuration. (port number can be 
chosen during setup).
 

Veeam
Virtualization
Extensions UI

 

Veeam
Virtualization
Extensions
Service
 

Secured
TCP

 

8084
 

Required for communications between 
Veeam Virtualization Extensions 
Service and Veeam Virtualization 
Extensions UI (port number can be
chosen during setup).
 

Workstation
Web Browser

 

Veeam
Virtualization
Extensions UI
 

HTTP
 

4430
 

Required to use Veeam Virtualization 
Extensions UI from remote web 
browser (port number can be chosen 
during setup).
 

Veeam Collector
 

vSphere Host
 

HTTPS
 

443
 

This port is optional; use it only if you 
need to connect the Collector directly 
to a vSphere host.
 

Veeam
Virtualization
Extensions
Service
 

vSphere Host
 

HTTPS
 

443
 

This port is optional; use it only if you 
need to connect Veeam Virtualization 
Extensions Service directly to a 
vSphere host.
 

Veeam Collector
 

ESX Host
 

UDP
 

514
 

This port is optional; use it only if 
Syslog is required. To allow outgoing 
syslog traffic, open this port on the ESX 
host firewall.
 
Note: Not supported on ESXi.
 

Veeam Collector
 

ESX Host
 

TCP
 

22
 

This port is optional; use it only if COS 
partition usage stats are required. To 
allow outgoing SSH traffic, open this 
port on the ESX host firewall.
 
Note: Not supported on ESXi.
 

In addition to the ports listed above, the following types of communication are used between the Veeam Virtualization Extensions service and Veeam Collector service:

From To Communication Type Notes

Veeam
Virtualization
Extensions
Service

 

Veeam Collector
 

Windows Share
 

This communication type is used to 
create log bundle for the Veeam 
support, if required. Read 
permissions should be available.
 

Veeam
Virtualization
Extensions
Service
 

Veeam Collector
 

RPC
 

RPC is used for the remote control of 
the collector’s service 
(start/stop/restart).
 

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.