Updates should be tested before the installation on production environment. Create a pre-production to validate updates Same baseline should be gathered in the same SCCM collection to ease software updates. That means that systems should be based on the same image installation, same Operating System (as much as possible) and application version and so on. A good source for security purpose is the CERT (sorry it is a French link J).Īll your system should be set on the same way to ease management and find the issue. There are many solutions to make a technology watch: RSS (ex: Microsoft bulletin), Twitter ( #security #updates) or Microsoft Security Bulletin Notification. Sometime an emergency update is released by Microsoft to fix a vulnerability so it is necessary to patch quickly and to reduce the risk to be attacked. It is important to be aware about the last updates (often the second Tuesday of the month) but also the last security issue. Subscribes to news site about updates and security T o conclude the SCCM Software Update subject, I will present some SCCM software update best practices to manage Micorosft updates in production environments. SCCM Software Update PART 5 – Best practices.SCCM Software Update PART 4 – Create deployment packages manually.SCCM Software Update PART 3 – Automatic Deployment Rules.SCCM Software Update PART 2 – Software Update Point configuration.SCCM Software Update PART 1 – Introduction to SCCM and WSUS.
