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 : SCCM Office 365 Inventory Report – Direct Download link If you don’t want to read the whole post, you can download the RDL file directly using this link : Office 365 Inventory Data Office 365 is using new update channels and update mechanisms. Tracking versions and update … Read More
SCCM Windows 10 Inventory – Upgrade vs Fresh Install
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
Win32_TPM Class in Hardware Inventory is missing Data by Default in Configuration Manager 2012
In Configuration Manager 2007, we were querying WIN32_TPM in hardware inventory for laptop security report. After the 2012 migration, the report was returning no value on this specific class. The usage of Bitlocker rely on TPM (Trusted Platform Module). We found by looking in the SQL query of the report that IsActivated, IsEnabled and IsOwner were selected but missing from 2012 inventory. This is collected throught hardware inventory so I decided to take a look at the default client settings. As you can see the screenshot below, WIN32_TPM class in hardware inventory is configured by default in Configuration Manager 2012 with missing information of the WMI class. To remediate at this situation, delete and recreate the class with the same name or a new one in the default client settings by importing the following TPM MOF file. [SMS_Report(TRUE), SMS_Group_Name(“TPM”), SMS_Class_ID(“MICROSOFT|TPM|1.0”), namespace (“\\\\\\\\.\\\\root\\\\CIMv2\\\\Security\\\\MicrosoftTpm”)] class Win32_Tpm : SMS_Class_Template { [SMS_Report(TRUE), key] string SpecVersion; [SMS_Report(TRUE)] string ManufacturerVersion; [SMS_Report(TRUE)] string ManufacturerVersionInfo; [SMS_Report(TRUE)] uint32 ManufacturerId; … Read More
SCCM 2012 : Hardware Inventory ConfigMgr Error Object
The hardware inventory in SCCM 2012 has been designed for ease of configuration. The integration with the client setting concept also helps in problem solving. I had a problem this week with a client where a specific information was not replicated to the primary after a hardware inventory. My first reaction was to analyze the configuration.mof and confirm that the information was well inventoried in WMI. Everything was perfect. Checking the inventoryagent.log file during a hardware inventory scan found that no WMI query was executed the specific WMI class. I targeted the custom device setting and try to open the hardware inventory console. I get a ConfigMgr Error Object then crashed my console. WTF! ‘CSspInventoryReport::GetRealInstance: Failed to get item from database’ The problem of ConfigMgr Error Object is caused by data corruption within the policy. The solution is quite simple, delete and recreate. Technet Reference I tried to open the console again without issue. After the new policy … Read More