Post-installation scripts do not install programs successfully when Windows Server 2003 is installed from a Sysprep image (835330)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSWhen you configure a script or a batch file to install
programs immediately after Microsoft Windows Server 2003 is installed, the
programs that the script or that the batch file installs are not installed
correctly.
Note You only experience this problem when Windows is installed from a
Sysprep.exe image. CAUSEThis problem occurs when the script or the batch file
installs programs that must register components with the Windows Management
Instrumentation (WMI) service. In this scenario, when Windows restarts after
being installed from a Sysprep image, and when components try to register with
the WMI service, the following behaviors occur:
- The first component registration is successful.
- Subsequent component registrations are
unsuccessful.
This problem occurs because the Winmgmt.exe process is not
completely initialized when the computer restarts after the installation is
complete. Typically, the Winmgmt.exe process requires about 2 to 4 minutes to
be initialized when Windows first starts after it is installed from a Sysprep
image. When Windows starts, WMI creates an inventory of all the driver
additions and class additions to the Web-Based Enterprise Management (WBEM)
repository. During the first restart after Windows is installed, there are many
driver and class additions. Therefore, the Winmgmt.exe process requires
additional time to initialize. RESOLUTIONHotfix informationA supported hotfix is now
available from Microsoft, but it is only intended to correct the problem that
is described in this article. Only apply it to systems that are experiencing
this specific problem. This hotfix may receive additional testing. Therefore,
if you are not severely affected by this problem, Microsoft recommends that you
wait for the next Windows Server 2003 service pack that contains this
hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required to install this hotfix. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file
attributes (or later) that are listed in the following table. The dates and
times for these files are listed in coordinated universal time (UTC). When you
view the file information, it is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time tool in Control Panel.
Microsoft Windows Server 2003, 32-bit editions|
Wmiprvsd.dll | 5.2.3790.142 | 416,256 | 20-Apr-2004 | 19:57 | x86 | RTMQFE | Wmiprvse.exe | 5.2.3790.142 | 206,848 | 20-Apr-2004 | 19:57 | x86 | RTMQFE | Microsoft Windows Server 2003, 64-Bit Enterprise Edition|
Wmiprvsd.dll | 5.2.3790.142 | 1,445,888 | 17-Mar-2004 | 03:31 | IA-64 | RTMQFE | Wmiprvse.exe | 5.2.3790.142 | 731,648 | 17-Mar-2004 | 01:35 | IA-64 | RTMQFE |
WORKAROUNDTo work around this problem, insert a delay in the script or
the batch file that starts when the Windows installation is complete. If you
insert a delay of about 5 minutes between the time that Windows starts and
the time that component registration starts, the WMI service does not hang, and
all components are successfully registered. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 2/1/2006 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbfix kbQFE kbWinServ2003preSP1fix KB835330 kbAudITPRO |
---|
|