Forum Discussion
'joindomain' error with Windows Virtual Desktop
I have a single vnet with a subnet that has gateway and a subnet that has a Domain Controller successfully joined to our on-prem domain via VPN tunnel. I went through all the steps I've found onlin...
Hi John,
Is the VM in the same vnet as the DC?
What is the DNS server in the subnet where the WVD VM is created? The domain needs to be resolvable.
Another option is that the account used for joining the WVD VM to the domain is incorrect.
Looking forward to your feedback!
BR,
Dirk
Thanks again. Do you mind if you could point me in the direction for figuring out the following 3
things??
1. When I login to https://rdweb.wvd.microsoft.com/webclient/index.html, the icons are called "Session Desktop". Is there a way to rename those?
2. How would I upgrade software/applications on these servers for users who will be using them? Do I just mstsc /admin into each of them and pull them out of the pool, then upgrade? or does each user get individual apps installed?
3. I use Okta SAML/SSO. While I get the prompt when logging into rdweb website, after authentication I still get a user/password login screen so it's not passing through so I have to authenticate a second time.
things??
1. When I login to https://rdweb.wvd.microsoft.com/webclient/index.html, the icons are called "Session Desktop". Is there a way to rename those?
2. How would I upgrade software/applications on these servers for users who will be using them? Do I just mstsc /admin into each of them and pull them out of the pool, then upgrade? or does each user get individual apps installed?
3. I use Okta SAML/SSO. While I get the prompt when logging into rdweb website, after authentication I still get a user/password login screen so it's not passing through so I have to authenticate a second time.
1.Check out this page:
https://docs.microsoft.com/en-us/powershell/module/windowsvirtualdesktop/set-rdsremotedesktop
2. Your VM's should be a 1-on-1 representation of your golden image, you should be able to update the golden image, destroy your WVD VM's and redeploy. The FSLogix profiles should hold the user data, not the WVD VM. If you don't want to do this, WVD VM's are also manageable by SCCM and other management tools.
3. This is normal, when using the remote desktop app, it will cache your credentials so you don't have to authenticate twice (altough I'm not sure with Okta, haven't tested that myself).
https://docs.microsoft.com/en-us/powershell/module/windowsvirtualdesktop/set-rdsremotedesktop
2. Your VM's should be a 1-on-1 representation of your golden image, you should be able to update the golden image, destroy your WVD VM's and redeploy. The FSLogix profiles should hold the user data, not the WVD VM. If you don't want to do this, WVD VM's are also manageable by SCCM and other management tools.
3. This is normal, when using the remote desktop app, it will cache your credentials so you don't have to authenticate twice (altough I'm not sure with Okta, haven't tested that myself).
- knowlite thanks that helps. And as far as performance is there some minor lag to be expected? Just wondering where I should start with optimizing the “snapiness” of the WVD. Suppose I could create other VMs to compare with WVD.
- Important are the local disk type (ssd) and the FSLogix profile storage.
The actual cpu/memory load is different for each company.
Depending on how many users you would want to squeeze on 1 VM, the VM type will differ.
