Search Engine: Elastic

Article ID: 115400, created on Jan 11, 2013, last review on May 9, 2014

  • Applies to:
  • Operations Automation


A customer with existing Hyper-V Virtual Machine subscription ordered additional hard drive to their VM and paid the order. Parallels Automation completely provisioned customer's order, however the new drive was not actually added to the customer's VM.


The possible reason of the problem is that Provider incorrectly configured resources in the Service Template which POA is using to create Hyper-V subscriptions - resources with the same Hyper-V VM add-on ID are included in the Service Template with different limits on them.

Another reason of the problem is incorrect configuration of Service Plan in PBA - resource rates for additional hard drive resources are created with improper limits or not created at all.


Make sure that only one instance of Resource Type with each of additional hard drive ID is included into POA Service Template:
  • Hard Disk #2
  • Hard Disk #3
  • Hard Disk #4

Follow the steps below to check resources in Hyper-V Service Template:

  1. Log into POA Provider Control Panel
  2. Go to the list of resources in the Service Template used to provision Hyper-V VMs
  3. Click on the Resource Type representing additional VM hard drive
  4. Find VM add-on ID on the Activation Parameters tab in resource properties in the Application Resource field
  5. Repeat the steps 3-4 for all HDD add-on resources

Service Template should not contain more than one resource with the same add-on ID - Hard Disk #2, Hard Disk #3 or Hard Disk #4.

Also, check if correct (non-zero at least) limits are set for the corresponding resources in the Service Plan in PBA (because limits from PBA Service Plan override limits configured in POA Service Template).

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF