It seems crazy that only 12 months ago, we were talking about Intune vs SCCM. As many of you know, Intune has been far more focused on being an access management solution to Azure resources; whilst ConfigMgr, on the other hand, has been a traditional systems management solution. So, for many IT professionals, it was never Intune vs SCCM, but rather Intune andConfigMgr.
The traditional approach to driver management is to only do it when absolutely necessary. You might have the odd occasion when a bug fix, or a feature requires a firmware or driver refresh, but if it’s working, you probably don’t need to fix it…unless it’s a Microsoft Surface device!
EXISTING DEVICES - THE GOOD…THE BAD
I think we’ve become a little blind-sided by terminology lately. Talk about adopting a Cloud strategy - and it conjures up a vision of a ‘Cloud platform’ somehow managing all of your data and infrastructure.
In reality, the cloud simply provides additional capacity to run workloads and give elastic-level scale to your capacity. Management is something else though, and it seems that the teams at Microsoft are starting to recognise this too, if the announcements at Ignite 19 were anything to go by.
The BIG news from Ignite '19 for System Center Configuration Manager (SCCM), is that it’s still alive and kicking! Despite fears that it would be dropped, it’s been given a new lease of life, in its new home – Microsoft End Point Manager (MEM).