Forum Discussion
WVD Patch Management
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
- Davide SalsiJun 05, 2020Copper Contributor
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
- Anoop C NairApr 14, 2021MVPWindows 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/
- Steven BlattAug 23, 2021Copper Contributor
Hi Anoop C Nair Do you know if there were any changes to the patches for 21h1 forward?
i am not seeing server version 21h1 like i did for 20h2 and 2004.
Thank you in advance