VMware Horizon Community
compwizpro
Enthusiast
Enthusiast
Jump to solution

Software installed on RDSH server with Appstack assigned isn't available after reboot

We currently have a few Server 2016 servers running Horizon Agent 4.8 and App Volumes 2.17.  We installed some software such as MS Office, SAP Gui, etc on the RDSH server initially to present as applications through Horizon.  After that, we installed some additional software into an AppStack and assigned that to the RDSH server and added that as a published application as well.  The published application on the AppStack was accessible successfully through the Horizon client.

However, when we went to install additional software on the RDSH server while the AppStack was assigned, whenever the server got rebooted the software would be removed. There would be no program files folder entries, shortcuts, etc. and was as if the program was never installed.  We also had issues uninstalling the software software such as Office where the uninstaller would complete successfully but after reboot, everything would still be present.  After suspecting App Volumes might be interfering due to it's filter driver, I unassigned all AppStacks from the RDSH server and was successfully able to install and uninstall applications again.

Is this expected behavior with App Volumes?  Is there a way to install applications on an RDSH server after the fact or is it required to either put all software in the base image and use an automated RDS pool where if you want to modify software, you do it in the parent and re-compose the pool?  Or do you make any additional software add as an App Volume and leave the base image immutable?  People that are using App Volumes on RDSH, are you using one of the above mentioned scenarios or are you doing it differently?

Thanks!

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
sjesse
Leadership
Leadership
Jump to solution

This is by design, you can't do anything while an appstack is attached.When appvolumes is attached and most file and registry options are redirected to the appstack, which is readonly so when you restart it all goes away. The idea is if you need to update anything on the guest image you updated it on the image the rds farm uses and then push the new image out.

View solution in original post

Reply
0 Kudos
2 Replies
sjesse
Leadership
Leadership
Jump to solution

This is by design, you can't do anything while an appstack is attached.When appvolumes is attached and most file and registry options are redirected to the appstack, which is readonly so when you restart it all goes away. The idea is if you need to update anything on the guest image you updated it on the image the rds farm uses and then push the new image out.

Reply
0 Kudos
compwizpro
Enthusiast
Enthusiast
Jump to solution

Thank you.  For some reason I couldn't find that documented anywhere but that makes perfect sense.  I am working on creating an automated RDS pool which seems like it will work the best. 

Reply
0 Kudos