VMworld 2011 EUC1825 VMware ThinApp Implementation and Design Best Practices Notes
Network bandwidth requirements need to be taken into consideration during the design process forThinApp.
Not all applications should use ThinApp
Follow the ThinApp Design Process
Listen to and document the customer pain points
Don't be afraid of ThinApp Steaming
Reuse existing deployment infrastructure
Don't be afraid of 3rd Party Tools
Use Case Definition
Target App List
Application Integration Design
Application Management Design
Packaging Infrastructure Standards
Deployment Infrastructure Design
ThinApp Bandwidth requirements:
ThinApp Streaming Workload is the traffic consumed by the application during the launch process
ThinApp Payload is the data containing the runtime components only
TCP/IP Overhead necessary to facilitate the ThinApp Streaming Process
ThinApp Network Impact Study Guide and ThinApp Repository Best Practices will be released soon
PowerShell can be used to Inventory deployed and remove deployed ThinApps
In place updates: Current version renamed to .1 update ran as .msi
App1.1 App1.MSI
Dependancies are included in the ThinApp. Multiple versions of Java can be packaged for different ThinApps and used on the same desktop.
Using DFS to replicate ThinApps works well
Liquidware Labs Profile Unity - ThinApp deployments and Persona management
ThinApp Factory, new version of the ThinApp Converter
Automatic conversion of MSI into ThinApps (coming soon)
Horizon App Manager
Phase 1 Saas based applications
Phase 2 ThinApp Management and Distribution (coming soon)
ThinApp management application
| Print article | This entry was posted by Mikeal on 08/30/11 at 11:21:21 pm . Follow any responses to this post through RSS 2.0. |