The deployment strategies that the previous section describes are traditional. You install an
operating system on a physical PC. However, desktop virtualization enables new deployment
scenarios that can streamline and simplify Windows 8 deployment.
Windows To Go
Windows To Go offers a new alternative to traditional operating system deployment.
Windows To Go is a Windows 8 Enterprise feature that enables users to boot and
run Windows 8 from a USB drive. It provides a flexible way for workers to access their
personal desktop on any PC. The article “Windows To Go: Feature Overview” at
http://technet.microsoft.com/en-us/library/hh831833.aspx provides additional information
about Windows To Go as well as step-by-step instructions for preparing, securing, and
managing Windows To Go devices.
Virtual Desktop Infrastructure
Microsoft Virtual Desktop Infrastructure (VDI) is an alternative desktop delivery model that
gives users secure access to centrally managed desktops running in the datacenter. VDI is
powered by Remote Desktop Services (RDS), which is a server role in Windows Server 2012.
It provides a single platform to deliver any type of hosted desktop, and RemoteFX provides
a consistently rich user experience. RDS enables organizations to choose the deployment
method that works best for them—all by using a single platform.
through a SharePoint portal, on a local desktop, or over the Internet.
pool to users. When they log off a VM, VDI returns it to the pool for use by another
user.
With all three VDI deployment methods, user state virtualization maintains users’ data
and settings across physical and virtual sessions. VDI empowers enterprises with unified
management of centralized desktops and corporate data by using System Center 2012. IT can
extend existing management tools and processes to the VDI environment.
Partner technology, such as Citrix XenDesktop, adds value to VDI by offering additional
scale and flexibility to enterprises. With Citrix technologies, users can access their Windows
environment even from non-Windows devices.
Chapter 11, “Windows 8 virtualization,” provides more information about Windows 8 and
VDI. You can also learn more on the Desktop Virtualization website at http://www.microsoft
.com/dv .
Client Hyper-V
On PCs running Windows 8, Client Hyper-V provides a robust virtual platform for d evelopers
and IT pros. It supports a broad range of devices and leverages the driver ecosystem of
Windows 8 to run on the broadest range of 64-bit PCs. Client Hyper-V provides a rich user
experience, including multimedia, touch, and USB support. Because Client Hyper-V is a core
part of Windows 8, it leverages all of that operating system’s security and management
features.
Client Hyper-V requires the following:
■ A 64-bit system
■ 4 GB of RAM is required
■ Support for Second Level Address Translation (SLAT)
SLAT unloads from the processor the process of mapping physical memory to v irtual
memory. For intensive graphics, it provides significant performance improvements. It
is r equired for Hyper-V on Windows 8, because most systems have extensive graphics
capabilities. It’s only required for Windows 8 Server when enabling the RemoteFX role service.
For more information, see the article “Client Hyper-V” at http://technet.microsoft.com/en-us/
library/hh857623.aspx.
operating system on a physical PC. However, desktop virtualization enables new deployment
scenarios that can streamline and simplify Windows 8 deployment.
Windows To Go
Windows To Go offers a new alternative to traditional operating system deployment.
Windows To Go is a Windows 8 Enterprise feature that enables users to boot and
run Windows 8 from a USB drive. It provides a flexible way for workers to access their
personal desktop on any PC. The article “Windows To Go: Feature Overview” at
http://technet.microsoft.com/en-us/library/hh831833.aspx provides additional information
about Windows To Go as well as step-by-step instructions for preparing, securing, and
managing Windows To Go devices.
Virtual Desktop Infrastructure
Microsoft Virtual Desktop Infrastructure (VDI) is an alternative desktop delivery model that
gives users secure access to centrally managed desktops running in the datacenter. VDI is
powered by Remote Desktop Services (RDS), which is a server role in Windows Server 2012.
It provides a single platform to deliver any type of hosted desktop, and RemoteFX provides
a consistently rich user experience. RDS enables organizations to choose the deployment
method that works best for them—all by using a single platform.
- Session-based desktops Session-based desktops provide users access to
through a SharePoint portal, on a local desktop, or over the Internet.
- Pooled virtual machines (VMs) Pooled VMs give users access to high-performance
pool to users. When they log off a VM, VDI returns it to the pool for use by another
user.
- Personal VMs Personal VMs give users access to a personal, high-performance
With all three VDI deployment methods, user state virtualization maintains users’ data
and settings across physical and virtual sessions. VDI empowers enterprises with unified
management of centralized desktops and corporate data by using System Center 2012. IT can
extend existing management tools and processes to the VDI environment.
Partner technology, such as Citrix XenDesktop, adds value to VDI by offering additional
scale and flexibility to enterprises. With Citrix technologies, users can access their Windows
environment even from non-Windows devices.
Chapter 11, “Windows 8 virtualization,” provides more information about Windows 8 and
VDI. You can also learn more on the Desktop Virtualization website at http://www.microsoft
.com/dv .
Client Hyper-V
On PCs running Windows 8, Client Hyper-V provides a robust virtual platform for d evelopers
and IT pros. It supports a broad range of devices and leverages the driver ecosystem of
Windows 8 to run on the broadest range of 64-bit PCs. Client Hyper-V provides a rich user
experience, including multimedia, touch, and USB support. Because Client Hyper-V is a core
part of Windows 8, it leverages all of that operating system’s security and management
features.
Client Hyper-V requires the following:
■ A 64-bit system
■ 4 GB of RAM is required
■ Support for Second Level Address Translation (SLAT)
SLAT unloads from the processor the process of mapping physical memory to v irtual
memory. For intensive graphics, it provides significant performance improvements. It
is r equired for Hyper-V on Windows 8, because most systems have extensive graphics
capabilities. It’s only required for Windows 8 Server when enabling the RemoteFX role service.
For more information, see the article “Client Hyper-V” at http://technet.microsoft.com/en-us/
library/hh857623.aspx.
Tidak ada komentar:
Posting Komentar