The IT team at a small government organization wants to deploy Windows RDS desktops to their end users. They want the end users' profile and application customization setting preserved. They also want to deploy applications using VMware App Volumes.
What should be implemented to meet requirements?
To preserve end users' profile and application customization settings while deploying Windows RDS desktops, using Horizon instant clone RDS hosts with User Environment Manager is the best option. User Environment Manager (UEM) allows for the management of profile settings and application configurations, ensuring that these customizations are retained across sessions. Additionally, the use of Horizon instant clone RDS hosts ensures quick and efficient deployment of the desktops. App Volumes, while crucial for application deployment, does not support writable volumes in an RDSH environment for user-specific data and settings.
The answer is A.. Writable Volumes is not supported on RDSH. https://kb.vmware.com/s/article/2151829
I think A is correct
This is another one of those tricky questions. A and C would both be acceptable and you can argue either one but usually AppVolumes writable volumes is a compliment to UEM and, although it will work on its own, usually does not act alone. I would pick A in this case.
but "They also want to deploy applications using VMware App Volumes" so i think that C is better
I agree with rfountain on this one primarily because they want to preserve application customization settings. In this case, UEM is required vs Writable volumes because you cannot preserve application customization settings with App Volumes writeable volumes, only application files and user installed applications
cdyoungtech is correct, you cannot mount writable volumes to rds hosts. A is correct an the one that makes the most sense
A I think everyone is failing to remember that writeable volumes are 1:1, A single writeable Vol per VM attachment. RDS hosts have many users, you cannot mount writable vol to RDS Hosts
Definitively
C is correct, they are deploying Windows RDS desktops, not deploy Windows RDSH.
Just a little detail: Writable Volumes is NOT supported on RDSH IF the assignment is for a USER, but if the assignment if for a COMPUTER, writable Volumes IS compatible with RDSH.
Answer "A" as this is RDS desktop which is the old terminal services session and not a proper VM. As we cannot assign Writable vols to RDSH then "A" is the only option
In my opinion letter C, because in writable volumes we can saved our data of applications and profiles.
You cannot attach Writeable Vol to RDSH
Hi Mezze, did you pass the exam ?