Forum Discussion
WVD Patch Management
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.
Just FYI,
FYI,
On ConfigMgr CB 2002 version, each WVD - Shared Desktops or Persistent Desktops are reported as "Windows Server" Operating System on ConfigMgr. Don't know why?
So, to manage WVDs with ConfigMgr, we made appropriate changes on ConfigMgr Collection's Limiting Collection and set to - "All Systems".
irfan.fakih@hotmail.com
It' correct.
As Christiaan Brinkhoff says (https://twitter.com/brinkhoff_c/status/1244557292214915072), Windows 10 Enterprise Multi-session has a different OperatingSystemSKU (175) and it's not a client-sku.
Davide
- Windows 10 Enterprise Multi-Session Support is there from SCC 1906 version onwards. Windows 10 multi-session support is only for Windows Virtual Desktop (WVD) solution. WVD Windows 10 multi-session is similar to a terminal server and most of the device management solutions are detecting multi-session as server OS. You will need to select the server-related patches as explained in the following post. https://www.anoopcnair.com/wvd-windows-10-multi-session-patching-with-sccm-configmgr-product-selection/
FYI, Based on extensive testing, I found WVD persistent VMs created based on "Microsoft Windows 10 + Office 365 ProPlus" image from Azure Marketplace is not working. SCCM CB 1906 version or CB 2002 version is unable to patch these VMs using the regular SCCM patching process SUM - (Software Update Management). And feedback or solution will be helpful.
