More than one application virtualization solution?
I'm looking to see if anyone out there has had to support a mixed application virtualization environment. I'm being asked about it and I can see the advantage of one product virtualizing applications that another cannot do but is this really strategic for an organization? I can see the packaging team having to be proficient with two virtualization technologies, Windows Installer, and legacy installers so that's already a tall order to fill from a skill set standpoint. Do people see this as an effective way to keep applications virtual or has this become a skill set / management nightmare?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
jfd3
16 years ago
Hi,
We will probably have at least 2 virtualization technologies... Encapsulation and redirection... They both have their strengths and weaknesses, to together we will be able to use this technology in a wider breadth of applications.
I do get the look from management sometimes when it comes to the reasoning why not only one virt tech... But the promise of what the technologies can do for us will far out strip the overhead of learning how to package the different virt technologies...
We will probably have at least 2 virtualization technologies... Encapsulation and redirection... They both have their strengths and weaknesses, to together we will be able to use this technology in a wider breadth of applications.
I do get the look from management sometimes when it comes to the reasoning why not only one virt tech... But the promise of what the technologies can do for us will far out strip the overhead of learning how to package the different virt technologies...
Posted by:
Randhir_T
16 years ago
Posted by:
BadShadd
16 years ago
More than one AV vendor product? No, but my customer has decided on mixed SoftGrid desktop implementation environments. For approx. 85% of the 'well connected' clients, the basic SoftGrid streaming implementation will be used. For the remaining 15%, SMS (already in place) will be used to deliver MSI Utility packaged SoftGrid-enabled apps to poorly connected, slow network connectivity clients where a majority of the client base needs the app. If only a few poorly connected clients need the app, a Helpdesk person will install the preconfigured MSI Utility packaged SoftGrid-enabled app.
Are there really customers out there that have the money to spend on multiple AV vendor solution implementations? I think MS's investment to implement / offer a non-streaming solution to SA customers was a big step in the 'right' direction. I'm not working with SoftGrid for TS so I haven't studied the ins / outs of its use, but I think that the MSI packaging for SoftGrid could cut the need for the SoftGrid streaming architecture as well.
Are there really customers out there that have the money to spend on multiple AV vendor solution implementations? I think MS's investment to implement / offer a non-streaming solution to SA customers was a big step in the 'right' direction. I'm not working with SoftGrid for TS so I haven't studied the ins / outs of its use, but I think that the MSI packaging for SoftGrid could cut the need for the SoftGrid streaming architecture as well.
Posted by:
kkaminsk
16 years ago
Well I know of a site that is running three solutions right now but that can be the nature of the beast in a larger organization where there might not be an overall architectural view and business units engage in the technology that they choose. I should say that I have also seen weird mixtures of technologies in government organizations such as a territorial or national governments.
The one idea I found interesting is to heavily invest in one virtualization solution and then use a backup virtualization solution that might be significantly different. For example use a full virtualization technology such as SoftGrid or Thinstall then use SVS for the situations where full isolation is a bad idea or maybe something the 4GB SoftGrid barrier causes a niche implementation scenario. It's still unlikely that you will get a 100% virtual application environment and you do pay more of a premium for the licensing. The other downside I find with that scenario is proficiency and the ability to attract talent. If you think it's hard to find an expert with virtualization technology X then try and find one that is an expert in more than one technology. Also the staff that can be effective with multiple technologies will probably be seeking a compensation premium from their employer as well.
I was curious to see how many people are doing this and I don't think many people are but it was interesting to talk to some people who are running such a configuration and finding out why they decided to run the configuration. It seems to be more of a political driver than a technical driver that causes these implementations but it could be more common as companies buy into application virtualization. An acquisition of another company could easily trigger this architectural situation.
The one idea I found interesting is to heavily invest in one virtualization solution and then use a backup virtualization solution that might be significantly different. For example use a full virtualization technology such as SoftGrid or Thinstall then use SVS for the situations where full isolation is a bad idea or maybe something the 4GB SoftGrid barrier causes a niche implementation scenario. It's still unlikely that you will get a 100% virtual application environment and you do pay more of a premium for the licensing. The other downside I find with that scenario is proficiency and the ability to attract talent. If you think it's hard to find an expert with virtualization technology X then try and find one that is an expert in more than one technology. Also the staff that can be effective with multiple technologies will probably be seeking a compensation premium from their employer as well.
I was curious to see how many people are doing this and I don't think many people are but it was interesting to talk to some people who are running such a configuration and finding out why they decided to run the configuration. It seems to be more of a political driver than a technical driver that causes these implementations but it could be more common as companies buy into application virtualization. An acquisition of another company could easily trigger this architectural situation.
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.