This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Virtualization Questions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 26, 2010
12:40 PM
Virtualization Questions
I have been tasks to research more into Virtualization of Installs/Applications and I was wondering if anyone has any good reference papers/links that they can share?
1. How does Virtualization affect install creation?
2. How does Virtualization affect application creation?
3. If you have 3 different apps and 3 different installer and we want to make them Virtual installs/apps then once they are installed can they interact or are they all in different virtual windows and therefore do not have access to interact?
4. what needs to be done to convert an install/application to install and work in the Virtual machine/OS?
Thanks for any and all input.
1. How does Virtualization affect install creation?
2. How does Virtualization affect application creation?
3. If you have 3 different apps and 3 different installer and we want to make them Virtual installs/apps then once they are installed can they interact or are they all in different virtual windows and therefore do not have access to interact?
4. what needs to be done to convert an install/application to install and work in the Virtual machine/OS?
Thanks for any and all input.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 26, 2010
03:24 PM
Hi Tim,
#1 - Instead of a traditional install package, you would need the virtual package itself (basically a binary proprietary file that contains the application payload and settings).
#2 - Since application virtualization technologies do a good job of fooling applications into thinking that they are actually running in the physical environment, normally not much tweaking is needed to the application itself to get it to work virtually.
#3 - Most application virtualization technologies (such as App-V and ThinApp) have built-in support for interaction between virtual packages. App-V has a feature called dynamic suite composition (DSC) that supports specifying dependencies between virtual packages.
#4 - The system changes made by the package installation need to be captured with a capture tool such as Repackager and then converted into the binary format of the virtualization technology that you are interested in. With InstallShield, you can directly convert from ISM and MSI formats to an App-V package - in some cases it would be necessary to repackage a MSI package before conversion to an App-V package.
I hope that helps to clarify some things for you.
#1 - Instead of a traditional install package, you would need the virtual package itself (basically a binary proprietary file that contains the application payload and settings).
#2 - Since application virtualization technologies do a good job of fooling applications into thinking that they are actually running in the physical environment, normally not much tweaking is needed to the application itself to get it to work virtually.
#3 - Most application virtualization technologies (such as App-V and ThinApp) have built-in support for interaction between virtual packages. App-V has a feature called dynamic suite composition (DSC) that supports specifying dependencies between virtual packages.
#4 - The system changes made by the package installation need to be captured with a capture tool such as Repackager and then converted into the binary format of the virtualization technology that you are interested in. With InstallShield, you can directly convert from ISM and MSI formats to an App-V package - in some cases it would be necessary to repackage a MSI package before conversion to an App-V package.
I hope that helps to clarify some things for you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 28, 2010
09:59 AM
Thanks for the repy Ajay.
So by the sound of #4 the install package itself would be only used to geneate this converted binary for virtualization and therefore would no longer need to be used for user deployment. Would this not mean that Install packages and therefore Installer application would not be needed as much?
Also how does this work in an admin push senario, would it be just like pushing a new image on to uses machine? How would they go about setting admin configurations that they had control over when pushing the msi?
Oh and do you know about any limitations to what can and can not be virtualized? I saw somewhere that if you app installs device drivers then it would not be good for virtualization. So do you know anything about this?
Thanks again for you reply and any more information you can supply.
So by the sound of #4 the install package itself would be only used to geneate this converted binary for virtualization and therefore would no longer need to be used for user deployment. Would this not mean that Install packages and therefore Installer application would not be needed as much?
Also how does this work in an admin push senario, would it be just like pushing a new image on to uses machine? How would they go about setting admin configurations that they had control over when pushing the msi?
Oh and do you know about any limitations to what can and can not be virtualized? I saw somewhere that if you app installs device drivers then it would not be good for virtualization. So do you know anything about this?
Thanks again for you reply and any more information you can supply.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 08, 2010
12:04 PM
Is there any other information that I need for install application virtualization?
We would like to look more into this, but need to know what is needed, what works good, is there a trial version that we can look at to create a test install appliation for virtualization just to see how they are created and how they would work in our environment?
Any more information would be great.
Thanks,
We would like to look more into this, but need to know what is needed, what works good, is there a trial version that we can look at to create a test install appliation for virtualization just to see how they are created and how they would work in our environment?
Any more information would be great.
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 08, 2010
03:13 PM
Hi Tim,
Let me answer the questions you raised:
1. Do installs become less relevant?
It is possible to distribute just the App-V package binaries without an installation. This is the likely scenario if your own company will be pushing out this package internally. But there is a strong possibility that you may need to create an install wrapper around the App-V package if you are distributing the App-V package to your customers. InstallShield has an option for creating such a wrapper install.
2. How does an administrator push scenario work?
The admin would use Microsoft SCCM 2007 R2 (most likely) to push out the App-V package internally similar to how they use SCCM to push out MSI packages.
3. Limits on what can be virtualized?
Please see Microsoft App-V Sequencing Guide section #5 Sequencing Limitations. You can find the version 4.5 guide at the following location (should be similar to what is in the more recent 4.6 guide):
http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-45_Sequencing_Guide_Final.docx
4. Trial version available for evaluating?
InstallShield 2010 evaluation has App-V support. You would also need to get an evaluation copy of App-V from Microsoft - for this please contact Microsoft directly, they may have an evaluation of their MDOP program or some other way to evaluate App-V.
-Ajay
Let me answer the questions you raised:
1. Do installs become less relevant?
It is possible to distribute just the App-V package binaries without an installation. This is the likely scenario if your own company will be pushing out this package internally. But there is a strong possibility that you may need to create an install wrapper around the App-V package if you are distributing the App-V package to your customers. InstallShield has an option for creating such a wrapper install.
2. How does an administrator push scenario work?
The admin would use Microsoft SCCM 2007 R2 (most likely) to push out the App-V package internally similar to how they use SCCM to push out MSI packages.
3. Limits on what can be virtualized?
Please see Microsoft App-V Sequencing Guide section #5 Sequencing Limitations. You can find the version 4.5 guide at the following location (should be similar to what is in the more recent 4.6 guide):
http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/App-45_Sequencing_Guide_Final.docx
4. Trial version available for evaluating?
InstallShield 2010 evaluation has App-V support. You would also need to get an evaluation copy of App-V from Microsoft - for this please contact Microsoft directly, they may have an evaluation of their MDOP program or some other way to evaluate App-V.
-Ajay
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)