Forum Discussion
WVD Patch Management
You can use this ARM Template for updating WVD.
https://github.com/Azure/RDS-Templates/tree/master/wvd-templates/Update%20existing%20WVD%20host%20pool
Hi Yuki398,
Thanks for the link. I've see this and believe this along with applying security & feature updates to the 'master image' is the best method for pooled desktops. If you are using personal desktops that users are modifying (deploying software etc) you cannot remove their persistent vdi's and give them a brand new one every time the OS needs patched. Its not feasible. I think until app attach is in GA its not a straight forward process for applying updates to personal desktops
- Hi Gerry,
Why would App Attach offer a solution to your problem? App attach makes applications seamlessly available through a separate VHD(x) drive integration. This is opposite to users installing their own software.
I still believe that personal desktops together with FSLogix can be a solution in separating the user data from the OS. If all applications are available in the image, there would not be any issue for the user in a redeployment (for patching etc). This enables you to have a consistent user experience along your users, compared to desktops patching separately etc.Hi knowlite,
I probably didn't explain it well enough. We would want to give a group of users, possibly up to 20 a personal desktop with admin rights. They could be using a significant number of different applications (probably too many to have in a master image ). Also these applications could vary quite frequently for different development staff. In short ' image management' becomes too intensive from an app perspective. I do take the point that app attach is not necessarily a silver bullet but it does help with the separation of the apps from the OS and also keeping the updating of the apps and the OS segregated.
Effectively I was trying to find out if there was any reason why I couldn't just allow the personal desktops to autoupdate using windows update. I understand the inherent risk associated of adopting this method with respect of an update causing an issue on the desktop.
We use SCCM to patch WVD - Personal Desktop on monthly basis. We consider it no different than regular corporate desktop. This way, there is no new process/project/standards created for handling WVD - Personal Desktop. Works very well with existing patching operations. End-users are already familiar with how patching works on corporate desktop, so they don't have any issues with WVD - Personal Desktop patching process.
