SovLabs Support Portal will be moving soon!

SovLabs Support

Submit a Ticket My Tickets

SovLabs Property Toolkit - Add Disks Approval Policy


Starting with plugin version 2019.16.0 a new feature was introduced to add Disks (up to 15) to a Virtual Machine using custom SovLabs properties. This is done by leveraging the Approval Lifecycle of VM provisioning to assign disks prior to MachineRequested.



  1. vRA Versions Supported: 7.5 and 7.6
  2. Minimum SovLabs Plug-in Version:  2019.16.0
  3. Approval Policy Type: Service Catalog - Catalog Item Request - Virtual Machine
  4. Target vRA Composite Blueprint with Cloned Machine Build type and with total capacity/maximum storage that can support the disks to be added
  5. Logged in with ID that is vRA Tenant Administrator or Approval Administrator and entitled to SovLabs Modules.


Create the Approval Policy.

  1. From the vRA Catalog, Search for "Manage Property Toolkit Approval Policies - SovLabs Modules".
  2. Click Request.
  3. Complete the Approval Policy Creation form. Select Create > Service Catalog - Catalog item Request - Virtual Machine > Input a New Policy Name. Submit and make sure a new Approval Policy is created.

Add Approval Policy to Entitlement(s).  Steps below must be repeated for each Business Group Entitlement if multiple.

  1. Browse to Administration > Catalog Management > Entitlements.
    1. Select the Entitlement for the target Business Group.
    2. On the Items & Approvals Tab, Select the Entitled Item or the '+" sign to add the desired Composite Blueprint to the Entitled Item list.

  2. Once the Entitled Item is identified Select the Down Arrow to Modify the Policy.
  3. In the new Window, Click on "Show All" and select the Approval Policy created in the First Step above.

Test the Approval Policy on a Blueprint Request

  1. Go to Catalog Items >  Select the Composite Blueprint with the modified Entitlement, Request. (Note: Make sure the Business group used matches the Business Group where the Approval Policy was added to the Entitlement Item above.)
  2. At Request Time on the Deployment or Machine add the following Properties: (substitute # for the number value of next disk available on the template [ ex: SovLabs_VM_Disk1-Label])

    Property Name

    Property Value


    {any string}


    {any number in GB}

  3. Once provisioning is Completed - Go to Deployments > View Details > Click on Machine Component > Storage Tab. Verify the additional Disk Size and Label appear on the VM.

Advanced Design

  1. Additional Disks can be added by adding the property SovLabs_VM_Disk#-Size to any request. This supports adding up to 15 total disks to a blueprint.
  2. Properties can be added via Property Toolkit Template Engine logic.
  3. Properties can be made selectable via Property Dictionary/Custom Form logic.
  4. Properties can be specified within any standard Property location and will be rendered as part of the request. (VM, Deployment, Business Group, Reservation.

Extended Usage Properties

SovLabs_VM_Disk#-Size is the only required Custom Property that is needed to add an additional disk.

  • Size/Capacity: SovLabs_VM_Disk#-Size
  • Value: <user chooses number within maximum storage limit>
  • e.g. SovLabs_VM_Disk1-Size, SovLabs_VM_Disk2-Size
  • The other Disk# Custom Properties below are optional and do not need to be added:
  • Storage Reservation Policy: SovLabs_VM_Disk#-StorageReservationPolicy
  • Value: <user leaves blank/does not add property or user specifies a Storage Reservation Policy>
  • Storage Reservation Policy Mode: SovLabs_VM_Disk#-StorageReservationPolicyMode
  • Value: <user leaves blank/does not add property or allocate disk to the best available storage reservation policy>
  • Label: SovLabs_VM_Disk#-Label
  • Value: <user leaves blank/does not add property or user specifies the disk's label>
  • Device ID: SovLabs_VM_Disk#-DeviceID
  • Value: <user leaves blank/does not add property or user specifies the disk's SCSI>
  • Active: SovLabs_VM_Disk#-Active
  • Value: <user leaves blank/does not add property or user specifies disk as active or inactive>
  • FS: SovLabs_VM_Disk#-FS
  • Value: <user leaves blank/does not add property or user specifies disk's file system for Windows guest agent (gugent)>
  • FileSystem: SovLabs_VM_Disk#-FileSystem
  • Value: <user leaves blank/does not add property or user specifies disk's file system for Linux guest agent (gugent)>
  • Letter: SovLabs_VM_Disk#-Letter
  • Value: <user leaves blank/does not add property or user specifies disk's drive letter or mount point>
  • Storage: SovLabs_VM_Disk#-Storage
  • Value: <user leaves blank/does not add property or user specifies the datastore on which to place disk>
  • Percent: SovLabs_VM_Disk#-Percent
  • Value: <user leaves blank/does not add property or user specifies the percentage of the disk to be formatted by a guest agent>
  • IsFixed: SovLabs_VM_Disk#-IsFixed
  • e.g. SovLabs_VM_Disk#-Size and SovLabs_VM_Disk#-size will set the Disk# capacity

Known Behaviors

vRA Machine Properties

  • Able to obtain vRA Custom Properties from: 1) vRA Business Group, 2) vRA Property Groups ,3) vRA Deployment for the vRA Blueprint, 4) vRA Reservation Policy, and 5) vRA Machine Properties for the Machine Component
  • Unable to obtain vRA Custom Properties from: 1) vRA Reservation, 2) vRA Compute Resource, 3) vRA Endpoint
  • If utilizing SovLabs Property Toolkit (e.g. SovLabs_CreateProperties_ and/or SVL_)
  • vRA Machine Properties are rendered 3 times
  • Note:
  • If the same property is manually added at request time in both the deployment level and machine level, the deployment level will be used
  • e.g. SovLab_VM_Disk1-size : 2 is manually added on the deployment level and SovLab_VM_Disk1-size : 5 is manually added on the machine level, then Disk1 size will be set to 2
  • This only pertains to if a user tries to manually set the same Disk# Custom Property at request time on both the machine and deployment level, otherwise the properties behave as expected

vRA Disk Properties

  • VirtualMachine.Disk#.Size is the only required Custom Property to add a new disk
  • If the Disk#.Size exceeds the total capacity for the blueprint, vRA will throw an error
  • VirtualMachine.Disk# must increment in sequential order, or that disk will not be added
  • Disk# properties cannot be manipulated if it is from a Cloned Machine Build/template, even if VirtualMachine.Disk# properties are set such as VirtualMachine.Disk0.Label, Size, etc.
  • In this case, users can set the next Disk# value and increment from there
  • e.g. Disk0, Disk1, and Disk2 have been cloned over. Only Disk3 and above can be manipulated with SovLabs_VM_Disk#-
  • For Create Machine Builds, Disk0 must be manually added (+New) in the Storage tab or the blueprint cannot be published
  • Since this is a Create build, all disk properties can be manipulated, even Disk0.
  • Changing volumeId does not change the ordering of the disks, but the property will show in the "Custom Properties" in the Storage tab for that Disk
  • Disk ordering is determined by VirtualMachine.Disk#
  • Unlike other machine properties, VirtualMachine.Disk# properties do not get added in the "Properties" tab for a Machine
  • Some properties will get added to the "Custom Properties" for the Disk
  • By default, Name is set to "Hard Disk #" and that name shows up in vcenter
  • Note: Disk ID # starts at 0 in vRA, but in vcenter, Hard Disk # starts at 1
  • The other Custom Properties of id, userCreated, IsFixed, IsClone, volumeId, Name, Label, DeviceID is handled by vRA if left blank
  • If left blank, DeviceID is set to a SCSI value

Additional information

Property Toolkit :
SovLabs Template Engine :

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.