Documentation

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

Amend RAM Total

Operation Information

This operation will amend the amount of RAM for a VMware vSphere Virtual Machine.

Extra Credentials

This operation requires an extra credential to be provided, stored in KeySafe, to the following specification:

  • Credential Reference: credential1
  • Credential Keysafe Key Type: Username + Password

Input Parameters

Name Type Description Required Sensitive
VMName string The name of the Virtual Machine to perform the action against Yes No
Port string Specifies the port on the server you want to use for the connection No No
Protocol string Protocol No No
NoTrustedCert boolean Specifies if the Connect-VIServer cmdlet will establish the connection without taking into account that the certificate is invalid Yes No
AmendBy decimal Specifies the amount of RAM (GB) to amend the total by - supports either a positive (2 for example) or negative (-0.5 for example) double Yes No

Output Parameters

Name Type Description Required Sensitive
outcome string Outcome of the operation. Can be OK, WARN or FAIL Yes No
errors string Any errors returned by the operation No No
warnings string Any warnings returned by the operation No No
oldTotal decimal The amount of RAM before the operation was run No No
newTotal decimal The amount of RAM after the operation was run No No
In This Document