I have a couple of questions for LTSB users:
1. Why did you decide to use LTSB on VDI?
2. Are you using LTSB along with UEM and Appvolumes (Writable or Appstask or both)?
3 Which version of Office are you using?
4. Any problems with applications not installing or not working?
5. Any problems with the OS?
6. Are you planning on going back to CBB and if so why?
Thanks for the feedback.
1 - Because it's supported VMware Knowledge Base and because it does not have as much junk as CBB https://mythoughtcube.com/2017/04/25/horizon-view-and-windows-10-ltsb/
2 - Persona Management
No would be the answer for 4, 5 and 6
LTSB is idd the way to go if you don't want any unnecessary metro/appx applications (weather, xbox, etc) You can have a better performance without all these apps.
But keep in mind, if you want a newer release/feature updates you cannot update the image with windows updates; you will have to create an entirely new image.
I don't recommend writable volumes at all, we had some nightmare projects with this.
Only use appstacks to deliver the applications and use VMware UEM to save user and application settings.
Thank you for your feedback. If you don't mind can you go over some of the problems that you encountered with a writable appstack?
I'd like to her about your experience with writable volumes too. We are planning to use writable volumes as we transition from linked clones to instant clones to give us the same functionality as persistent disks.
When using together with VMware UEM, there are essentially two products which can save user and application data, this can be challenging:
- VMware UEM you have to configure the configuration files with entries you want to include in the profile
- With AppVolumes writables you configure to snap conf file with entries you want to exclude from the profile