--- title: "About VESServer Parameter" description: "This section describes how to work with an optional connection parameter in VEShell. Most VEShell cmdlets support an optional –VESServer connection parameter." canonical: "https://helpcenter.veeam.com/docs/mp/veshell/connection_parameter.html" breadcrumb: "Veeam MP VEShell Reference > About VESServer Parameter" dateModified: "2026-09-10" --- # About VESServer Parameter This section describes how to work with an optional connection parameter in VEShell. ## Description Most VEShell cmdlets support an optional `–VESServer` connection parameter. This parameter allows you to specify options for connecting to the Virtualization Extensions Service. The following VEShell cmdlets support the `–VESServer` connection parameter: - [Add-MonitoringGroup](add-monitoringgroup.md) - [Add-VMwareServer](add-vmwareserver.md) - [Disable-Monitoring (VMware)](disable-monitoring.md) - [Disable-Monitoring (Hyper-V)](disable-monitoring_hv.md) - [Enable-Monitoring (Hyper-V)](enable-monitoring_hv.md) - [Enable-Monitoring (VMware)](enable-monitoring.md) - [Get-Collector](get-collector.md) - [Get-CollectorJobs](get-collectorjobs.md) - [Get-GlobalCollectorSettings](get-globalcollectorsettings.md) - [Get-HypervServer](get-hypervserver.md) - [Get-License](get-license.md) - [Get-MonitoringGroup](get-monitoringgroup.md) - [Get-VESettings](get-vesettings.md) - [Get-VMwareServer](get-vmwareserver.md) - [Install-License](install-license.md) - [Invoke-LoadBalance](invoke-loadbalance.md) - [Invoke-RebuildTopology](invoke-rebuildtopology.md) - [Move-Collector](move-collector.md) - [Move-CollectorJobs](move-collectorjobs.md) - [Remove-MonitoringGroup](remove-monitoringgroup.md) - [Remove-VMwareServer](remove-vmwareserver.md) - [Rename-MonitoringGroup](rename-monitoringgroup.md) - [Set-VESettings](set-vesettings.md) - [Set-VMwareServerConnectionSettings](set-vmwareserverconnectionsettings.md) - [Set-VMwareServerNewJobPlaceholder](set-vmwareservernewjobplaceholder.md) - [Set-VMwareServerProxySettings](set-vmwareserverproxysettings.md) - [Test-VMwareServerConnection](test-vmwareserverconnection.md) - [Unregister-Collector](unregister-collector.md) By passing the `–VESServer` parameter to a VEShell cmdlet, you can define the name of the server where the Virtualization Extensions Service runs, port that the Virtualization Extensions Service "listens" and credentials of the user account under which the cmdlet configuration task will be performed. Thus, you can configure Virtualization Extensions Service running on the local computer or any remote machine of your choice. By default, if the `–VESServer` parameter is not passed to a cmdlet, the configuration task will be performed for the Virtualization Extensions Service on the localhost. This will use the default 8084 port number and credentials of the user who launched the VEShell console. You can override this default behavior by using the [`Start-VEShellClient`](start-veshellclient.md) cmdlet. ## Parameter Values You can pass with the `–VESServer` parameter the following types of values: `` or `Veeam.Psves.VesConnection` object. ### \ The `` value specifies the name of computer on which the Virtualization Extensions Service runs. Acceptable formats for the input value are: server name (such as "localhost"), IP address (such as "172.15.19.6") and FQDN (such as "localhost.veeam.local"). ::: note If the `` value is passed in the `-VESServer` parameter, VEShell creates and opens a new connection session before executing the cmdlet. The connection session is created with the following properties: computer name passed with the `-VESServer` parameter, the default **8084** port number and credentials of the user who launched the VEShell console. After the cmdlet execution is completed, the connection session is closed automatically. ::: ### Veeam.Psves.VesConnection The `Veeam.Psves.VesConnection` object stores settings for connecting to the Virtualization Extensions Service: the name of the server where the Virtualization Extensions Service runs, port that the Virtualization Extensions Service "listens" and credentials of the user account under which the configuration task will be performed. This object allows you to explicitly specify server name, user name, password and port number for connecting to the Virtualization Extensions Service. This can be extremely useful for VEShell scripting. Before you can pass the `Veeam.Psves.VesConnection` object, you need to create a connection session object using the [`New-VEConnection`](new-veconnection.md) cmdlet. The `-VESServer` parameter accepts the created connection session object as the input value. ::: note If the `Veeam.Psves.VesConnection` object is passed in the `-VESServer` parameter, VEShell automatically opens a connection session for the specified Virtualization Extensions Service before executing the cmdlet. This session is not closed after the cmdlet execution is completed. To close the session manually, use the [`Disconnect-VE`](disconnect-ve.md) cmdlet. ::: ## Related Topics [Getting Started with VEShell](getting_started_with_veshell.md)