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.
all the needed task sequence variables, you could<br />
get this error.<br />
7202 ZTIConfigureDHCP.wsf Not enough values specified for scope<br />
creation.<br />
1 5 Same as above, but you didn’t specify subnet<br />
mask, IP, or scope name properties.<br />
7203 ZTIConfigureDHCP.wsf Not enough values provided to Set the<br />
IP range For this scope.<br />
1 5 Same as above, but you didn’t specify the starting<br />
and ending IP address details for the DHCP scope.<br />
7300 ZTIConfigureDNS.wsf Unable to issue DNS commands 1 5 When you add a “Configure DNS” task sequence<br />
step into the task sequence, you configure the<br />
specific DNS settings that should be configured.<br />
The ZTIConfigureDNS script builds a DNSCMD.EXE<br />
script based on these values and executes it. This<br />
error means that DNSCMD.EXE reported a nonzero<br />
return code. You can review the BDD.LOG log<br />
to see what commands failed.<br />
77<strong>11</strong> ZTIDiskpart.wsf Disk OSDDiskIndex() can not be<br />
found!<br />
5 7 You told MDT to format a disk with a particular<br />
index (by default, index 0) but there was no such<br />
disk. Make sure you specify a disk that exists.<br />
Assuming you are using the default disk index, this<br />
can also mean that you are missing the mass<br />
storage driver needed for the disk.<br />
7712 ZTIDiskpart.wsf Disk () can not be formatted in<br />
OSD.<br />
7820 ZTIDiskpart.wsf DoNotFormatAndPartition has been set<br />
to Yes, however the Target Partition for<br />
the OS could not be determined. See<br />
BDD.Log for details.<br />
7701 ZTIDiskpart.wsf Disk is not large enough for System and<br />
BDE partitions, Required = 300MB<br />
5 7 You told MDT to format a disk (typically with index<br />
0) but when MDT checked the disk it found out<br />
that it couldn’t be used for an OS, typically<br />
because it’s either a removable disk or too small to<br />
hold the OS. Make sure you specified the correct<br />
disk.<br />
1 8 The DoNotFormatAndPartition variable was set to<br />
YES, indicating that no formatting or partitioning<br />
should be done. But no operating system volume<br />
could be determined, so an error is generated at<br />
this point rather than waiting until later when<br />
LTIApply tries to figure out where to put the new<br />
OS.<br />
1 1 This is a deceptive message, because what it is<br />
really trying to tell you is that you specified a<br />
custom value for the BdeDriveSize task sequence<br />
Page | 15
Change language