WinINSTALL 8.70.04 DMS/DAS Hotfix



Base WinINSTALL Version:          8.70.0401, 8.70.0402 or 8.70.0403 (Japanese)

Hotfix WinINSTALL Version:         8.70.0404 (Japanese)


Products affected by this hotfix:



*          This hotfix contains no new fixes for DMS, so does not need to be applied if the 8.70.0403 hotfix has already been applied to DMS.  However, it can be applied to DMS with no ill effect.


Product version information:


            WinINSTALL hotfixes are cumulative, and include all fixes for issues corrected in all previous hotfixes.  However, depending on which files are updated in this hotfix or in previous hotfixes, certain areas of the product will report a product version corresponding to the previous hotfixes or the base product release.  Following correct application of this hotfix, the following versions should be observed in Add/Remove Programs (ARP), in Help / About or when viewing agent status:



ARP Version

About/Agent Version











*          After the agents are properly updated, the console will show the correct agent version (8.70.0404) when a machine is viewed.  However, when new machines are deployed from a share with the hotfix installed, they will initially show the base version (8.70.0401), but will show the correct version following the next time they are restarted.


Files included in this hotfix:



Old Version(s)

New Version





Hotfix description and installation instructions (this file).




Hotfix installation trigger file.




Updated console module for PXE Client Reset.




Updated console module for Patch Management.




Updated agent module for PXE Client Reset.




Updated post-install module for Client Reset.


Dated 9/14/2006

Dated 6/12/2007

Updated bootstrap loader for PXE Client Reset.




Updated agent module for the Publisher agent.




Updated console MSI file.




Updated agents MSI file.




Command (batch) file to update Client Reset files.


*          The WIPXECr.dll and WICRAgent.dll files are only needed for DAS, as well as WIAgents.msi.  The DMS product does not require these files, though they can be added to the DMS share with no ill effect.


Issues addressed in this hotfix:


Issue: DTR 298864 - Blank txtsetup.sif after adding OS files.


Description: For some OS/service pack combinations, the PXE server is failing to copy the txtsetup.sif file.  The PXE server was using an incorrect code page for Japanese, resulting in an invalid txtsetup.sif.


Resolution: The PXE server was fixed to use the correct code page for Japanese.


Important: After applying this hotfix, we strongly recommend that you use the console to re-add the OS files previously added to your PXE server(s).  Please see the “Post-install instructions” section at the end for more information.


Issue: DTR 298877 - PostInstall log contains invalid characters.


Description: The post-install log messages contain a mixture of Japanese and garbage characters.


Resolution: The PostInstall program now correctly passes logs containing Japanese characters to the PXE agent for logging in the database.


Important: After applying the hotfix, the PXE client logs should be cleared.  Please see the “Post-install instructions” section at the end for more information.


Issue: DTR 298872 – Unable to browse to external domains to add accounts during template creation.


Description: The console is unable to browse to external domains (other AD domains in the forest) in the domain browser on Windows Server 2003.  This works fine on Windows 2000 Server.


Resolution: A flag was added to the browser code to enable external domain browsing on Windows Server 2003.


Issue: DTR 299714 – Account to access PXE server cannot contain Japanese characters.


Description: If the user credentials contain one or more Japanese characters, setup hangs at the "Setting up Windows" phase.  This is caused by MBCS characters in the user credentials.


Resolution: The PXE server was fixed to write MBCS characters in the user credentials.


Issue: DTR 299218 – No dynamic LST files are being produced.


Description: The Publisher was not producing dynamic LST files.


Resolution: The Publisher was corrected to produce dynamic LST files.


Issue: DTR 299144 – Documentation lacking on automatic configuration of Windows firewall exclusions for the WinINSTALL agent.


Description: The information below is not presented in the documentation of the WinINSTALL PXE Client Reset feature.


Resolution: If you create a PXE reset template for Windows XP or 2003 and configure that template to both enable the Windows firewall and deploy the WinINSTALL agent, firewall exclusions for the default ports used by the WinINSTALL agent, 3674 UDP and TCP, are automatically added during the reset.  You do not need to add these exclusions yourself, and doing so will improperly configure the firewall.


Issue addressed in previous hotfixes:


Issue: DTR 296893 (17974) – Cannot download or refresh Japanese patch bulletin information with the shortcut bar closed.  (8.70.0403)


Description: In the Japanese console, if the shortcut bar is closed, patch bulletin information cannot be downloaded or refreshed.  An HTTP BAD REQUEST (400) error is received.


Resolution: With the shortcut bar closed, a garbage application name was being sent with the HTTP request.  This has been corrected.


Issue: DTR 297140 (18275) – April 2007 Japanese MSSecure.xml file no longer parsed by the console.  (8.70.0403)


Description: MSSecure.xml files prior to April 10, 2007 had an error which WinINSTALL compensated for in Patch Management.  Microsoft corrected the error in MSSecure.xml, but the code to compensate for the original error caused the file to no longer be parsed by the console for Japanese, French and German.


Resolution: The MSSecure.xml parsing code has been modified to deal with both the broken MSSecure.xml, and the corrected version.


Issue: DTR 297147 (18282) – After previous Japanese bulletin download failures, bulletins display in English and not Japanese by default.  (8.70.0403)


Description: Related to DTR 18275, if a previous download of MSSecure.xml fails, when the issue is resolved, the default language for the bulletins changes from its previous setting (e.g. Japanese) to English.  It can be manually changed back via the UI, in which case the bulletins will be downloaded in the correct language.


Resolution: The MSSecure.xml parsing code has been modified to deal with both the broken MSSecure.xml, and the corrected version.


Issue: DTR 297148 (18283) – The patch bulletins list may appear to be blank after bulletins are downloaded.  (8.70.0403)


Description: After downloading bulletins, the bulletin list may not be properly refreshed, and appears blank.


Resolution: The display issue with refreshing the bulletin list view was corrected so that the list is properly re-drawn following a download.


Issue: DTR 297149 (18288) – Reset of a Japanese system with a template that both enables the firewall and deploys WinINSTALL agents results in a corrupt SIF error.  (8.70.0403)


Description: If a Japanese XP machine is reset with the firewall enabled and the template includes deployment of the WinINSTALL agents, the reset will fail with an error regarding SIF file corruption due to use of localized (Japanese) characters in the SIF file.


Resolution: The PXE Client Reset agent was changed to generate a SIF using English characters, as Microsoft doesn’t support localized SIF files.


Issue: DTR 291057 (18183) – Optimize query for Create PXE Clients dialog.  (8.70.0402)


Description: The query for available machines in the Create PXE Clients dialog screen can cause a long delay in larger environments.


Resolution: The query has been rewritten to significantly reduce the delay.


Install instructions for this hotfix:


  1. The hotfix executable will automatically save copies of all files in a folder on the share named “8700404.BAK”.  The files within are all renamed to include a random extension so they don’t conflict with existing files.
  2. Execute the hotfix executable (WI870404.exe).  You will be prompted to locate the share to be updated, and the hotfix will be applied to the share.
  3. Start the console, which will then offer to automatically upgrade.  Allow the upgrade.
  4. From the console, re-start any agents, which will then automatically upgrade the agents:
    1. Select the machine or machines to be upgraded in the machine list.
    2. Right click / Agent Maintenance / Stop Agent / OK.
    3. Right click / Agent Maintenance / Start Agent / OK.
    4. Upon startup, the agents should update.
  5. Verify that WIPXECR.dll and WIPatchCfgu.dll (on console machines) and WICRAgent.dll (on all machines with DAS WinINSTALL agents installed) has been updated in the local \Program Files\OnDemand\WinINSTALL\Bin folder.
  6. From a command prompt, in the WinINSTALL\Bin folder, run UpdateCR.cmd.  This will update Client Reset files (PXEStart.bin and PostInst.exe) in any existing OS templates.


Note 1:  The default for all agents is to check for upgrades on startup.  Please confirm that this option has been set in Agent Settings… / Advanced / Check for upgrade at startup, and set if necessary.

Note 2:  After the DAS agents are properly updated, the console will show the correct version (8.70.0404) when a machine is viewed.  However, when new machines are deployed from a share with the hotfix installed, they will initially show the base version (actually, 8.70.0400, not 8.70.0401), but will show the correct version following the next time they are restarted (and updated).


Post-install instructions:


1.       In previous releases, there were some logging issues with PXE Client Reset where log entries were written in ANSI, resulting in logs that couldn’t properly represent Japanese characters.  Logs are now written in Unicode (fixed by DTR 298877), however existing log entries will appear garbled and may cause some console instability.  These old log entries should be purged from the database.  To purge the existing log entries:


  1. View the clients in the Clients View in PXE Client Reset.
  2. Select all of the clients.  The simplest way to do this is to select one client and use Ctrl+A, which will select all of them.
  3. Right-click on the client list and select the “Clear Log” item from the context menu.


2.       DTR 298864 addresses issues with an invalid txtsetup.sif file being created.  As a result, following installation of the hotfix, if you have added any OS files to PXE prior to application of the hotfix, those files should be re-added following application of the hotfix to gain the benefit of this fix.  The following steps are necessary, for each OS that was previously added to PXE, on each PXE server:


  1. Select the PXE server from the list and right-click.
  2. Select the “Properties” menu item.
  3. Select the “Operating Systems” tab.
  4. For each OS added to the server:
    1. Right-click and select “Edit OS”.
    2. Insert the original OS CD.
    3. Click on the “Browse…” button, browse to the OS CD, and click OK.