03-29-2019 05:29 AM
03-29-2019 05:29 AM
I've succesfully deployed a Windows Virtual Desktop tenant and host pool. However, I'm trying to publish a remote app, which is not showing in the webfeed of the assigned user.
Add-RdsAppGroupUser TENANTNAME POOLNAME RemoteApps-Test -UserPrincipalName firstname.lastname@example.org
Add-RdsAppGroupUser : The specified UserPrincipalName(s) is already assigned to a Desktop AppGroup in the specified HostPool.
Powershell commands to diagnose the failure:
Get-RdsDiagnosticActivities -ActivityId b013d027-07f6-4ffa-a848-6ff7e1e2508a
At line:1 char:1
+ Add-RdsAppGroupUser TENANTNAME POOLNAME RemoteApps-T ...
+ CategoryInfo : FromStdErr: (Microsoft.RDInf...RdsAppGroupUser:AddRdsAppGroupUser) [Add-RdsAppGroupUser], RdsPowerShellException
+ FullyQualifiedErrorId : UpnAlreadyHasDesktopRights,Microsoft.RDInfra.RDPowershell.AppGroupUser.AddRdsAppGroupUser
03-29-2019 12:39 PM
@markkrolwsb : Windows Virtual Desktop has the restriction that within a host pool, a user cannot be assigned to both a desktop app group and a RemoteApp app group. This means that you'll have to first remove the user assignment (Remove-RdsAppGroupUser) to the desktop app group before you can re-assign that user (Add-RdsAppGroupUser) to the RemoteApp app group.
10-07-2019 11:34 PMSolution
I tried creating another host pool in the same tenant and then created a new RemoteApp App Group. Assigned to the same user and it works. So that means we can assign a user with RemoteApp and Desktop App group but it should be from different host pool and not from same pool.@markkrolwsb
10-21-2019 11:41 AM
@Rg035 : The reason we don't have this behavior supported by default is because of the trickiness of having 2 sessions on the VM, since the desktop session is different than a RemoteApp session. We've heard similar feedback from other customer engagements.
Here is our UserVoice channel to create/upvote this feature: https://aka.ms/wvdfbk .