RDInfra.RDAgent - template preparation

%3CLINGO-SUB%20id%3D%22lingo-sub-1211317%22%20slang%3D%22en-US%22%3ERDInfra.RDAgent%20-%20template%20preparation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1211317%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20are%20trying%20to%20build%20a%20POC%20WVD%20installation.%20Upon%20creating%20a%20master%20image%20on%20an%20Azure%20VM%20and%20installing%20the%20agent%20(with%20the%20host%20pool%20token%20baked%20in)%2C%20bootloader%20and%20stackSxS%20installer%20I%20have%20seen%20a%20strange%20issue%20with%20the%20two%20hosts%20in%20my%20host%20pool.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt%20seems%20to%20only%20register%20one%20host%20if%20I%20run%20a%26nbsp%3B%26nbsp%3B%20Get-RdsSessionHost.%20If%20I%20restart%20the%20agent%20on%20either%20machine%2C%20that%20machine%20then%20becomes%20visible%20with%20the%20same%20cmdlet.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20i%20uninstall%20the%20agent%20from%20a%20machine%2C%20and%20re-install%20it%20with%20the%20same%20token%20%2C%20the%20command%20then%20shows%20both%20hosts.%20I%20am%20assuming%20that%20it's%20because%20I%20installed%20it%20into%20the%20image.%20Is%20there%20any%20advice%20for%20doing%20this%20so%20that%20once%20built%20all%20machines%20from%20a%20master%20image%20all%20affiliate%20to%20the%20pool%20correctly%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20if%20anyone%20can%20help!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1217915%22%20slang%3D%22en-US%22%3ERe%3A%20RDInfra.RDAgent%20-%20template%20preparation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1217915%22%20slang%3D%22en-US%22%3E%3CP%3EFrom%20all%20investigation%20I've%20done%20on%20this%20in%20the%20last%20week%2C%20it%20doesn't%20seem%20recommended%20to%20install%20the%20RDInfra%20Agent%20on%20a%20master%20image%20before%20deploying%20to%20any%20given%20host%20pool.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20documentation%20I've%20found%20seems%20to%20suggest%20installing%20the%20agent%20after%20machine%20creation%20and%20giving%20it%20then%20pool%20token.%26nbsp%3B%20This%20is%20a%20real%20pain%20and%20I%20can't%20see%20an%20easy%20way%20of%20installing%20this%20across%20multiple%20RDS%20environments%2Fhosts.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThat's%20pretty%20poor%2C%20I'll%20add%20this%20to%20my%20%22reasons%20this%20isn't%20an%20enterprise%20ready%20product%22%2C%20after%20%22can't%20entitle%20groups%20of%20users%22%20as%20the%20first%20reason.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1395642%22%20slang%3D%22en-US%22%3ERe%3A%20RDInfra.RDAgent%20-%20template%20preparation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1395642%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20a%20workaround%2C%20you%20can%20use%20the%20ORCA%20application%20to%20edit%20the%20.msi%20file%20and%20add%20the%20generated%20token%20value%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,


We are trying to build a POC WVD installation. Upon creating a master image on an Azure VM and installing the agent (with the host pool token baked in), bootloader and stackSxS installer I have seen a strange issue with the two hosts in my host pool.


It seems to only register one host if I run a   Get-RdsSessionHost. If I restart the agent on either machine, that machine then becomes visible with the same cmdlet. 

If i uninstall the agent from a machine, and re-install it with the same token , the command then shows both hosts. I am assuming that it's because I installed it into the image. Is there any advice for doing this so that once built all machines from a master image all affiliate to the pool correctly?

 

Thanks if anyone can help!

 

2 Replies
Highlighted

From all investigation I've done on this in the last week, it doesn't seem recommended to install the RDInfra Agent on a master image before deploying to any given host pool.

 

Any documentation I've found seems to suggest installing the agent after machine creation and giving it then pool token.  This is a real pain and I can't see an easy way of installing this across multiple RDS environments/hosts. 


That's pretty poor, I'll add this to my "reasons this isn't an enterprise ready product", after "can't entitle groups of users" as the first reason. 



Highlighted

As a workaround, you can use the ORCA application to edit the .msi file and add the generated token value