Patching Symantec

Good article post over at boardfish (second post down on the page) on patching using the msp files. Its similar to the method I advocate.
I’m really not sure why they have him create a second administrative install point for the second patch.
Also not sure why you’d patch the install point and then reinstall from there instead of merely rolling the patches to the clients.
Are we free to use any MSI method we prefer? Or are there Symantec specific ways of doing things?

2 Comments

  1. Yeah, duncan seemed to disappear that board and several of his other ones a few weeks ago.
    Symantec has reported that they will be reopening their community forum. I haven’t found that link yet though.
    I’ve retrieved that page through the google cache, here’s what I was refering to:
    “I did some research for you on this by consulting with fellow TAMs and searching our knowledge base.
    Although development has not confirmed it, the word in TAM-land is that you ­can `doublepatch` the installation. You can go from 10.0.2.2000 directly to 10.0.2.2021 for example.
    To do this, you would first merge the original msi package with MP2 bringing you up to 10.0.2.2020. Then you use that newly created package as a base to merge with the point patch, creating a 10.0.2.2021 package.”
    Situation / Metro Search Description:
    You would like to upgrade your clients to Symantec AntiVirus Corporate Edition (SAVCE) directly to 10.0.2.2021 from SAVCE 10.0.2.2000
    Solution:
    First you must merge the 10.0.2.2000 (MR2) installer with the SAVCE 10.0.2.2020 (MP1) maintenance patch.
    1. Copy the SAV folder from the root of the 10.0.2.2000 CD or other source to a temporary working directory. For this example we will use C:\PreMerge
    2. From a command prompt or run line, execute the following command
    msiexec /a “c:\PreMerge\symantec antivirus.msi”
    3. When prompted for a location to save, chose another temporary location. For this example we will use C:\Merged
    4. Copy the sav_10.0.2.2020_allwin_en.msp patch to the C:\PreMerge folder
    5. From the Windows Taskbar, click Start > Run (optionally you can open a cmd window as well)
    6. In the Open box, type the following:
    msiexec /a “C:\Merged\Symantec AntiVirus.msi” /p “C:\PreMerge\sav_10.0.2.2020_allwin_en.msp”
    7. When prompted for the path, use the same path you defined in step 3, or for this example, C:\Merged
    8. From the same source used in step 1, copy all the files from the SAV folder except the Data1.cab, Symantec Antivirus.msi, and vdefhub.zip into the C:\Merged folder.
    At this point you have created a patched version of the Symantec AntiVirus installer in the C:\Merged folder that will install SAVCE directly to 10.0.2020 (MR2+MP2).
    Next you need to merge the patched 10.0.2.2020 installer you created previously with the 10.0.2.2021 (MR2+MP1+PP1). The steps to merge the current point patch are outlined below.
    1. From a command prompt or run line, execute the following command
    msiexec /a “c:\Merge\symantec antivirus.msi”
    2. When prompted for a location to save, chose a new temporary location. For this example we will use C:\Merged2
    3. Copy the sav_10.0.2.2021_allwin_en.msp to the C:\Premerge folder
    4. From the Windows Taskbar, click Start > Run (optionally you can open a cmd window as well)
    5. In the Open box, type the following:
    msiexec /a “C:\Merged\Symantec AntiVirus.msi” /p “C:\PreMerge\sav_10.0.2.2020_allwin_en.msp”
    6. When prompted for the path, use the same path you defined in step 2 above, or for this example, C:\Merged2
    7. From the same SAVCE 10.0.2.2000 source used in the initial step 1, copy all the files from the SAV folder except the Data1.cab, Symantec Antivirus.msi, and vdefhub.zip into the C:\Merged folder.
    At this point, the contents of the C:\Merged2 folder are the source files needed to install directly to SAVCE 10.0.2.2021 (MR2=MP1+PP1)
    To upgrade SAVCE 10.0.2.2000 systems you need to execute the following command line
    msiexec.exe /fva “‘ REINSTALLMODE=amus
    The steps required for other builds would be similar except for the .msi and .msp files used.

Comments are closed.