Server 2012 R2 Standard RDP RemoteApp in WORKGROUP

From what I've read on various tech sites (EE included), and have experienced so far on my test 2012 R2 standard server, I can't configure RDP feature "RemoteApp" unless my server has been joined to a domain. Has anybody successfully configured/deployed a RemoteApp while their server was only a standalone workgroup server?

I currently use all 2008R2 servers and for business reasons many are standalone in workgroup mode...and can't be in a domain.

I have been able to configure all RDP / terminal server features I need in workgroup mode, except for RemoteApp.  Most config is workable via local group policy. But RemoteApp looks like it requires the server being a domain member. I tried to use Powershell to force remoteapp configuration but that failed. Group Policy isn't helpful here either. So I'm pretty certain RemoteApp requires domain membership...but I'm new to 2012 server so I want other opinions.

I'm looking to see if anybody has been able to accomplish this.
LVL 15
ZabagaRAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
Many features like remote app require that the computer be a member of a domain. It has largely to do with authentication.  mycomputer\username can't be authenticated by server as these are local accounts but domain\username can be authenticated and appropriate security is applied.
0
 
ZabagaRAuthor Commented:
I was hoping to get some more input - thoughts - suggestions - from a few others but I do trust that RemoteApp requires a domain. I'll accept and move on,
0
All Courses

From novice to tech pro — start learning today.