We are currently running a proof of concept fo VMView v5 and MA500 7.3 and FRX 6.7 is some of the apps we've been testing.
For these apps we tried thinapping and "baking" them into the parent image which we used XP Pro SP3 32bit.
Current used a Terminal Server win2k3 setup for these apps.
Results
1) Thinapping MAS500 7.3
- We were getting slow reponses when we thinapped Mas500. We tried thinapping the app together with .NET both before and after a prescan and still the logon times and such seems about 3 to 5 times slower than production. We had users actually take times on how long the login screen appeared, logging on, pulling up reports and such. Not what we expected.
2) We then decided to just bake "MAS500" into the parent vm and created a dedicted pool for these MAS users.
- Times were much better and pretty much idential to production.
a) opening up the application and getting to the login screen took 2 seconds to open versus 10 seconds in production.
b) Logging into the application tooks about 6 seconds versus 2 seconds in production. Slower in vmview.
c) But every other process was either the same time and or just a second or two slower. Pretty good.
Our test users love the fact that printing was so easy. No need to install a 3rd party app like uniprint to get printing working. Plus they like having their own virtual desktop. No more issues with the terminal server resources spiking which affects everyone else.
So for MAS500 v7.3 on VMView v5 it seems okay. We are just having issues with FRX v6.7 which is drastically slower no matter how we virtualize the app.
