The third hotfix for SCCM Current Branch (1610) is now available. This post is a complete SCCM 1610 Update Rollup 3 (KB4010155) installation guide. If you’re looking for a complete SCCM 1511 installation guide, see our blog series which covers it all. You can’t install this upgrade if you are running SCCM 2012. You need to be running at least SCCM 1610. Installing SCCM upgrades is important for your infrastructure. It fixes a lot of issues from SCCM 1610, which some of them are important. New Update and Servicing Model If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all. You may wonder what’s the difference between a Cumulative Update (CU) and an Update Rollup (UR) : A CU is a new servicing baseline. A post-CU1 hotfix requires CU1 first, whereas a post-UR1 hotfix doesn’t require UR1. Like CU, UR are cumulative which means … Read More
BIOS UEFI Conversion using SCCM Task Sequence
With the release of SCCM Current branch 1610, one of the interesting new feature is the ability to do a BIOS to UEFI conversion in a task sequence. This would also allow to use Secure Boot with Windows 10 for strengthen security. In this blog, we’ll explain how to convert BIOS to UEFI with a task sequence on HP computers. This solution can also be applied for Dell and Lenovo computers. SCCM BIOS UEFI Conversion Prerequisites Before starting, you need 3 things : SCCM Current Branch 1610 or higher [su_box title=”Note” style=”glass” title_color=”#F0F0F0″]If you are not yet on 1610, you can achieve BIOS to UEFI following this procedure from Johan Schrewelius and Jörgen Nilsson.[/su_box] The computer manufacturer must provide a tool for BIOS configuration HP Lenovo Dell Package for Bios Configuration Utility and configuration file must be created (procedure included in this post) Create BIOS and UEFI Configuration File First, we need to create a configuration … Read More
SCCM Office 365 Client Management Dashboard Overview
Starting in SCCM 1610, you can use the new Office 365 Client Management dashboard from the Configuration Manager console. This is the fourth dashboard since the Current Branch release which is a great effort from the product group to give better visibility on the data gathered by your Configuration Manager clients. We already made an overview of the Windows 10 Servicing dashboard and the Software Update dashboard if you’re interested to read that out. You can also refer to our post about managing Office 365 Updates with SCCM and our free Office 365 report if want complete information about how to deploy and inventory Office 365 in your environment. SCCM Office 365 Client Management Dashboard Overview To open the dashboard : Open the SCCM console Go to Software Library / Office 365 Client Management The dashboard displays charts for the following: Number of Office 365 clients Office 365 client versions Office 365 client languages Office 365 client channels You … Read More
SCCM Software Update Dashboard Overview
Starting in SCCM 1610, you can use the new Software Updates Dashboard to view the compliance status of devices in your organization and analyze devices that are at risk. This is the third dashboard since the Current Branch release which is a great effort from the product group to give better visibility on the data gathered by your Configuration Manager clients. We already made an overview of the Windows 10 Servicing dashboard and the Office 365 Management dashboard will also be a topic in a future post. SCCM Software Updates Dashboard Overview To open the dashboard : Open the SCCM console Go to Monitoring / Security / Software Updates Dashboard The dashboard is divided in 5 sections : Devices Compliance Status Missing Updates by Category Critical Alerts Last Successful Synchronization Time Devices Missing Updates Devices Compliance Status Gives a number of devices the are compliant and non-compliant based on the Compliance Status Filters options using the 3 … Read More
How to Ignore SCCM Duplicate Hardware Identifiers
Prior to SCCM 1610, you may had an issue when trying to image multiple Surface or ultrabook devices using the same USB to Ethernet Adapter. A USB adapter is needed because the devices lack a built in Ethernet port. This issue could also apply when trying to image Surface devices using the Docking Station. Following a UserVoice idea, it has been fixed in SCCM 1610 and it’s now easier to ignore a particular MAC Addresses from an OS deployment. Cause Before heading to the solution, we’ll explain why this was a problem in previous SCCM releases : SCCM uses SMBIOS to identify computers and fallback to MAC Addresses if SMBIOS is not available SMBIOS is the GUID stored in the device’s BIOS or UEFI. It’s unique to the device and SCCM uses it to recognize imported computers When computers are not imported, SCCM will use their Ethernet MAC Addresses by default The problem is that … Read More