Figure 2 - uploaded by Tom Olzak
Content may be subject to copyright.
Source publication
Current security issues caused by an increasing number of threats, application vulnerabilities, and the growing complexity of many computing environments is making traditional approaches to system maintenance and support very difficult—or impossible—to manage. Even the best attempts to maintain up-to-date endpoint device environments—including oper...
Contexts in source publication
Context 1
... clarification, let's examine what this does not include. Figure 2 is what many think of when discussing desktop virtualization. Instead of permanently installing applications on users' endpoint device, they are installed in virtualized server environments. ...
Context 2
...
Figure 2 is what many think of when discussing desktop virtualization. Instead of permanently installing applications on users’ endpoint device, they are installed in virtualized server environments. They might also be installed on blade servers, with each blade corresponding to a single desktop device. Finally, thin clients accessing terminal services or Citrix sessions are sometimes running virtualized desktops using solutions like SoftGrid. These are examples of server-based computing, and they do not fall within the definition of “virtualized desktops” used in this paper. One big problem with this approach is leaving unused a significant amount of processing potential in the form of desktop fat clients. Now let’s take a look at a virtualized desktop environment that uses the power available. Figure 3 depicts a Microsoft SoftGrid-enabled desktop. Each application runs in an isolated environment. Although the applications share OS services and hardware resources, components unique to each application (e.g. registry entries, dynamic link libraries, COM objects, etc.) can be private to that application—running within the application “sandbox.” This approach does not virtualize the OS: just the ...
