{"id":558,"date":"2014-09-18T15:15:26","date_gmt":"2014-09-18T13:15:26","guid":{"rendered":"https:\/\/www.em-soft.si\/myblog\/elvis\/?p=558"},"modified":"2014-09-18T15:15:26","modified_gmt":"2014-09-18T13:15:26","slug":"rdp-2012r2-web-access-why-not","status":"publish","type":"post","link":"https:\/\/em-soft.si\/myblog\/elvis\/?p=558","title":{"rendered":"RDP 2012R2 Web access? Why not!"},"content":{"rendered":"

Publishing terminal services through the web is more and more popular and I am still convinced that we have to use them more. Maybe with publishing this article I will help someone to decide and publish them. In this article, it is nothing new or revolutionary; there are practically few tricks, that my customers like.<\/span>
\nThere are many changes, in working with remote applications, that are coming with Windows Server 2012. After some of us really appreciated publishing remote applications with a method of distributing RDP files or MSI installers in Windows Server 2008 and 2008R2, now it is not possible to do it anymore. Many changes are visible also in the installation of RDP rules. Now we have separate steps form installing \u201cjust rules and features\u201d \u2013 this is a good thing, because doing installation this way, there are not so many errors in RDP deployment and it is the only right way for installing web access and other RDP rules (don\u2019t do it through rules and features!!!).<\/span>
\nIn addition, this WEB access is the functionality where I want to show some tricks. <\/span>
\nAs we know, the address https:\/\/rdp_server.publicname.com\/rdweb<\/strong><\/em> is the address, where we can access to our applications. Here you can see a desired application instantly after it was installed and published.<\/span>
\n\"RDP<\/a>
\nMany times we have unhappy users, because for running those application they have \u00bba lot of work\u00ab – they have to type this web address and login\u2026 Other not nice functionality of this web interface is that some browsers are unable to run RDP file directly from the web and they have to download it and run it.<\/span>
\nHere we can do something for our users. In Windows 7 and newer, in the control panel it is present a setting called Remote App and Desktop Connections. This is exactly what we want to do. Just type in the apposite text box the published web address and add in the end feed\/webfeed.aspx (example: https:\/\/rdp_server.publicname.com\/rdweb\/feed\/webfeed.aspx<\/strong><\/em>). This setting will put all published applications to which user has access to his Start menu under Work Resources (RADC). Need more? They are also dynamic; if you revoke permissions or deinstall application, the application will disappear from there. In addition, if you add a new one, it will simply appear there. Nice.<\/span>
\nIt is still too complex for your users? OK. Then we can try making this easier for them. There is an option to write the E-Mail address<\/strong>. In this case, E-Mail is used only for getting the domain name. All other work is done by DNS setting and all other process is equal as you write down a published address. Of course, the domain used in the E-Mail address must have a TXT record with this few parameters:<\/span><\/p>\n