- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did a fresh capture of Visio Pro 2010 yesterday with ThinApp hotfix build 556613 and the HKLM delete keys. Visio KMS activation failed right away. I added one more delete line to the top of HKLM and the activation error disappeared. I added:
deleted HKEY_LOCAL_MACHINE\Software\Classes\AppID\
YMMV (your mileage may vary)
I would like to encourage you that, rather than be disappointed in VMware, consider that they
- Don't own the source code for Windows
- Don't own the source code for Office 2010
- Don't own the source code for the KMS server
- Are, in many cases, not able to exactly reproduce every single customer environment
yet
- They can provide multiple versions of virtual IE running side-by-side on multiple Windows version (something Microsoft doesn't offer, and they do own all the source)
- ThinApp uses a runtime baked in to the compiled package - no agent to manage
- ThinApp doesn't require a massive infrastructure to get started, and integrates well with existing infrastructure
- If you attempt to virtualize Office 2010 with Microsoft or Citrix, you still have to make use of the APP-V Deployment Kit for Office 2010
I'm a customer, just like you. I'm not a reseller or an employee of VMware. I've investigated no fewer than six application virtualization products. I think that ThinApp is right at the top in terms of ROI and simplicity. The products that can handle kernel-mode drivers (a.k.a. Acrobat) typically require an agent and a backend infrastructure.
My encouragement to you is to be patient. I've been working on virtualizing Office 2010 components (Project and Visio) for several months. I believe we (VMware and its customers) are turning a corner with this latest hotfix and registry entries, and soon we'll see consistent success in virtualizing these products. With build 556613 and the registry entries, I'm able to run virtualized Project 2010 and virtualized Visio 2010 together and in conjunction with native Office 2010 without any KMS activation issues. I didn't have to use any agents (APP-V kit), any servers (Citrix/Terminal Services), or any Visual Basic scripting (to control OSPPSVC.) This is a big step in the direction that many VMware customers have been seeking to go and now we are.
I hope you find this message is encouraging, as that is its intent. I firmly believe this community and VMware are dedicated to solving issues and advancing the cause of application virtualization.