tag:blogger.com,1999:blog-6461067935478170803.post8747598305048396097..comments2024-03-05T10:37:06.810-06:00Comments on | Exit | the | Fast | Lane |: Native RDS in Server2016 - Part 2 - RDVHPeterhttp://www.blogger.com/profile/07331743507096012047noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-6461067935478170803.post-11774240824053236522019-01-26T14:40:47.087-06:002019-01-26T14:40:47.087-06:00Hi Jamie, sorry I had comments stuck in the queue ...Hi Jamie, sorry I had comments stuck in the queue I didn't know about. Updating and re-syspreping is one way you could go or you could offload apps externally and present them to the VMs directly. XenApp/RDSH, thinapp etc. This allows you to separate application management from gold image management. Peterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-47206329061437498372018-06-20T14:37:23.388-05:002018-06-20T14:37:23.388-05:00Peter,
Thank you for this series you created. My ...Peter,<br /><br />Thank you for this series you created. My question is if you went this route, how you would update the applications installed on the VM? Boot it up, update and then sysprep again?<br /><br />Thanks,<br />JamieAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-34233851560205369602018-03-12T15:29:36.209-05:002018-03-12T15:29:36.209-05:00Looks like the answer is no: https://docs.microsof...Looks like the answer is no: https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-supported-configPeterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-10473267524831459162018-03-12T04:12:43.066-05:002018-03-12T04:12:43.066-05:00Does RDS 2016 Support both RDVH 2012 R2 and 2016? ...Does RDS 2016 Support both RDVH 2012 R2 and 2016? Not just during the upgrade of RDVH but more like heterogeneous RDVH hosts together.$$$https://www.blogger.com/profile/00940312842712704241noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-62047142274053694372018-01-30T11:08:16.766-06:002018-01-30T11:08:16.766-06:00Hey Anon, I see your problem. So the C:\Clustersto...Hey Anon, I see your problem. So the C:\Clusterstorage\ namespace doesn't exist on your RDCB VM. I cheated a bit with my example here by installing the RDCB role on one of my RDVH nodes directly. What you will need to do is: From one of your cluster hosts, create a share on the root of your collection folder that RDCB can access via UNC and input this path into your collection settings for template export. At that point the cluster will manage the VM data that comes in via the new share. Let me know how it turns out. Peterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-14100139882953869532018-01-25T18:06:25.788-06:002018-01-25T18:06:25.788-06:00Hi again Peter. I am close but it seems that I'...Hi again Peter. I am close but it seems that I've encountered a bug with the virtual desktop template export location when specifying CSV storage for the virtual desktops and parent locations. By default the template export location is the RDVirtualDesktopTemplate share on the connection broker. However, when creating a collection, no files are placed in this folder. Instead I am seeing c:\clusterstorage\volume2\vdparents\collection1\IMGS\.. folder structure being create on the connection broker server! This is what i defined as the virtual desktop parent location which resides on the RDVH servers. The folders are created but no actual vhdx or files are created within the folders. The result is that the collection creation progress gets stuck at "The virtual desktops are being created" and never completes. Strangely the virtual desktops do actually get created on the cluster and joined to AD and appear fully functional. However, since RDS doesn't ever actually finish creating the collection they are not usable. This happens for both pooled and personal desktop collections. I am wondering if you've encountered this and where I could have possibly gone wrong.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-18764877644285034542018-01-25T11:30:00.458-06:002018-01-25T11:30:00.458-06:00RDS is cluster-aware so when the RDCB goes to prov...RDS is cluster-aware so when the RDCB goes to provision new VMs, it will work directly with the cluster services on the targeted RDVH hosts. The one significant change you will make at the time of deployment is defining the target cluster shared volume in the collection settings. I show how this works towards the end of this post: http://www.exitthefastlane.com/2017/04/the-native-msft-stack-s2d-rds-part-2.html Peterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-71739706845422500012018-01-25T10:56:59.695-06:002018-01-25T10:56:59.695-06:00The installation succeeds if I specify each cluste...The installation succeeds if I specify each cluster member as individual RDVH's. My question now is how does RDS know to deploy the virtual desktop VM's as clustered resources vs just a standard VM on each host? Is it smart enough to recognize the RDVH's are in a cluster? Or do I need to take specific steps to during my collection creation process? Or, will it deploy the desktops on each host and then I must manually make them highly available from failover cluster manager? If you could shed any light on this I'd really appreciate it!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-25022271909352040922018-01-24T22:14:21.571-06:002018-01-24T22:14:21.571-06:00Hey Anon, so this could be something related to th...Hey Anon, so this could be something related to the computer account in AD for the cluster object or DNS possibly. Try targeting a server node directly by name, not via the cluster name. Peterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-79885665402713811372018-01-24T21:18:29.526-06:002018-01-24T21:18:29.526-06:00Hi Peter, thanks for clarifying that. I am droppin...Hi Peter, thanks for clarifying that. I am dropping by once more as I attempt to deploy the RDVH role onto a Server 2016 hyper-v failover cluster consisting of 3 nodes. I initiate the RDS role installation from my connection broker VM (located outside the cluster) and followed your steps exactly (by selecting the failover cluster name for the RDVH server). The installation basically stalls on the RDVH restart step and then eventually fails with an error "Failed: The given key was not present in the dictionary". Have you seen this? I can't find anything about this error and how to successfully RDVH onto an existing failover cluster. Any help would be great!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-50955862324176047562017-11-17T12:21:06.883-06:002017-11-17T12:21:06.883-06:00Hi, thanks for dropping by. Yes you can absolutely...Hi, thanks for dropping by. Yes you can absolutely run all RDS infrastructure VMs within the same failover cluster! That is the architecture I used here for this deployment. Typically I recommend dedicating these mgmt VMs to a single node just so you can capacity manage your compute nodes easier but you could also spread these VMs across all nodes in the cluster if you wanted to. One thing to keep in mind is the placement of the Gateway role if you'll be allowing outside access. For now, still probably best to isolate that guy in the DMZ, one day soon this will no longer be an issue. Peterhttps://www.blogger.com/profile/07331743507096012047noreply@blogger.comtag:blogger.com,1999:blog-6461067935478170803.post-46954321672020896552017-11-17T11:52:31.542-06:002017-11-17T11:52:31.542-06:00When using a Hyper-V failover cluster for RDVH is ...When using a Hyper-V failover cluster for RDVH is it supported to also run the RD CB, Web and Gateway roles as guest VM's on the same cluster? Would these interfere with a managed/unmanaged/pooled/persistent VDI collection living on the same cluster? Essentially I am looking to avoid having seperate hyper-v clusters for RDVH and the other RDS roles and misc server VM's I want to deploy.Anonymousnoreply@blogger.com