2 Replies Latest reply on Oct 18, 2012 11:10 AM by historicalshavlikcustomer

    Misc. issues in definition file 2.0.0.2772

    Master
      Hi,

      I have noticed the following issue using this definition version. It may have been present in previous version but I am not able to provide more info.

      KB981716 (MS10-044): appears as missing because of msaccess.exe version being less than expected (11.0.8166.0 < 11.0.8321.0) but when installing the patch manually it says : "This update has already been applied or is in an update that has already been applied".

      In the OHotfix.log generated during manual install the following lines could be found:
              Product {90110409-6000-11D3-8CFE-0150048383C9} Microsoft Office Professional Edition 2003 Version 11.0.8173.0: Already has a patch that supersedes this patch.
              Product {90110409-6000-11D3-8CFE-0150048383C9} Microsoft Office Professional Edition 2003 Version 11.0.8173.0: Already has this patch.

      Having all the patches reinstall by date fixed the issue.


      KB2535812 (MS11-036), KB2687323 (MS12-060), KB2687483 (MS12-064): When trying to push the patches with the "Push full-file patches when possible" it only works with the office2003-KB??????-Client.exe files not the office2003-KB??????-FullFile.exe files.
      If the "fullfile" file is present but not "client" file, it appears as not downloaded.
      Manually installing the "fullfile" version works fine and is then detected as installed.


      The FullFile vs Client is a bit of an issue for us as we use the DS folders as sources for machines reinstallation so having twice the files is both using disk space and making the patch installed twice during the process. We try (and succeded so far) to work with the FullFile version and it help us to keep both patching and master clean.
        • 1. Re: Misc. issues in definition file 2.0.0.2772
          Master
          In regards to Q981716/MS10-044, it may well have been the case that the update did not correctly apply. It can often be the case with Microsoft updates that once the update is seen as installed by the operating system (i.e. is enumerated as an installed update), the update installer will not execute. In cases such as this, the solution is often to manually remove the update and then re-install (as it appears that you discovered).

          In regards to Q2535812/MS11-036, Q2687323/MS12-060, and Q2687483/MS12-064, these updates must be handled uniquely due to the fact that there are two potential methods of installation (i.e. the client installation and the full file installation). In order to handle this architecture, it is necessary that we have two uniquely named files for the updates. In some cases, both files may be identical, differing only by name. In other circumstances, the two files may indeed be unique.

          The following detail on the subject (taken from our administration guide, and also available via the 'Help>Index' menu of the Protect GUI) may prove helpful:

               "For many Office patches, Microsoft provides two different patch files. A full-file patch contains entire copies of updated files, while binary or client patches contain only the differences between the original file and the updated file. The full-file patches are generally much larger files than the binary patches. The full-file patches, however, are less likely to require access to the original media. VMware vCenter Protect allows you to choose which type of patch to deploy when both types are available.
               
               Note: Only full-file patches are supported by VMware vCenter Protect Agent. Binary Office patches cannot be deployed by VMware vCenter Protect Agent."
               
               
               We would certainly encourage you to submit ideas you may have using our Feature Request submission form. If you are still unable to resolve any issues which you are having, we would urge you to contact Support directly for immediate assistance.

          • 2. Re: Misc. issues in definition file 2.0.0.2772
            Master
            Thanks a lot for the detail answer.

            For the FullFile/Client, in those case, the definition file only permit the use of the client file which is the contrary of the note you mentionned:
            "Note: Only full-file patches are supported by VMware vCenter Protect Agent. Binary Office patches cannot be deployed by VMware vCenter Protect Agent."

            I may have to precise that we use the agentless method which differ from the agent method.