search

Azure / RDS-Templates

ARM Templates for Remote Desktop Services deployments
MIT License
466 stars 599 forks source link

3-wvd-management-ux - 2 out of 4 Tenants do not display sessions hosts #415

Open brighammirabelli opened 4 years ago

brighammirabelli commented 4 years ago

WVD UX = Version 1.2.2

I have 4 Tenants in their own subscriptions but all part of to the same Azure AD .

I can see the Tenants and host pools for all in WVD Management Portal.

I can only see the Session hosts for 2 out of the 4 Tenants.

When checking by PowerShell I can see that those session hosts are healthy and available and part of the pool but the UX is not showing them under the host pool. I can even connect to sessions through them.

I have deleted and recreate session hosts for the pools that to not show them in the UX.. I have generated a new pool token and added to the session host registery and rebooted the session host. I have deployed a new WVD management UX from the ARM template

All steps and i still only see Session hosts for 2 out of the 4 tenants.

Logging in as Global Admin and i am using the default tenant group.

When I click on the user name in the upper right I do see" Infrastructure Permission /Default Tenant Group/"name of first tenant only"

And that seems odd to me.

Please let me know if more info in needed or anything to try.

brighammirabelli commented 4 years ago

I have deleted and recreated one of the tenants and pools that are not showing in the Management UX. Once added back in and hosts are deployed I do not see them in the MGMT UX.

I redeployed the Management UX 2 times and both have the same issue.

sywyndir commented 4 years ago

I have a similar issue. Just deployed a personal host pool with 9 VMs. The session hosts are all alive and available to the users, but the management UI does not show them in the host pool page. VMs and RDS tenant are in different subscriptions and belongs to the same Azure AD. The user connected to the ui is owner of both subscriptions. Vm reboot, remove and re-register did not solve the issue.