SCSM: Management and CMDB for Linux Devices via Import Software Inventory from SCCM

Dujon Walsham • 21 December 2018

Manage your Cross-Platform Estates!

Import Management Packs into SCSM

You will require the following pre-requisites for this

Management Packs

  • WS Management Library
  • Client Monitoring Library
  • Data Warehouse Library
  • Network Device Library
  • System Center Core Monitoring
  • Microsoft Audit Collection Services
  • System Centre Core Monitoring Views
  • Microsoft System Center Operations Manager Library
  • Once these are imported you can then import the management packs from the System Centre Management Packs for UNIX which is used to discover all Linux/Unix Cis within SCOM

Run the SCOM CI Connector

Once these are imported you will need to run the PowerShell commands to add them to the Allow list class which will enable them to be synchronized via the SCOM CI Connector

Get-SCSMClass -Name "*Unix*" | ForEach-Object {$_.Name} {Add-SCSMAllowListClass -ClassName $_.Name}

( Note : If adding anything else such as Linux, Solaris, RHEL then change the value where the name switch is specified)

Once these have been added you can confirm them within the list using the Get-SCSMAllowList

Then you can use the synchronize button for the SCOM CI Connector which you have. Once completed you can create a custom view which will show the Linux/Unix Cis which would have been imported from your SCOM CI connector

Import Linux Software Inventory & Relationships

Once you have the CIs of your Unix/Linux devices imported, the next part you will require is the hardware/software inventory which comes from the SCCM side as there is no direct synchronization within the connector.
In this case you can use the following script which i have here that performs the following

  • Connects to your SCCM Database
  • Runs a query to pull all of the Hardware/Software Inventory
  • Discover the Linux/Unix Cis in your Service Manager
  • Discover the Software Item class in Service Manager
  • Creates all of the Linux Software items in Service Manager
  • Creates the relationships between the Linux/Unix CI and the Software item CI

The script can be downloaded here https://gallery.technet.microsoft.com/Linux-Software-Inventory-14402621

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 4 - SQL Server Requirement Analysis

by D Walsham • 13 December 2021
Looking through the current SQL Server topology and how it affects our decision

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 3 - Current Branch Upgrade Approaches

by D Walsham • 19 November 2021
Impact of Current Branch Upgrades

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side - Part 2 - Operating System Considerations

by D Walsham • 29 October 2021
Introduction

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side

by D Walsham • 7 October 2021
Introduction

Endpoint Manager: Device Estate Cleanup

by D Walsham • 6 October 2021
Introduction

Modern Workplace Management: Creating Applications Common Practices - LOB vs Win32 Package

by D Walsham • 3 September 2021
Introduction

Modern Workplace Management: Build Endpoints Without SCCM Part 6

by D Walsham • 12 August 2021
All the parts of the series we went into great detail about how we analyse an end to end solution and how we would design a solution in which would allow us to build endpoints without SCCM being a dependency. Whilst we did this, there is another scenario which we have not touched on yet, which is the hybrid scenarios. In a perfect world ideally you would have your Azure Active Directory within the cloud, every machine meets the recommended requirements for Windows 10, everything is imported into Intune/Autopilot and everyone is happy. But we know this isn't realistic in all cases. Many organisations cannot just simply up and go from on-premise into the cloud therefore the checkpoint here is of course getting into hybrid solutions such as; Co-Management Between Intune and SCCM Hybrid AD with Azure AD and On-Premise AD syncing together These things can play a very interesting part in how you would tackle this if you envisage the next step in the blueprint is to be in a position in which you can build and manage endpoints soley within Intune. With this final part of the series we will go in-depth in how the common hybrid setups look like and how we go about moving into the next step of being able to manage and build devices without SCCM.

Modern Workplace Management: Build Endpoints without SCCM Part 5

by D Walsham • 29 July 2021
In continuation from the previous part where we had discussed how we create the "on site" piece of the solution, this was the part which would allow us to get our endpoints into a state in which they would essentially be ready to go through the Autopilot process. Which leaves our next piece of the puzzle, to begin the configuration of the actual backend side that resides within our Endpoint Management console. And you will see how everything ties up together to satisfy the full end to end process of getting an unknown (or known) device to proceed thorough the whole workflow to be finally managed by Intune without the aid of SCCM taking part in any of the prerequisites or preparation at hand.

Modern Workplace Management: Build Endpoints without SCCM Part 4

by D Walsham • 15 July 2021
In this part we are now going to look into the technical step by step points on how we put everything together. In the previous part we spoke about the structure of how we would asses whether a machine was actually ready to be built with Autopilot or not with a build checklist process which would step through all areas which would cover an endpoints eligibility. Now with everything planned out we finally want to step into making things reality by putting everything together.

Endpoint Manager: Find machines not in Autopilot

by D Walsham • 2 July 2021
When it comes to managing your endpoints in endpoint manager, one of the things you may be looking to do is to get all of your Intune registered machines to also be enrolled as Autopilot devices. Now we can of course just have the deployment profile deployed to all machines and then hit the "Convert targeted machines to autopilot" but this might not necessarily be feasible for every client. We may want to perform some due diligence first so we can at least understand what devices in Intune are not in Autopilot.
Show More