Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005
-
@dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@scottalanmiller said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-config
Windows 10 cannot be used with Server 2012.
What do you mean? VDI or what?
VDI access is the same as non-VDI access. The limits of one have to reflect on the other as it is the connection over the network that doesn't work. Right?
I understand that but I have still RDS with Server 2008 R2, 2012 and one available and can connect via Windows 10 to Windows 10 Computers behind the RDS while they are non-VDI. Maybe @Osvaldo can clarify but he said Physical Desktops.
You have Windows 2012 (not R2) RDS acting as a front end proxy to Windows 10 that is working?
Yes and Server 2008 R2 as well.
So here it is RDS, but with RDW. Not sure if that is the source of the additional limitation.
-
@scottalanmiller Yeah, RDW is the problem I understand now. Basically you can remote desktop without need of App Resources Proxy without any problems. But if you try to load the App Resources from a Windows 10 device then yes I understand now.
-
@dbeato said in Windows Server 2012 Remote Web Access not connecting and RDS services showing error 23005:
@scottalanmiller Yeah, RDW is the problem I understand now. Basically you can remote desktop without need of App Resources Proxy without any problems. But if you try to load the App Resources from a Windows 10 device then yes I understand now.
Yeah. It's a weird "Essentials only" issue, only on 2012 and older. From what I can tell.
