Extend your inventory with SCCM Active Directory Attributes

Benoit LecoursSCCM11 Comments

SCCM Active Directory System Discovery is a discovery method to bring discovered devices into your SCCM server. It’s one of the most used discovery methods for its simplicity. Many organization extends their Active directory to include custom attributes to their records. By default, SCCM brings a couple of default Active Directory attributes but it’s also possible to bring any custom attribute that you may have. The good news is that it’s quite simple to add these custom Active Directory Attributes to your SCCM Discovery methods. What is more complicated is how to fetch this data once it’s discovered. Over the years, we’ve seen much different information stored in AD Attributes. For this post, we’ll add the Description attribute from a computer account to SCCM and describe how to query this information to create collections or reports. SCCM Custom Active Directory attributes Configuration The first step is to find the name of … Read More

SCCM Office 365 Inventory Report

Benoit LecoursHardware Inventory, OFFICE, REPORT, SCCM98 Comments

This post describes how to inventory Office 365 using SCCM 1606. We will also provide a free report at the end of the post that you could use on your Reporting Point to easily display Office 365 inventory data. SCCM 1606 introduces new hardware inventory classes for Office 365 configurations. You no longer need to edit your MOF files to gather Office 365 inventory. If you are using SCCM 1602 or below, follow Jason Sandys post which describes Office 365 inventory process using a MOF customization. If your goal is to deploy Office 365 updates, refer to our post on how to manage Office 365 updates using SCCM. SCCM Office 365 inventory report post summary : Office 365 Inventory Data explained How to enable Office 365 Inventory classes Verify Office 365 Inventory data on a client How to upload and use our free Office 365 report SCCM Office 365 Inventory Report – Direct Download link If you don’t want to read the … Read More

SCCM Windows 10 Inventory – Upgrade vs Fresh Install

Benoit LecoursSCCM, WINDOWS 103 Comments

With the next Windows 10 release planned for October 17th, I’m actually working on migrating a bunch of Windows 10 devices. Some are Windows 10 v1511, some v1607. Some have been installed using a fresh image and some have been migrated from a previous version. I thought it would be a good idea to inventory those devices to know their installation source (fresh or upgraded). To achieve this, we’ll need to extend our SCCM inventory to grab a custom registry key and then build a query or report to show this information. For this post, I’m using SCCM 1706 but the procedure is the same for SCCM 2012 or later. Windows 10 Fresh vs Upgrade Inventory Information The Windows 10 Upgrade information is located in the device registry in the HKLM\System\Setup\upgrade\downlevelbuildnumber. We need to modify our hardware inventory to gather this value on our Windows 10 devices. I’ll guide you through this process if … Read More

SCCM Hardware Inventory Problem on Windows 10 1607

Benoit LecoursSCCM11 Comments

  [su_box title=”Update 2016/10/28″ style=”glass” box_color=”#000000″ title_color=”#F0F0F0″]This issue is now resolved in the October 27, 2016—KB3197954 (OS Build 14393.351) update : File information and complete details available in the KB3197954 support article.[/su_box] With the increasing speed of new Windows 10 releases, SCCM administrators will be faced with new testing process before deploying to all your users. During this process at a customer, we found an hardware inventory problem affecting only Windows 1607 devices. We were able to reproduce the problem in our lab and finally decided to submit the problem to Microsoft. They confirmed that it’s actually a bug that seems to reside in the latest Windows 10 1607 release. We had no inventory problem on this device using Windows 10 1511 and no changes were made in SCCM. The hardware inventory just stopped working after the Windows 1607 upgrade. We also reproduce the problem on a fresh Windows 1607 deployment. Our setup is on SCCM 1606 … Read More