Microsoft KB Archive/921281

= You may receive a warning message or the Zero Touch Installation process may stop responding when you use the Solutions Accelerator for Business Desktop Deployment together with Systems Management Server 2003 Service Pack 2 =

Article ID: 921281

Article Last Modified on 11/16/2007

-

APPLIES TO


 * Microsoft Windows XP Professional
 * Microsoft Windows XP Tablet PC Edition
 * Microsoft Office Professional Edition 2003
 * Microsoft Solution Accelerator for Business Desktop Deployment
 * Microsoft Systems Management Server 2003 Service Pack 2

-





SYMPTOMS
When you use the Solutions Accelerator for Business Desktop Deployment (BDD) together with Microsoft Systems Management Server 2003 Service Pack 2 (SP2), the Zero Touch Installation (ZTI) Windows Operating System Deployment process may stop responding during the State Restore phase. When this issue occurs, you may receive the following warning message:

Security Warning The publisher could not be verified. Are you sure you want to run this software?

Note If you receive this warning message, you can respond to it by clicking Run. The process should continue until it is completed.



CAUSE
This issue occurs when the following conditions are true:
 * You use the Fully Qualified Domain Name (FQDN) in the Systems Management Server hierarchy.
 * You use the computer name of the server for the UDShare parameter and for the SLShare parameter in the CustomSettings.ini file.

Under these conditions, the Microsoft Windows operating system generates a security warning message when the ZeroTouchInstallation.vbs script runs the OSDConnectToUNC.exe file.

In most cases, you cannot see the message box, and the State Restore phase will appear to stop responding.



RESOLUTION
To resolve this issue, you must modify the ZeroTouchInstallation.vbs script. To do this, follow these steps:   In the ZeroTouchInstallation.vbs script file, locate the following lines. Line 3813:    LogInfo sLogFile, &quot;About to call OSDConnectToUNC to connect to &quot; & sServerUNC, LogTypeInfo Line 3814: sCmd = &quot;&quot;&quot;&quot; & sOSDConnectToUNC & &quot;&quot;&quot; &quot;&quot;&quot; & sServerUNC & &quot;&quot;&quot; &quot; & arrSplit(0) & &quot; &quot; & arrSplit(1) & &quot; &quot; & arrSplit(2)   Add &quot;cmd /c&quot; to the command line on line 3814, as in the following example. Line 3813: LogInfo sLogFile, &quot;About to call OSDConnectToUNC to connect to &quot; & sServerUNC, LogTypeInfo Line 3814: sCmd = &quot;cmd /c &quot;&quot;&quot;&quot;&quot; & sOSDConnectToUNC & &quot;&quot;&quot; &quot;&quot;&quot; & sServerUNC & &quot;&quot;&quot; &quot; & arrSplit(0) & &quot; &quot; & arrSplit(1) & &quot; &quot; & arrSplit(2) & &quot;&quot;&quot;&quot;  Save and then close the script file.



Steps to reproduce the issue
To see when this issue occurs in the ZTI process, follow these steps:  Run the ZTI process together with the /debug:true flag.  Review the ZeroTouchInstallation.log file. The log resembles the following: -- PHASE START ---

Using COMMAND LINE ARG: Debug = True

Using COMMAND LINE ARG: Phase = STATERESTORE

Using DEFAULT VALUE: Ini file = \\SMS01.contoso.com\SMSPKGD$\SMS00001\CustomSettings.ini

Using DEFAULT VALUE: CapiComDLL = \\SMS01.contoso.com\SMSPKGD$\SMS00001\capicom.dll

Using LOGFILE = C:\MININT\SMSOSD\OSDLOGS\Zerotouchinstallation.log OSD environment is available.

WMI is available.

...

...

...

About to call OSDConnectToUNC to connect to \\FS01\Logs Notice that the last item that is logged in the State Restore phase indicates that the ZTI process is about to call the OSDConnectToUNC.exe file. </li></ol>

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

925220 The SMS 2003 Operating System Deployment Feature Pack appears to stop responding (hang) in the &quot;State Restore Phase&quot; for over one hour

<div class="references_section">