![]() ![]() – RD Connection Broker’s centralized publishing enables administrators to aggregate RemoteApp programs, session-based remote desktops and VM-based remote (virtual) desktops from various sources into a single customized view for users. A user can either be assigned a personal virtual desktop or a desktop from a virtual pool. The desktops are virtual machines hosted on a Windows Server 2008 R2 system with the Hyper-V role and Remote Desktop Virtualization (RD Virtualization) role service installed. – the new Virtual Desktop Infrastructure (VDI) of RDS in Windows Server 2008 R2 enables an administrator to provide access to virtual desktops through RemoteApp and Desktop Connection. Administrators can assign RemoteApps to users. These resources can be published via RD Web Access, or deployed directly to users via. – provide traditional session-based desktops and RemoteApps to users. Rather, various aspects of RemoteApp and Desktop Connection functionality are provided by specialized RDS role services and other components including: There is no single component that provides RemoteApp and Desktop Connection functionality. Additionally, administrators can deploy the RemoteApps and desktops directly to users using a variety of methods. Users can then access the RemoteApps and desktops from the RD Web Access portal, or subscribe to a web feed which will seamlessly integrate them into a Windows 7 Start menu and automatically update the list as published applications and desktops change. ![]() With RemoteApp and Desktop Connection, administrators can create an aggregated and customized view of RemoteApps and desktops and assign them to users. Those capabilities have been expanded in Windows Server 2008 R2 and Windows 7 into a new framework for deploying RemoteApps, session-based desktops, and virtual machine-based desktops to users called “RemoteApp and Desktop Connection. In addition, TS Web Access provided a single web page to access all RemoteApp applications and session-based desktops. ![]() RemoteApp was introduced to deploy RDS applications to users, and to seamlessly integrate those applications into the users’ desktops so they would appear as if they were running locally. Our subject: RemoteApp and Desktop Connection. It’s Day Fourteen which means that there’s just over a week to go! Today we’re continuing on with our look at various Remote Desktop Services components. Check out our guide to accessing Remote Desktop over the Internet for more information about that.First published on TECHNET on Oct 14, 2009 If you’re planning to connect to the remote PC over the Internet, you’ll have to do a little extra setup that involves allowing Remote Desktop traffic through your router and forwarding those types of packets to the right PC. RELATED: How to Access Windows Remote Desktop Over the Internet Just type in the name or IP address for the PC to initiate the connection. You can start a remote connection from those computers by clicking Start, typing “remote,” and then choosing the “Remote Desktop Connection” result. Windows automatically creates exceptions in the Windows Firewall to allow remote connection traffic to get through. If you’re planning to connect from other PCs on the same local network, that should be all you have to do. On any version of Windows, you can also click the “Select Users” button to set up specific users that are allowed to make remote connections. When you’re done setting things up, click the “OK” button to have your PC start listening for remote connections. Notice that you have three distinct options in Windows 7-don’t allow remote access, allow connections from any version of Remote Desktop, and allow only connections that run with Network Level Authentication. If you’re using Windows 7 or Vista, things work the same, but are presented in a slightly different way. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |