Environment:
LDMS 9.6 (Confirmed)
May apply to earlier versions using ImageW.
Review Date:
10/24/2014
Problem:
When provisioning using ImageW, provisioning uses all drive space instead of the original size of the image.
For example: You have a captured Windows 8 image that had a 60 GB system partition when captured. When you deploy this image to a desktop that has a 500 GB hard drive, the system partition is expanded to 500 GB, leaving no unallocated space for other purposes.
Cause:
By default, ImageW uses scaling that automatically increases the captured partitions to the size of the physical drive it is deployed to. This is controlled by the /x command in the "Deploy Image" action in provisioning templates.
Solution / Workaround:
Solution 1:
Remove the /x command from the "Command-line parameters" in your Deploy Image task.
Solution 2:
Add /nos:size to your "Deploy Image" task in a provisioning template. If you don't want scaling to happen at all, use solution 1 or use a large number such as 1000g.
Example: /nos:100g will not allow a partition that is smaller than 100 GB to scale. If you have a partition captured that is 120 GB, it will scale.
Before:
After:
Other Information:
Consult the ImageW manual: http://www.terabyteunlimited.com/downloads/ifw_en_manual.pdf
