Hi, new here and to Appv / sequencing.

I have an application that has been virtualized and deployed and now I need to apply a patch to it.

I opened it for UPGRADE in sequencer and ran the wizard, it created a new version but here is my problem.

We want to TEST the new version before deploying to everyone who had the old version but once I add the new version through the Management Console, it "replaces" the previous version.

Seems like the toruble is that both versions use the same name for the .OSD file.


Do I need to create a new package maybe?

Hope this makes sense and appreciate any help anyone can provide.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Joel,

When you build your sequenced package, select the option to create an MSI - (you may need to go back and do this for your 'old' package too).

That way, you can install the App-V client on a test machine, install the 'old' package MSI, launch and test then install the 'new' package MSI, launch and test. This will confirm that everything upgrades etc.

Hope this helps,

Dunnpy
Answered 06/16/2010 by: dunnpy
Red Belt

Please log in to comment
0
I am not sure that I asked my question correctly.

I was able to update my application with the patch, but I am not sure if there is a way to control the deployment of the UPDATED application.

I would like to be able to use my original Security Group to control access to the "original version" and a newly defined Security Group for the "updated version" but once the updated version is added to the management console, BOTH security groups's members now only have access to the update version.

I am sorry if I am not clear or simply missed your point.

I hope you or someone can help me.

Thanks!
Answered 06/16/2010 by: snj2000
Orange Belt

Please log in to comment
0
Joel,

I believe that is by design - because you've opened the original for upgrade, indentifiers remain the same, meaning that when you import into the console it will replace/update the 'older' one.

The only way around that is to create a new package, that includes the upgrade and add that into the console - that way it will be treated as a brand new sequenced package that you'll be able to use with the security groups.

Hope this helps,

Dunnpy
Answered 06/16/2010 by: dunnpy
Red Belt

Please log in to comment
0
Sequencer 4.5 had the option: Save as New Package, which generated a new GUID. I must say I haven't seen it in 4.6 though.....

I suppose you can get around it by changing the GUID yourself, so it will be treated as a new app. Not sure how to do it though, never had the need to try it before.

Maybe the AVE can help you with this. (Haven't had the chance to try that either, but sounds like it should make your life easier when it comes to things like this)
Answered 06/16/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
Ok, thanks so much. Creating a NEW package seems like the direction I need to go. I will start experimenting with that.
Answered 06/16/2010 by: snj2000
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity