It is also possible, however, to install RDS on a server running in the cloud and share desktops from the cloud.
Typically, the machine that hosts RDS runs in the same physical location - such as the same office building - as the computers from which users access the remote desktop environments. RDS can also be configured to make only certain applications available to remote users, if admins choose to set it up that way.
Once you log into the RDS-hosted PC environment, you can usually access all of the same local resources - including storage, applications, the Windows desktop interface and so on - that you would be able to use if the RDS environment were an actual PC that was sitting in front of you.
By setting up RDS on a Windows server, then using a Remote Desktop Protocol (RDP) application like Microsoft Remote Desktop, you can log in from another computer to a Windows environment that is hosted via RDS. In Windows, Remote Desktop Services, is a platform that lets users share desktop environments between one Windows computer and another over the Internet. Here’s a breakdown of the similarities and differences between RDS and DaaS, and why to choose one or the other. The differences matter not just for IT teams who maintain one of these platforms, but also for the end-users who rely on them to access desktop environments remotely. However, RDS and DaaS are fundamentally different types of solutions. Two of the most popular approaches, Remote Desktop Services (RDS) and Desktop-as-a-Service (DaaS), deliver approximately the same end-result. In today’s network-centric world, there is no shortage of solutions available for making PC environments available over the Internet.
0 kommentar(er)
