Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
7813 ZTIDiskpart.wsf FAILURE: Verify there are partitions<br />
defined in this Task Sequence Step.<br />
7714 ZTIDiskpart.wsf FAILURE: Verify that any Bitlocker<br />
implementation does not have<br />
EXTENDED or LOGICAL Drives<br />
1 6 The ZTIDiskpart step is running to format and<br />
partition a disk, but not partitions were defined.<br />
Make sure you define at least one partition.<br />
2 9 You have specified to create extended or logical<br />
partitions as well as to enable BitLocker. BitLocker<br />
doesn’t support extended or logical partitions. The<br />
simple solution is to not use extended or logical<br />
partitions.<br />
7718 ZTIDiskpart.wsf FAILURE: Verify drive object is created 1 2 This should not happen as this is related to internal<br />
script logic.<br />
7815 ZTIDiskpart.wsf FAILURE: Verify Partition size is<br />
Numeric: <br />
2 4 It is possible to override the partition size via a task<br />
sequence variable, e.g. OSDPartitions1Size, to<br />
specify a different size than what was configured<br />
in the “Format and Partition Disk” UI. But in this<br />
case, the variable value is not a valid number,<br />
hence the error.<br />
7817 ZTIDiskpart.wsf FAILURE: Verify There are Free drives<br />
available.<br />
7801 ZTIDiskUtility.vbs FAILURE: Verify iDisk index is numeric:<br />
<br />
3 4 Each volume that is formatted by ZTIDiskpart<br />
needs to have a drive letter assigned to it. But<br />
there are only 26 letters available, so when you<br />
run out you will see this error. (The letter can be<br />
removed after the MDT “Format and Partition<br />
Disk” step runs.)<br />
3 2 You can specify the index of the disk to be<br />
formatted by setting the OSDDiskIndex variable. In<br />
this case, the variable was set to an invalid nonnumeric<br />
value, hence the error.<br />
1 2 This should not happen as this is related to internal<br />
script logic.<br />
1 2 This should not happen as this is related to internal<br />
script logic.<br />
7802 ZTIDiskUtility.vbs FAILURE: Verify oDisk index is an object.<br />
<br />
7803 ZTIDiskUtility.vbs FAILURE: Verify Disk is correct WMI<br />
Object. <br />
7804 ZTIDiskUtility.vbs FAILURE: Verify First object is set. 1 2 This should not happen as this is related to internal<br />
script logic.<br />
7805 ZTIDiskUtility.vbs FAILURE: Verify oDisk index is an object. 1 2 This should not happen as this is related to internal<br />
<br />
script logic.<br />
7806 ZTIDiskUtility.vbs FAILURE: Verify Drive is correct WMI 1 2 This should not happen as this is related to internal<br />
Object. <br />
script logic.<br />
Page | 34
Change language