Error using ZTIConfigure.wsf script
-
Thursday, December 01, 2011 10:13 PM
I hope someone can help me understand an error message I am receive when running a zero-touch deployment from Configuration Manager 2007. Sometimes when running the Task Sequence to install Windows 7 a status message is returned for the "Configuration" task (the one that follows the "Applying Network Settings") (see below). I can not find much information on what it means when ZTIConfigure.wsf returns "Unterminated opaque block - matching end tag not found". This error occurs infrequently, but when it does the OS deployment does not complete. Any information will be appreciated.
Command line for extension .exe is "%1" %* Set command line: Run command line Working dir 'not set' Executing commandline: Run command line Process completed with exit code 1 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. ????4???????????4??????????????????????????????????Command line returned 1 C:\_SMSTaskSequence\WDPackage\scripts\zticonfigure.wsf(634, 14) Windows Script Host: Unterminated opaque block - matching end tag not found : script ??????????????????????????????????????????????????????????????????4???›???
All Replies
-
Friday, December 02, 2011 12:06 AM
The configure action injects some of the properties gathered into the unattend.xml. Review the ZTIGather.log for strange/extended characters, and the unattend.xml file in your settings package for missing tags,
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch -
Friday, December 02, 2011 7:55 PM
Thank you for the information Johan. I will have to take a close look at the logs.
FYI, the task sequence I use gathers only local data and does not use an unattend or sysprep answer file. The ZTIconfigure.log file shows that there is some data being written to C:\WINDOWS\panther\unattend\unattend.xml but that file is gone after the deployment finishes.
-
Saturday, December 03, 2011 3:21 PM
The SCCM 2007 Zero Touch sequence does use an unattend.xml, the one in the settings package, and the mini-setup always use an unattend.xml, otherwise it would stop and prompt you for OOBE information.
Just add a pause in the task sequence directly after the Configure action, and you can review the unattend.xml file.
A pause could be a simple vbscript, I use the below for pausing in WinPE (the Configure actions runs in WinPE).
Set fso = CreateObject("Scripting.FileSystemObject")
filespec = "X:\go.txt"'Check every 1 second to see if the file exists
While Not fso.FileExists(filespec)
Wscript.Sleep 1000
Wend'When it does exist, delete it and go on
fso.DeleteFile(filespec)/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch- Marked As Answer by mpbaird Tuesday, December 06, 2011 2:27 AM
-
Tuesday, December 06, 2011 12:50 AM
This is good information Johan. I have used it, and have found that the problem is that the ZTIConfigure.wsf script is sometimes corrupted when the Task Sequence is run. I paused the tasks and looked at the script; it ends half way through line 635. This would explain why the Command line returned "1 C:\_SMSTaskSequence\WDPackage\scripts\zticonfigure.wsf(634, 14)".
I am not certain why sometimes only a part of the file gets copied into the script folder. I think I will make a new group in the sequence that "Uses Toolkit Package" if there is an error running the Configure task. I believe this is the that task copies the scripts into the correct subfolder.
I would be interested in hearing what you have to say about this condition.
-
Tuesday, December 06, 2011 2:27 AM
Boy do I feel stupid. After posting the last message I decided it would be a good idea to check every distibution point in my site to be certain the ZTIConfigure.wsf file was the same. I found one DP that had the bad script file. This explains why the failure only occured some of the time.
Thank you Johan for your help, it was very valuable.
-
Sunday, September 09, 2012 6:56 PM
Hi,
Thank You for this thread... I resolved my issue by putting respective scripts in %SystemDrive%\Support folder. At the end of the build, I deleted these files and cleaned sim file. Thank you for giving hint about vbscript issue. I spent almost three days to resolve this issue.

