SOLVED

Spring Update: Creating Host Pool with a VM - Portal UI Bug?

%3CLINGO-SUB%20id%3D%22lingo-sub-1405741%22%20slang%3D%22en-US%22%3ESpring%20Update%3A%20Creating%20Host%20Pool%20with%20a%20VM%20-%20Portal%20UI%20Bug%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1405741%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20I%20am%20doing%20something%20wrong%20or%20this%20needs%20some%20fix.%3C%2FP%3E%3CP%3EIt's%20a%20quite%20simple%20scenario%2C%20here%20we%20go%20-%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ECreating%20a%20brand%20new%20host%20pool%20(pooled%20type)%20using%20Azure%20portal%20UI.%3C%2FLI%3E%3CLI%3EWhile%20creating%20the%20host%20pool%2C%20creating%20single%20VM%20(%3CSPAN%3EStandard%20B2ms)%3C%2FSPAN%3E%20in%20it%20that%20is%20based%20on%20an%20custom%20Win10%20Enterprise%20multi-session%20image%20provisioned%20in%20the%20shared%20image%20gallery.%3C%2FLI%3E%3CLI%3EAlso%20selecting%20to%20create%20a%20new%20workspace%20so%20that%20default%20desktop%20app%20group%20can%20be%20associated%20to%20it.%26nbsp%3B%3C%2FLI%3E%3CLI%3EDeployment%20succeeds%2C%20can%20see%20that%20the%20VM%20gets%20provisioned%20and%20joined%20to%20correct%20domain.%20Also%2C%20can%20RDP%20into%20it%20from%20one%20of%20the%20domain%20joined%20jump%20box%20and%20appears%20fine.%20(can%20see%20wvd%20agent%20and%20agent%20boot-loader%20installed%20on%20it%20by%20default)%3C%2FLI%3E%3CLI%3ECan%20also%20see%20the%20Host%20pool%20provisioned%20along%20with%20the%20default%20desktop%20app%20group.%20The%20workspace%20is%20also%20provisioned%20and%20shows%20default%20desktop%20app%20group%20associated%20to%20it.%26nbsp%3B%3C%2FLI%3E%3CLI%3EBut%20when%20I%20see%20the%20host%20pool%20-%20I%20expect%20that%20the%20VM%20should%20appear%20in%20the%20Session%20Hosts%20but%20it%20doesn't%20show%20up%20there.%20(Refer%20screenshot%20attached)%3C%2FLI%3E%3C%2FUL%3E%3CP%3ECan%20someone%20confirm%20if%20there%20is%20something%20wrong%20with%20deployment%20steps%20or%20could%20it%20be%20a%20potential%20bug%20or%20an%20expected%20behavior%20(that%20will%20be%20surprising).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFYI%20-%20all%20my%20deployments%20are%20in%20the%20Southeast%20Asia%20region%20and%20metadata%20is%20being%20stored%20in%20West%20US%20region.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1408296%22%20slang%3D%22en-US%22%3ERe%3A%20Spring%20Update%3A%20Creating%20Host%20Pool%20with%20a%20VM%20-%20Portal%20UI%20Bug%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408296%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F624245%22%20target%3D%22_blank%22%3E%40bhushangawale%3C%2FA%3E%26nbsp%3Ball%20right%2C%20seems%20I%20have%20found%20the%20issue.%20It%20was%20because%20of%20the%20fact%20that%20the%20image%20itself%20was%20containing%20the%26nbsp%3B%3CSPAN%3Ewvd%20agent%20and%20agent%20boot-loader%20installed%20on%20it%20and%20hence.%20Had%20to%20re-create%20the%20image%20without%20these%20agents%20and%20issue%20was%20resolved.%20a%20big%20thanks%20to%26nbsp%3BDean%20Cefola%20for%20the%20tip!%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Not sure if I am doing something wrong or this needs some fix.

It's a quite simple scenario, here we go - 

 

  • Creating a brand new host pool (pooled type) using Azure portal UI.
  • While creating the host pool, creating single VM (Standard B2ms) in it that is based on an custom Win10 Enterprise multi-session image provisioned in the shared image gallery.
  • Also selecting to create a new workspace so that default desktop app group can be associated to it. 
  • Deployment succeeds, can see that the VM gets provisioned and joined to correct domain. Also, can RDP into it from one of the domain joined jump box and appears fine. (can see wvd agent and agent boot-loader installed on it by default)
  • Can also see the Host pool provisioned along with the default desktop app group. The workspace is also provisioned and shows default desktop app group associated to it. 
  • But when I see the host pool - I expect that the VM should appear in the Session Hosts but it doesn't show up there. (Refer screenshot attached)

Can someone confirm if there is something wrong with deployment steps or could it be a potential bug or an expected behavior (that will be surprising).

 

FYI - all my deployments are in the Southeast Asia region and metadata is being stored in West US region. 

1 Reply
best response confirmed by bhushangawale (Contributor)
Solution

@bhushangawale all right, seems I have found the issue. It was because of the fact that the image itself was containing the wvd agent and agent boot-loader installed on it and hence. Had to re-create the image without these agents and issue was resolved. a big thanks to Dean Cefola for the tip!