User Profile
michawets
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Windows Virtual Desktop Spring 2020 edition workshop
Introduction Last week (15-06 until 19-06), I was hosting a Technical Deep Dive on the Windows Virtual Desktop Spring 2020 edition together with Bart Roels from Microsoft Belgium for all West-Europe partners from Microsoft. We started with a Presentation on Monday about the changes in the Spring 2020 edition. And from Tuesday till Friday, we hosted Hands-on Labs. During these Hands-on Labs, the attendees had to create a custom image deploy a WVD Workspace and Hostpool using the portal and ARM Templates config a WVD Deployment in the portal and using Powershell configure FSLogix on a fileserver create an Azure FileShare to store the FSLogix profiles configure MFA & RBAC work with IGEL OS on HyperV or VirtualBox The idea Bart and I made the decision to make the entire Workshop available online, to everybody and to make it open-source! This way, you can do it yourself, at your own pace, at the office with your co-workers. But more importantly, you can also contribute! You can make changes, add topics or idea's so I (or the community) can make those manuals. The workshop You can find the entire workshop, with slides, video, links, tasks, everything, right over here: https://aka.ms/WVDWorkshop As you can see, Bart made an aka.ms shortlink, to make it even more easy for you to find it. The source code The page is a generated GitHub Page, and you can find the sourcecode here: https://github.com/michawets/CA-Microsoft-WVD_ARM-Workshop If you have great idea's, things you want to add, change, anything, let me know. Create a fork, do your changes and create a Pull Request. This way, you help to make this workshop better for all. Comments We hope this helps! Please leave a comment below if you have questions or remarks. [source] https://www.cloud-architect.be/2020/06/22/windows-virtual-desktop-spring-2020-edition-workshop/2.6KViews4likes2CommentsRe: Is the Set-RDSTenant <TenantName> -FriendlyName <NewFriendlyName> working yet?
Hi Alex Levin , What is the outcome of the Get-RdsDiagnosticActivicities cmdlet? Especially the Errors property is important, so you should add -Detailed to the cmdlet & expand the Errors property1.3KViews0likes1CommentRe: sage install not working
Hi EricFehn , Have you checked the installation with a ProcMon yet? You could search for setup.lst, see where it fails and perhaps fix the installation. Have you checked with Sage already if they know issues with Win10 & Office365 ProPlus installations? Especially the Office version could be the blocker. For the Temp file, by default, the Temp folder is not created. If you create the Temp folder manually and ProcMon the installation, can you see which folder is missing/failing? Here's the link to my favorite tool https://docs.microsoft.com/en-us/sysinternals/downloads/procmon1.8KViews0likes0CommentsRe: remote app host pool configuration
Hi EricFehn , You are hitting a hard limit of WVD at this time: a user can only be assigned to 1 AppGroup in 1 HostPool at the same time. If you would like to publish RemoteApps & a RemoteDesktop to a user at the same time, you will need to have 2 HostPools with seperate SessionHosts. Just a small tip: check your profiling method (Roaming Profile, FSLogix), especially when publishing multiple HostPools to the same user1.7KViews0likes0CommentsRe: Connecting to Windows Remote Desktop through Azure
Hi babylon1475 , You could check what is going wrong using the Get-RdsDiagnosticActivities cmdlet: https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-role-service Filter out the Connection attempt, get the Detailed logging (using the -Detailed parameter) and expand the Errors property3.9KViews0likes0CommentsRe: Deployment Error: Exception(s) occured while joining Domain
Hi AjantiDaggar , You are correct, you need a Windows Server Active Directory in sync with Azure Active Directory. This can be enabled through: An Azure VM in your VNET, with the Windows AD role & Azure AD Connect Azure AD Domain Services So it is important, during the deployment, that you select a VNET that has either one of these options enabled in it so the SessionHosts (WVD hosts) can join that domain. Hope this helps14KViews0likes0CommentsRe: AD Sync not strictly required?
Hi AlexPawlak , As I already thought and stated, the UPN & password hashes do match in Windows AD & Azure AD, making it possible for the user to sign in. But as soon as Windows AD or Azure AD changes, it would fall apart. Therefor, AD Connect syncs the useraccounts from Windows AD to Azure AD, keeping passwords in sync (with Writeback capabilities). Azure AD DS goes a step further, it starts from Azure AD, and makes a Windows AD available in your VNET, also keeping it in sync. Regarding the licensing: it could be possible to connect without proper license, but this is not guaranteed. I would recommend to assign an eligible license to the user(s) which are listed here at the FAQ. https://azure.microsoft.com/en-gb/pricing/details/virtual-desktop/1.6KViews1like1CommentRe: AD Sync not strictly required?
Hi AlexPawlak , The AD Connect will sync the user accounts from your Windows AD to Azure AD, so that the user can authenticate when starting the WVD client (web or installed client) Those clients will authenticate against Azure AD first, requiring the users to live in Azure AD in the same way the live in Windows AD (same password, upn, etc) Regarding the working deployment: is the user you test with created in both Azure AD & Windows AD with the same credentials & UPN? If you create a new user in Azure AD, the user will be able to authenticate in the clients, but will not be able to start an application. If you create a new user in Windows AD, this user will not be able to authenticate in the clients, and never start an application through WVD. Hope this makes things clear for you1.6KViews1like3CommentsRe: Windows Virtual Desktop - is AD Domain Controller needed and where does it reside?
Hi SeizeThaNight , I think you are mixing the things up a bit here . If you have an onprem Windows AD, then you should install Azure AD Connect on the DC. In Azure, you could create a VPN in your VNET, updating the VNET DNS settings to point to the onprem DC, and then join the WVD Sessionhosts to the onprem Domain using a AD account from that AD Forest. If you don't want to use a VPN, you could use the following setup: On the onprem Windows AD, install Azure AD Connect on the DC to sync to Azure AD. In Azure, add Azure AD DS, which will update the VNET for you, and then you can use that AD account from the local domain to join the WVD sessionhosts. Hope this makes things more clear9.2KViews1like0CommentsRe: "Remote Desktop licensing mode is not configured"
Hi Nicholas Semenkovich , Which OS Version of Windows 10 are you using? The 1903 version should give you plenty of time. Microsoft has acknowledged this message, and a fix/update will be available before the "Grace period" is passed.6.9KViews0likes4CommentsRe: WVD - Windows Server 2019?
Hi AlexPawlak , Windows Server 2019 is support as Sessionhost for WVD, no problem there. It is just not yet in the Marketplace list of OS images for the moment. But I thought it will be added later If you want to start using it, you could use the ARM template that is available on GitHub and modify the option list.2.2KViews0likes0CommentsRe: Created a WVD Pool using custom VM, but can't login to it when accessing the pool
Hi ramitadros, Can you check if the Windows Virtual Desktop Agent and Windows Virtual Desktop Agent Boot Loader are correctly installed? https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-vm-configuration#windows-virtual-desktop-agent-and-windows-virtual-desktop-boot-loader-are-not-installed If not, follow these steps to install or reinstall both agents on your VM: https://docs.microsoft.com/en-gb/azure/virtual-desktop/create-host-pools-powershell#register-the-virtual-machines-to-the-windows-virtual-desktop-preview-host-pool After that, your sessionhost should end up as available in the Get-RdsSessionHost cmdlet. Hope this helps Kind regards4.3KViews0likes4CommentsRe: Created a WVD Pool using custom VM, but can't login to it when accessing the pool
Hi ramitadros , You could check what is going wrong using the Get-RdsDiagnosticActivities cmdlet: https://docs.microsoft.com/en-us/azure/virtual-desktop/diagnostics-role-service Filter out the Connection attempt, get the Detailed logging (using the -Detailed parameter) and expand the Errors property4.3KViews0likes6CommentsRe: p2v Win7 desktop to Windows Virtual Desktop
Hi Daniel Corkill , This could be possible (in theory)! These would be the steps: Create a VHD from your Win7 VM (perhaps with Disk2vhd https://docs.microsoft.com/en-us/sysinternals/downloads/disk2vhd) Run through these steps: Prepare a Windows VHD or VHDX to upload to Azure (https://docs.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image) Use that image to deploy a new VM in Azure behind the WVD service If you have the Win7 running in Hyper-V, you can also use Azure Migrate to migrate the VM to Azure, without making the Win7 into an Azure Image first: https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-hyper-v This is all theory of-course. You will have to do some testing 😊2.2KViews0likes0CommentsRe: Windows Virtual Desktop - is AD Domain Controller needed and where does it reside?
Hi SeizeThaNight , You are correct, the deployment will not create a VM with Active Directory, this is a prerequisite before you start deploying (https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements) As for the AD, you need a Windows Server Active Directory in sync with Azure Active Directory. This can be enabled through: An Azure VM in your VNET, with the Windows AD role & Azure AD Connect Azure AD Domain Services So it is important, during the deployment, that you select a VNET that has either one of these options enabled in it so the SessionHosts (WVD hosts) can join that domain. Hope this helps9.3KViews0likes3CommentsRe: Internal error occurred when connecting to RD
Hi Hermanbonnie , Yes, I'm afraid your Sessionhost(s) needs to be in a Windows AD, which syncs with Azure AD This can be a Azure VM with Windows AD role installed, and Azure AD Connect Azure AD DS It is mentioned in the Requirements from WVD: https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements Your infrastructure needs the following things to support Windows Virtual Desktop: An https://docs.microsoft.com/azure/active-directory/ A Windows Server Active Directory in sync with Azure Active Directory. This can be enabled through: Azure AD Connect Azure AD Domain Services An Azure subscription, containing a virtual network that either contains or is connected to the Windows Server Active Directory The Azure virtual machines you create for Windows Virtual Desktop must be: https://docs.microsoft.com/azure/active-directory-domain-services/active-directory-ds-comparison or https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan. Virtual machines can't be Azure AD-joined. Running one of the following https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#supported-virtual-machine-os-images.6.2KViews0likes0CommentsRe: Internal error occurred when connecting to RD
Hi Hermanbonnie , Just a small question: is the user available in both Windows AD & Azure AD? Is it in both cases the same UPN? And perhaps this could be the issue: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-client-connection#error-o_add_user_to_group_failed--failed-to-add-user--username-to-group--remote-desktop-users-reason-win32error_no_such_member6.3KViews0likes2Comments
Recent Blog Articles
No content to show