Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

More documents

Recommendations

Info

all the needed task sequence variables, you could get this error. 7202 ZTIConfigureDHCP.wsf Not enough values specified for scope creation. 1 5 Same as above, but you didn’t specify subnet mask, IP, or scope name properties. 7203 ZTIConfigureDHCP.wsf Not enough values provided to Set the IP range For this scope. 1 5 Same as above, but you didn’t specify the starting and ending IP address details for the DHCP scope. 7300 ZTIConfigureDNS.wsf Unable to issue DNS commands 1 5 When you add a “Configure DNS” task sequence step into the task sequence, you configure the specific DNS settings that should be configured. The ZTIConfigureDNS script builds a DNSCMD.EXE script based on these values and executes it. This error means that DNSCMD.EXE reported a nonzero return code. You can review the BDD.LOG log to see what commands failed. 77<strong>11</strong> ZTIDiskpart.wsf Disk OSDDiskIndex() can not be found! 5 7 You told MDT to format a disk with a particular index (by default, index 0) but there was no such disk. Make sure you specify a disk that exists. Assuming you are using the default disk index, this can also mean that you are missing the mass storage driver needed for the disk. 7712 ZTIDiskpart.wsf Disk () can not be formatted in OSD. 7820 ZTIDiskpart.wsf DoNotFormatAndPartition has been set to Yes, however the Target Partition for the OS could not be determined. See BDD.Log for details. 7701 ZTIDiskpart.wsf Disk is not large enough for System and BDE partitions, Required = 300MB 5 7 You told MDT to format a disk (typically with index 0) but when MDT checked the disk it found out that it couldn’t be used for an OS, typically because it’s either a removable disk or too small to hold the OS. Make sure you specified the correct disk. 1 8 The DoNotFormatAndPartition variable was set to YES, indicating that no formatting or partitioning should be done. But no operating system volume could be determined, so an error is generated at this point rather than waiting until later when LTIApply tries to figure out where to put the new OS. 1 1 This is a deceptive message, because what it is really trying to tell you is that you specified a custom value for the BdeDriveSize task sequence Page | 15
variable (used to control the size of the boot volume) that is too small. You must specify a size of 300 or higher. 7706 ZTIDiskpart.wsf ERROR! Drive was not found! 1 5 The ZTIDiskpart script formatted and partitioned a drive, but then couldn’t find the volume that it just created, so something is wrong. 7707 ZTIDiskpart.wsf ERROR! Drive is not Ready! 1 5 The ZTIDiskpart script formatted and partitioned a drive, but when checking the volume that it had just created, it found that the volume wasn’t ready, so something is wrong. 7708 ZTIDiskpart.wsf ERROR! Drive is not a fixed disk: 77<strong>09</strong> ZTIDiskpart.wsf ERROR! Files are present on was not cleaned: 7710 ZTIDiskpart.wsf ERROR! Folders are present on was not cleaned: 10201 ZTIDomainJoin.wsf Unable to Join Stop installation. 10801 ZTIExecuteRunbook.ws f 10802 ZTIExecuteRunbook.ws f 10803 ZTIExecuteRunbook.ws f Unable to create Orchestrator job for the specified runbook. 1 5 The ZTIDiskpart script formatted and partitioned a drive, but when checking the volume that it had just created, it found that the volume wasn’t reporting itself as a fixed disk, so something is wrong. 1 5 The ZTIDiskpart script just formatted and partitioned a drive, but when checking the volume it had just created, it found files on the volume. That shouldn’t happen, so something is wrong. 1 5 The ZTIDiskpart script just formatted and partitioned a drive, but when checking the volume it had just created, it found folders on the volume. That shouldn’t happen, so something is wrong. 1 8 You set task sequence variable DomainErrorRecovery to “FAIL” indicating that the ZTIDomainJoin.wsf script should force a failure if it is unable to join the specified domain. 3 8 The ZTIExecuteRunbook script tried to talk to the Orchestrator web service to create a job to run the specified runbook, but this failed. Unable to find job. 1 7 The ZTIExecuteRunbook script was able to create a job to run the specified runbook, but it was then unable to retrieve the job from the Orchestrator web service. Unable to get Orchestrator job status. 3 7 The ZTIExecuteRunbook script was not able to retrieve the status of the job created to execute Page | 16
Page 1 and 2: SEPTEMBER 11, 2012 Troubleshooting
Page 3 and 4: Document History Date September 6,
Page 5 and 6: Log files Windows logs There are se
Page 7 and 8: Smsts.log Main log file written by
Page 9 and 10: TaskSequenceProvider.log Useful whe
Page 11 and 12: 5204 LiteTouch.wsf The logged-on us
Page 13 and 14: 5614 LTIApply.wsf ERROR - Unable to
Page 15: 7102 ZTIConfigureADDS.wsf ERROR - M
Page 19 and 20: 9701 ZTIUserState.wsf Unable to fin
Page 21 and 22: Version is not supported. You must
Page 23 and 24: deployment share, but it wasn’t t
Page 25 and 26: oot sector on the boot drive. In th
Page 27 and 28: 6191 LTISysprep.wsf FAILURE: Test f
Page 29 and 30: use.”) Then BCDBoot was used to c
Page 31 and 32: emovable disk or network path. In t
Page 33 and 34: 6740 ZTIBDE.wsf FAILURE: Check to s
Page 35 and 36: 7813 ZTIDiskpart.wsf FAILURE: Verif
Page 37 and 38: means that it wasn’t able to find
Page 39 and 40: 10311 ZTIVHDCreate.wsf FAILURE: Ver
Page 41 and 42: User State Migration Tool Return Co
Page 43 and 44: An option argument is missing An op
Page 45 and 46: 12 USMT_ERROR_OPTION_PARAM_T OO_LAR
Page 47 and 48: Another process is preventing migra
Page 49 and 50: valid and that you have write acces

Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

Create successful ePaper yourself

Delete template?

Save as template?