![]() ![]() "Typically you can get three or four applications on an RDS server before they start to conflict," says Gavriella Schuster, general manager of Windows Product Management. That's why some use cases may be better suited for VDI.Īlso, because Windows applications installed into a virtual desktop are really running Windows Server 2008, not a native desktop version of Windows, application issues can come up - particularly as the number of applications installed into the virtual desktop session increases. If one user's session must reboot and restart the kernel, everyone else's session must be rebooted as well. That means each gets its own kernel space and user space from RDS, but at the kernel level core components of the host operating system are still shared. The benefit of the hosted shared services model is that it scales well, maximizing the use of resources on each Windows Server and eliminating the need to store many virtual desktop images for every user or groups of users.Įach published application or desktop runs in its own isolated session. Think of it as a simulation of a Windows desktop within an RDS session on Windows Server.Įvery hosted shared virtual desktop resides within a separate RDS terminal session but shares the same underlying operating system: Windows Server. ![]() VDI delivers a full native Windows XP or 7 desktop operating system to every user, while XenApp presents a "Windows desktop" that is really Windows Server 2008. The published virtual desktop executes on a Windows Server in the back-end Citrix server farm, and as with the VDI model, exchanges only mouse, keystroke and video data with the client using the Citrix Receiver client and its bandwidth-optimizing, proprietary Independent Computing Archtecture (ICA) protocol.Īlthough the connection method is the same, the XenApp approach is very different from Citrix's hosted virtual desktop infrastructure model (VDI), in which XenDesktop creates a dedicated Windows 7 or XP virtual machine for each user and hosts it in the data center. With XenApp/XenDesktop it has extended the approach to deliver an entire virtual desktop. Traditionally Citrix has "published" virtual applications in this way using Presentation Server (previously Metaframe), with users launching applications from a browser-based menu or desktop icon. ![]() In the XenApp hosted shared virtual desktop approach, formerly known as server-based computing, RDS turns Windows Server into a multi-user operating system, with Windows desktop applications running on top of it within the confines of individual terminal sessions. Practically speaking, however, the end result looks similar, and it might be a good fit for some applications. ![]() Technically, says Steve Kaplan, vice president of the data center virtualization practice at infrastructure services provider INX, this approach is not virtual desktop technology, since users are really running a shared Windows Server operating system, not a native Windows XP or 7 desktop operating system hosted within a virtual machine. Rather, it is an extension of what Citrix has been doing all along with XenApp (formerly Presentation Server), which runs on top of Microsoft's Windows Server as a Remote Desktop Services (formerly Terminal Services) session. Here's what you need to know about the technology, why you might consider it, and what the tradeoffs are.Ĭitrix's hosted shared desktop technology delivers a hosted virtual desktop to end users, but the technology isn't based on virtual machine technology at all. The technology has some potential upsides as an alternative to hosting virtual desktops using VDI, but didn't get into the details. Last week's tips for successfully hosting virtual desktops story mentioned an interesting alternative to VDI: Citrix's hosted shared virtual desktop technology, based on XenApp. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |