The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1. WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde
The good thing about collections in SCCM 2012 is we have separate nodes for Users and Devices Collections helping us to segregate in a better way. There is a new node called “Assets and Compliance” that deals with the users, systems, metering and compliance settings. While creating collections, we now have an option to include or exclude certain collections from the newly created collection. This is highly useful when you have to maintain an infrastructure where there are validated machines and the management doesn’t want to bring those machines under the radar. Here, I am creating a device collection that consists of Windows 7 operating system machines. 1. Go to Assets and Compliance> Right click on Device collections> Click on Create Device collection. 2. General tab: Enter the collection name: here it is “All Windows 7 Systems” Enter description, and most importantly click on browse and select a limiting collection. Limiting collection has to be sp