Best Practices for Implementing Application Virtualization with ：实施虚拟化应用的最佳实践.pptVIP

Best Practices for Implementing Application Virtualization with SVS and SVS Pro;Speaker Background;Speaker Background;Agenda;All Applications have a lifecycle;“DLL Hell” is part of the Application Lifecycle;NTFS protects system and application files by restricting access to these files In Windows NT – MS released Zero Administration Kit to provide corporations with the tools to increase system lock down In Windows 2000 – MS added further restrictions to users and changed the way applications work with the OS In Windows XP and 2003 – MS added support for side by side DLL operation, even in memory In Windows Vista — MS added protection for the registry as well as system files Applications that follows the most recent guidelines for the Designed for Windows Logo program should not install any component in the system directories Windows Resource Protection Stores a backup copy of critical system files and critical registry keys %SystemRoot%\System32\DLLCache folder Special agent is constantly watching protected components Allows only OS operations to update protected files and registry keys ;Managing Windows Installer;Package for Windows Installer 4.0;Traditional software installations require a formal packaging process Rely on Wise Package Studio If moving to Vista, you must update all existing MSI packages to WIS 4.x;Traditional Application Management Woes;In comes Application Virtualization;Key AppV Features;Do Away with Application Conflicts;The SVS Filter;Build a Core OS based on a Model;Use the ‘Bull’s Eye’ Construction Model;Streaming Applications with SVS Pro;Rely on Application Streaming;SVS Pro Streaming Components;SVS Pro Streaming Architectures;Streaming and SVS;SVS Pro Desktop Management Model;Software as a Service (SaaS);How to proceed?;What to Virtualize?;Rely on AppV and Streaming;The 10 Commandments of AppV;Final Thoughts;SVS break-outs and labs;reso-net ;Resources