REMOTE DESKTOP CONNECTION ADALAH WINDOWS

There is a common subset of connection broker features that all vendors offer: In today's world, the platform that can offer that experience (and the capabilities to manage it all) wins. I don't care where my desktop comes from or how it gets here, as long as it looks the same and behaves as if it were coming from the device sitting right in front of me. The desktop, at least as it pertains to desktop virtualization, is an abstract concept. No longer is the desktop a device sitting under your desk. So, what makes for a good platform? It depends. The choice of a connection broker has been folded into the selection of the overall desktop virtualization platform.

Now, however, people aren't so focused on the broker. The early adopters were quick to buy the first connection brokers that were available. In just a few years, we've gone from a world with zero desktop connection brokers to at least 10! Sun/Oracle, Leostream, Virtual Bridges, Symantec (by way of the nSuite acquisition) and Ericom all have their own connection brokers, as well.

REMOTE DESKTOP CONNECTION ADALAH WINDOWS

To reflect this change in the name of the feature, Microsoft renamed all Terminal Services roles and services to Remote Desktop in Windows Server 2008. Microsoft also updated its Terminal Services Session Broker to accept desktop connections. By the end of 2008, the company renamed the product VMware View.

The vendor had to pretty much remake the product after buying it, so it didn't introduce VMware VDM (Virtual Desktop Manager) until early 2008. Having a head start on the virtualization side, VMware opted to purchase a connection broker from U.K.-based Propero. In 2007, the company released this as Citrix Desktop Server, the product that would eventually become XenDesktop after the acquisition of XenSource. That product grew into what is now Quest vWorkspace, one of the top products in the market.Д¬itrix had already been working on a project called PortICA, which 'ported' the ICA client to desktop operating systems. The concept of a desktop-oriented connection broker was so similar to that of a TS-based connection broker, though, that it wasn't long before they started appearing.Д«y 2006, Provision Networks (now Quest Software) began talking about how its Provision Management Framework brokered connections to any kind of device - TS, virtual desktop, physical desktop or blade PC. This connection broker was unaware of desktops, as was any other TS-based product on the market. Microsoft had just released a connection broker as part of Terminal Services (TS) in Windows Server 2003. All that was needed to pull it together was something called a 'connection broker.' VDI was also expected to solve a wide array of other problems associated with server-based computing and traditional desktops. We had virtualization, remote display protocols, Terminal Server-based solutions and powerful enough hardware to begin thinking that we could get away with virtualizing desktops in the data center.ДЄt the time, the benefits were promising: Desktops in the data center could reduce power, allow you to use more applications than you could with Terminal Services, eliminate the need for individual silos and increase desktop security. Five or six years ago (an eternity in this business), the concept of virtual desktop infrastructure began taking shape.

Remote desktop connection adalah