Problem Definition:

A Customer has submitted the Add/Remove Storage Form from the CloudConnect Support Portal.  The form opens a Ticket on behalf of the customer with the following information (or similar)


The customer would like to change the storage allocation of the specified virtual machine. This iCCT Article explains how to process this service request.


NOTE: Storage Allocation Requests must currently be completed by Escalation Support.  The process detailed in this iCCT Article will take effect after March 1, 2015.

Using your CloudConnect GATEWAY Account, access the VMware vSphere Client.Locate and verify the Virtual Machine Configuration and Ownership in the vSphere Client.  For information on how to locate and verify a Customer’s Virtual Machine Configuration, see iCCT-201410142 – Locating and Verifying a Virtual Machine Configuration and Ownership in the vSphere Client.

After verifying the Virtual Machine Configuration and Ownership, choose “Edit Settings.”  Note that the Virtual Machine does NOT need to be Powered Off to complete this procedure.


In the Hardware Tab of the Virtual machine Properties window, you may see one or more Virtual Disks.  The vSphere Client names disks in order of creation (Hard disk 1, Hard disk 2, Hard disk 3, etc.).  However, the Hard Disk name/number has no relationship to the Disk Number specified in the Form the Customer submitted.


In this example, the Customer specified Disk 1.The “1” in “Disk 1” corresponds to the second digit of the SCSI Virtual Device Node.  So in this case, Disk 1 is Virtual Device Node “SCSI (0:1).”  If the Customer requested Disk 0, the Virtual Device Node would be “SCSI (0:0).”  In this example, SCSI (0:0) corresponds to “Hard disk 1” as shown below:


Generally, the Disk Number submitted by the customer will be one digit lower than the hard disk name in the vSphere Client.  As such, you must always verify by matching the requested Disk number to the second digit of the SCSI virtual device node.

In this case, there is no existing Hard disk with a virtual device node of SCSI (0:1).  When the Customer is referencing a device that does not exist, the Customer is requesting we create the device.As such we must Add a Hard Disk and assign it to SCSI node (0:1) so it appears as Disk 1 to the Customer.  To add a new disk, click “Add” in the Hardware Tab.


Select the “Hard Disk” as the Device Type. Click Next.


Choose “Create a new virtual disk.” Click Next.


Specify the Capacity, this should match the size/allocation requested in GB.  Under Disk Provisioning choose “Thin Provision.”  Leave everything else as default.Click Next.


Verify the second digit of the virtual device node selected matches the Disk number specified by the Customer on the Storage Allocation Form (above).  Leave the “Mode” fields unchecked and click Next.

Review the Summary, then click "Finish."

Click OK to exit the Virtual Machine Properties Window.



If prompted by SDRS, click “Apply Recommendations.”  If you cannot Apply Recommendations, contact Escalation.



In this case, the Customer was requesting we create a new Disk.However, if the Disk node did exist i.e. Customer submitted Disk 0, one would change the disk “Provisioned Size” on SCSI Node (0:0) by selecting the disk, and typing the new disk size into the “Provisioned Size” window.Click “OK.”

Additional Information:

It is common for customers to complain that storage allocation requests have not been processed even though they have been properly processed.This is generally because the customer is unaware that they must format the storage once allocated.In order for the customer to see the additional space, the customer must open Server Manager, access the Storage Node, and choose rescan.



The additional storage is now visible to the OS and may be formatted and assigned to a volume.

Applies To:

VMware vSphere 5.5 and above.