IT admins will occasionally get bit by buggy Microsoft updates on Windows devices. This is a manual and time-intensive process to follow, especially at a time when Microsoft releases several updates at different times of the month. Later, they would push the patches to legacy and more delicate devices. Some admins would read up on every single update, deploy to a test group and then roll out to the main fleet. They either allowed all updates as they arrived or they allowed the critical and security updates straight away and held off on the rest for testing. WSUS helps automate the busywork of Windows patchingįor a long time, many admins used WSUS in a mostly automated fashion. SCCM ingests the updates downloaded via WSUS and uses its own client to deploy them, using the workflow and rules defined in ConfigMgr. System Center Configuration Manager (SCCM) - also known as ConfigMgr and recently rebranded as Microsoft Endpoint Configuration Manager - came along and offered even more control over Windows updates. WSUS helps maintain order: Instead of having all the Windows clients go to the internet and download the updates, you have one or more WSUS servers that centralize the job and give you control on which updates to release to the clients. WSUS is still fully supported and many companies rely on it. Microsoft released Windows Server Update Services (WSUS) in 2005 to supersede Software Update Services (SUS).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |