When you use the Microsoft Systems Management Server (SMS) 2003 Operating System Deployment Feature Pack to deploy an operating system image, you experience the following symptoms:

• The installation or the upgrade of an operating system takes much longer than you expect. In this situation, the Operating System Deployment Feature Pack appears to stop responding (hang) in the State Restore Phase of the operating system deployment for approximately one hour.
• If you examine the OSDAgent log file, entries that resemble the following may be logged:

  Successfully connected to server <server name>
  Failed to get response from server <server name> (10060)
  Failed to send status message 40002B67 (8007274C)

  Note These entries may indicate that only five minutes have passed between the first entry and the second entry. However, in this scenario, the OSDAgent.exe program may have stopped processing for approximately 65 minutes.
• If you examine the Statmgr.log file on the SMS site server, you notice logged entries from the client computer that resemble the following:

  WARNING: SMS_STATUS_MANAGER received a status message from component "Software Distribution" on machine "<client name>" that was reported 3583 seconds in the future.  The machine's system clock must be set ahead of the site server's clock.

  Note In these entries, the number of seconds that is displayed generally corresponds to approximately 60 minutes.

This problem occurs if the following conditions are true:

• The Windows Imaging Format (WIM) file that you deployed was created on a computer that was using standard time.
• You deployed the WIM file to a computer that has the clock adjusted for daylight saving time.
• The OSDAgent.exe program experienced a network communications failure with the SMS management point during the State Restore Phase of the deployment operation.

If you create an image from a computer that uses standard time, and then you deploy that image to a computer on which the time is updated to reflect daylight saving time, the Windows mini-Setup program incorrectly adjusts the computer clock to standard time. The system time is then corrected when the Windows Time service starts on the computer. If the system time is corrected at the same time as when the OSDAgent.exe program experiences a communications failure with the management point, the network error timeout value may change from the default value of five minutes to 65 minutes. Therefore, the State Restore Phase of the deployment operation may stop responding for 65 minutes.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, use one of the following methods, as appropriate for your situation.

Note These workarounds do not address a network communication problem that you may experience with the management point. Therefore, if you experience a network failure during the image deployment operation, you may still experience a five minute delay.

Method 1: Set the ActiveTimeBias registry entry to 0xFFFFFFFF

When Windows first starts, it adjusts the system clock as soon as it detects that the ActiveTimeBias registry value differs from the Bias registry value. This action occurs even before the mini-Setup program runs.

To work around this problem, set the ActiveTimeBias registry entry to 0xFFFFFFFF. This value corresponds to a value of -1. Windows interprets this -1 value as "Unknown." When Windows detects an ActiveTimeBias registry value of Unknown, Windows does not adjust the time. Therefore, you do not experience the problem that is mentioned in the "Symptoms" section. To set this registry value, use one of the following methods.

Method A: Set the registry value when you capture the image

Before you run the Image Capture CD Wizard, set the following registry entry on the reference computer:

Method B: Set the registry value when you deploy the image

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

When you deploy the image, add a command to the Postinstall phase that sets the ActiveTimeBias registry value to 0xFFFFFFFF. The following batch file example illustrates how to do this: Important In this batch file, you must modify the reference to "x:\windows" to match the path to which Microsoft Windows PreInstallation Environment (Windows PE) installs the image. By default, the version of Windows PE that is included with the Operating System Deployment Feature Pack uses drive X.

Method 2: Create an image from a computer that uses the current time zone settings

If you deploy an image to a computer that is in a time zone where daylight saving time is in effect, perform one of the following actions:

• Use a WIM file that was created on a computer that was in a time zone where daylight saving time was in effect.
• Use a WIM file that was created on a computer that was in a time zone that makes the same adjustment for daylight saving time. For example, use a computer that moves the time one hour ahead.

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