I have a particular interest in the reverse proxy side having done a lot of work with UAG lately which makes me miss TMG! As discussed in my previous blog Publish Lync 2013 Including Mobility and Office Web Apps with UAG 2010, with TMG disappearing the only Microsoft product (other than IIS with ARR) with reverse proxy functionality is Microsoft Forefront UAG (Unified Access Gateway).
LYNC WEB APP PLUG IN RDS 2012R2 REGISTRATION
The Web Application Proxy is a reverse proxy and ADFS (Active Directory Federation Services) Proxy that also provides functionality like Workplace Join for Windows 8.1 using the Device Registration Service (DRS). It provides the ability to publish access to corporate resources, and enforce multi-factor authentication as well as apply conditional access policies to verify both the user’s identity and the device they are using resources, and enforce multi-factor authentication as well as verify the device being used before access is granted. Web Application Proxy – The Web Application Proxy is a new role service in the Windows Server Remote Access role. The announcement from Microsoft TechEd North America early in June that got me really interested was the Windows 2012 R2 Web Application Proxy which was described as: Clarification about modifying published applications.Clarification about ADFS being a hard requirement for the Web Application Proxy, even if only doing pass-through.ActiveSync does not support SNI so a default binding needs to be set on the Web Application Proxy as per the post above to make it work.Lync 2013 and Office Web Apps 2013 have been tested and work with some configuration changes.They say it will be fixed in the RTM version I have heard from a member of the Web Application Proxy product group who said there is a bug in the Preview version that prevents Outlook Anywhere from working.Updated PowerShell deployment of Web Application Proxy blog after testing with RTM – see.Tested after Windows 2012 R2 RTM released to Technet and Outlook Anywhere works now.If you don't see them then you might need to click on the printer(?) icon on the blue RDS bar.Īdding to the weirdness, the webcam worked fine for the user but when we disconnected we lost the "Other supported RemoteFX USB Devices" setting on mstsc. I tested by restarting chrome and going to one of the "webcam test" sites. I enabled RemoteFX redirection and the webcam showed up instantly. Ultimately, I gave up on my computer and went to the user's workstation.
LYNC WEB APP PLUG IN RDS 2012R2 PC
I was testing on my PC (Wind圆4) with "Allow RDP redirection of other supported RemoteFX USB devices from this computer" enabled (and rebooted), but I could not get "Other supported RemoteFX USB Devices" to show up Also, for anyone considering enabling this, be aware that I saw a 30% increase in CPU usage just by turning the webcam on inside of the RDS. So, I had to go to a completely different machine to get this working. Server 2016 Remote Desktop Session Host.confirmed that the webcam does not show up under devices and printers, or device manager.Confirmed that the webcam shows up and works on the workstation.Computer Configuration\Administrative Templates\Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection/ Do not allow supported Plug and Play device redirection = set to disabled on the RDS server.Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client\RemoteFX USB Device Redirection\ Allow RDP redirection of other supported RemoteFX USB devices from this computer = set to enabled for everyone on the workstation.I have done the following items but I can't seem to get webcams working:
We've tried to talk them out of it and it appears that there's no way out. We have a user that insists on using a webcam on their RDS session.