04-24-2019 09:57 AM
04-24-2019 09:57 AM
After adding a domain joined Azure VM to my host pool by installing the RD Agent I'm seeing it give errors on upgrading:
SessionHostName : ACE-WIN10-MS-0.windstream.com
05-15-2019 04:28 PM
Sadly wasn't able to get it working, but haven't seen this particular error again. Completely removed the RDS App Group and Host Pool. Started from the ground up, but second go around the VM never even appeared as a Session Host at all. Left a comment over on https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell stating that the installers listed aren't the same version as what is pushed in the DSC from the ARM template, but doesn't look like they've been updated.
Have a case with my company's Microsoft TAM on the DSC in the New Host Pool Resource failing to download, but looks like I may just have to wait for that to get resolved because I can not get the manual steps to work.
05-15-2019 09:06 PM
@ScriptingJAK : Hmm...if all of the steps go through, then the only reason the VMs wouldn't show up is if there's name collisions, in which case the service doesn't automatically overwrite the session hosts that are already in the database.
To address your first comment, the DSC is now updated to match the published version from the docs, but I understand how the mismatch would be confusing. Hopefully you're able to resolve the issues in your environment and continue testing.
05-16-2019 05:16 AM
Have they been updated? Ran the New Host Pool resource yesterday and the RD Agent it tried pulling down to install from https://catalogartifact.azureedge.net/publicartifacts/rds.wvd-provision-host-pool-a6ce9b11-d690-4507... is labeled "Microsoft.RDInfra.RDAgent.Instaler-x64-184.108.40.206" while if I click the download link from the manual instructions page I linked earlier it takes me to https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWrmXv and pulls down "Microsoft.RDInfra.RDAgent.Installer-x64-220.127.116.112"