locked
application downgrade on Appv Server RRS feed

  • Question

  • Hi,
    could someone explain how a downgrade szenario on an AppV server could be established? That means for example downgrade from winzip 3.0 to winzip 2.0. Are there any actions to be done on the client side as well, I'm thinking of chached applications on clients or sft file in use etc?

    many thanks in adavance,
    Achim

    RECAC01
    Wednesday, February 3, 2010 7:00 AM

Answers

  • Hello,

    There are several ways todo it and it all depends on what you mean by a down-grade.

    1. Running an application side-by-side can be done without effort and simply by removing the "older" package (using msi-engine, removing the permissions from the app-v server or removing the advertisement in sccm) and adding the "newer" package
    2. If you want to down-grade from an active-upgrade scenario you can simply remove the reference to the new file and thus maintain the older-package. However, it is also very common to need to remove the application from the cache on any clients and any user-settings relating to the application - however that entirely depends on the application.

    /Znack
    • Proposed as answer by kirk_tnModerator Wednesday, February 3, 2010 10:17 AM
    • Marked as answer by AchimR Wednesday, February 3, 2010 2:04 PM
    Wednesday, February 3, 2010 8:16 AM
  • Hi,

    while upgrading works quite well, downgrading sometimes causes issues. As znack wrote, it sometimes is required to unload the application from the client cache. Newer clients don't seem to have much issues there, but sometimes older clients were not able to downgrade an application without unloading..

    As znack also wrote, sometimes User Setting (User cache) causes issues. Imagine that WinZip3 stores its settings in a different way then WinZip 2. Then, your App-V internal User settings for Winzip are stored in the v3 format. If you then downgrade the package, these v3 settings are injected into the (downgraded) v2 package and might cause issues.

    So: It should work, but it has to be tested (well: doesn't this apply to every change we do?)


    Falko
    • Marked as answer by AchimR Wednesday, February 3, 2010 2:04 PM
    Wednesday, February 3, 2010 10:22 AM
    Moderator

All replies

  • Hello,

    There are several ways todo it and it all depends on what you mean by a down-grade.

    1. Running an application side-by-side can be done without effort and simply by removing the "older" package (using msi-engine, removing the permissions from the app-v server or removing the advertisement in sccm) and adding the "newer" package
    2. If you want to down-grade from an active-upgrade scenario you can simply remove the reference to the new file and thus maintain the older-package. However, it is also very common to need to remove the application from the cache on any clients and any user-settings relating to the application - however that entirely depends on the application.

    /Znack
    • Proposed as answer by kirk_tnModerator Wednesday, February 3, 2010 10:17 AM
    • Marked as answer by AchimR Wednesday, February 3, 2010 2:04 PM
    Wednesday, February 3, 2010 8:16 AM
  • Hi,

    while upgrading works quite well, downgrading sometimes causes issues. As znack wrote, it sometimes is required to unload the application from the client cache. Newer clients don't seem to have much issues there, but sometimes older clients were not able to downgrade an application without unloading..

    As znack also wrote, sometimes User Setting (User cache) causes issues. Imagine that WinZip3 stores its settings in a different way then WinZip 2. Then, your App-V internal User settings for Winzip are stored in the v3 format. If you then downgrade the package, these v3 settings are injected into the (downgraded) v2 package and might cause issues.

    So: It should work, but it has to be tested (well: doesn't this apply to every change we do?)


    Falko
    • Marked as answer by AchimR Wednesday, February 3, 2010 2:04 PM
    Wednesday, February 3, 2010 10:22 AM
    Moderator