Admin Studio 9.5
Is anyone using Admin Studio 9.5 to create virtual packages, either App-V or ThinApp? I like the idea that you can create both the MSI and App-V package from the same capture, all though it looks like it is just avialable for App-V only and not ThinApp.
I would be very interested to hear if Admin Studio 9.5 can do what it states in it's advertising.
I would be very interested to hear if Admin Studio 9.5 can do what it states in it's advertising.
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Posted by:
bill_appleton
14 years ago
Posted by:
007sQ
14 years ago
I have been kicking the tires on AS 9.5's virtualization outputs.
The interest thing is it will take as input either: a) output from the IS repackager or b) an MSI file as input and then virtualize to: a) App-V, b) Thinapp, or c) XenApp.
Although I am always wary of conversions, I imported the Adobe Lightroom MSI and exported as a Thinapp Virtualized app and the application fires up and is usable with no problems.
I haven't done any forensics on what is missed with this method, but I have to assume that the results of any custom actions that would normally run are not captured. Depending on the package that could obviously be lethal.
The interest thing is it will take as input either: a) output from the IS repackager or b) an MSI file as input and then virtualize to: a) App-V, b) Thinapp, or c) XenApp.
Although I am always wary of conversions, I imported the Adobe Lightroom MSI and exported as a Thinapp Virtualized app and the application fires up and is usable with no problems.
I haven't done any forensics on what is missed with this method, but I have to assume that the results of any custom actions that would normally run are not captured. Depending on the package that could obviously be lethal.
Posted by:
TheBigSaxon
14 years ago
Ok,
I have been using ThinApp & AdminStudio 9.5 VPack and this is what I have found & my experiences:
1. ASV9.5 & TA 4.5 do not work together out of the box. Because of me, Flexera will be releasing SP2 that addresses the fact that VMWare changed the encoding on the Package.ini from UTF-8 to ANSI.
2. ASV9.5 will not automatically embed VBScripts into the project the way ThinApp packager will.
3. When you leverage MSI to V-MSI feature of ASV, you must remember that any changes made will be in the "bubble". When you build the MSI it will create another ISM that is the build ISM and changes like branding must be made there.
4. All primary data containers are set as Package.dat. That can be good & bad.
I have a number of Feature Enhancements in to Flexera for the Virt Pack. I personally do not think it is worth the ridiculous cost but the MSI to V-MSI feature is really nice.
I have been using ThinApp & AdminStudio 9.5 VPack and this is what I have found & my experiences:
1. ASV9.5 & TA 4.5 do not work together out of the box. Because of me, Flexera will be releasing SP2 that addresses the fact that VMWare changed the encoding on the Package.ini from UTF-8 to ANSI.
2. ASV9.5 will not automatically embed VBScripts into the project the way ThinApp packager will.
3. When you leverage MSI to V-MSI feature of ASV, you must remember that any changes made will be in the "bubble". When you build the MSI it will create another ISM that is the build ISM and changes like branding must be made there.
4. All primary data containers are set as Package.dat. That can be good & bad.
I have a number of Feature Enhancements in to Flexera for the Virt Pack. I personally do not think it is worth the ridiculous cost but the MSI to V-MSI feature is really nice.
Posted by:
TheBigSaxon
14 years ago
Posted by:
TheBigSaxon
14 years ago
ORIGINAL: 007sQ
I have been kicking the tires on AS 9.5's virtualization outputs.
The interest thing is it will take as input either: a) output from the IS repackager or b) an MSI file as input and then virtualize to: a) App-V, b) Thinapp, or c) XenApp.
Although I am always wary of conversions, I imported the Adobe Lightroom MSI and exported as a Thinapp Virtualized app and the application fires up and is usable with no problems.
I haven't done any forensics on what is missed with this method, but I have to assume that the results of any custom actions that would normally run are not captured. Depending on the package that could obviously be lethal.
That is the biggest thing I have run into. It works great on Repackaged MSI's but not so great on vendor MSI's.
Posted by:
TheBigSaxon
14 years ago
Posted by:
mcompton69
14 years ago
Posted by:
Mike Marino
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.