Updated App-V package still will have impact on deployed App-V package?

Hi,

I assumed I had to make a new version of an App-V package (or at least a new Deployment type) but it seems as if also updating the App-V package will have an effect on already deployed app-v packages?

Noticed this with App-V Office 2013, did set a supersedence which deleted the Lync 2010 client. Users who had the App-V Office 2013 client mentioned their Lync 2010 got suddenly uninstalled(?)

I really like to know what's happening since I regularely update packages and, like now, would like to send an updated configfile of an App-v package. Is it enough to update the package (thought not)?

Pls advise.

September 1st, 2015 11:33am

Those are two different things. Changing the content of an application will not affect already performed deployments, but changing the configuration of the application can affect already performed deployments. That can happen during the next Application Deployment Evaluation Cycle.
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2015 2:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics