'''=== Workspace Virtualization vs Application Virtualization''': === Workspace virtualization enables individual applications to interact with each other and also enables user settings/configuration and user data to stay within the workspace. Application virtualization does not. Application Virtualization shields independent applications from each other better should one of them prove to be hostile (i.e. contains a virus of some sort).
=== Workspace Virtualization vs Desktop Virtualization ===
'''Workspace Virtualization vs Desktop Virtualization''': Workspace Virtualization runs directly on the client computer hardware whereas Desktop Virtualization in many cases runs on a remote computer somewhere over a corporate LAN/WAN or over the Internet (called Hosted Desktop Virtualization). In other cases Desktop Virtualization can be run on the client directly through a virtual machine environment such as VMWare Workstation. Because the applications in a Desktop Virtualization environment run at a different ___location, on a remote machine or in a local virtual machine, and technology simply offers a way to present the graphics interface locally using technologies such as Remote Desktop. As a result the graphics system is much slower and access to local data services such as USB or Firewire-connected cameras, scanners, & hard drives is much slower. Desktop virtualization, on the other hand, offers the advantage that the amount of time required to move from one client computer to another is small because applications, settings and data are stored locally on the client. When it comes to system resources, Workspace Virtualization requires fewer resources than Desktop Virtualization because it doesn't contain a complete copy of the operating system running in a virtualization environment.<ref>http://virtualizationreview.com/articles/2009/09/01/workspace-virtualization-grows-up.aspx</ref>
