App Volumes not creating Start Menu entries during start-up on RDSH

[MikeD3883]

Hi All,

I'm working on an App Volumes 4 deployment with instant clone RDS-Hosts to support VMware Horizon published applications.

I've captured an application, assigned it to the computer object and manually tested that it works on my RDS Farm. But I have noticed some odd/annoying behaviour when the RDS-Hosts start up. I see the application VMDK get attached to the RDS-Host VM during start up, but things such as the Start Menu entries don't appear until about 10 seconds after a user actually logs into the host. This is the case even if I leave the RDSH alone for 5 minutes after booting. This is then causing problems for Horizon when it is scanning for the applications (which is done at start up and usually before anyone can log into the RDSH), as it can't find them.

I'm currently using the following:

App Volumes Manager - 4,  version 2006

App Volume Manager - 4.1.0.57

RDSH - Windows Server 2016

Horizon - 7.10

I'm having trouble extracting the logs at the moment, but will post them if I can get them out.

I was just wondering is this expected behaviour? Has anyone seen this sort of thing before?

[MikeD3883 · Accepted solution]

Found the issue.

The DelayVirtualizationType registry key had not been set on the golden image for the RDSH Farm (as per the last line of Install App Volumes Agent  )

So App Volumes wasn't fully mounting the applications until logon - as designed.

After setting the registry key and re-publishing the applications are getting properly mounted at start-up and Horizon is able to find them.

*Face-palm*