A government organization wants to deploy a brand new Horizon system using RDSH desktop automated farms while installing the fewest instances of Windows servers. They also want to preserve user profiles, personalization and application customization.
Which option meets the requirements?
To meet the requirements of deploying a Horizon system with RDSH desktop automated farms while installing the fewest instances of Windows servers, and simultaneously preserving user profiles, personalization, and application customization, the best choice is to use RDSH instant clone farms and User Environment Manager (UEM). RDSH instant clones are preferred because they streamline management and reduce the need for additional infrastructure, which aligns with the objective of deploying the fewest instances of Windows servers. Additionally, UEM effectively manages user profiles and settings, ensuring personalized experiences and application customization for users.
We got 2 requirements: 1) Writeable volumes for user-profiles and 2) Fewest instances of Windows Servers. In KB https://kb.vmware.com/s/article/2151829 we can see that Writable Volumes cannot be assigned to RDSH users, so we must use UEM. And 2nd requirement limits us with Instant Clones because we need to deploy additions Windows instance for View Composer if want to use Linked Clones.
From my understanding and studying. Writable volumes is not compatible with rdsh and theres no instant clone solution for RDSH. I would pick rdsh with UEM D
"User Writable Volumes are not applicable to RDSH" - https://techzone.vmware.com/resource/app-volumes-architecture#architecture-overview
I believe the answer is C based off the solution having a requirement of "fewest instances of Windows servers." Linked Clones require an additional Composer Server and App Volumes Writeable Volumes also has additional Server requiremetns when compared to UEM as a profile solution.
The answer is C because there is another question with the exact wordings except in the other question they mentioned using app volumes to capture the users and applications settings but in this one they did not. And yes you guessed it. The answer to the other question is RDS with writable volumes.
KB 2151829, Writable volume cannot be assigned to RDSH users. And it should be Instant Clone for ease of management and scalability. UEM will do the per user per app customisation. UEM will capture anything written to registry settings we specify to capture and anything to the users\userid\appdata
This should be "A" Instant Clones writeable App Volumes. UEM enforces the settings but it does not capture anything written to disk. Put another way, if the user's profile allows it, an application could be installed within a persisent session and UEM would have no knowledge of it. Writeable volumes would preserve the installed application settings.
It should not be D? "linked clone" instead of "instant clone"?
The reason is that they want to preserve user profiles, rationalization and application customization. You can do that with a linked clone, however extra configuring would need to be done because a default profile is automatically created in the persistent disk which means more disk space usage and overhead of having to worry about profiles being considered "local" to the vm. Much easier, less space, easier management with an instant clone