The release of System Center Configuration Manager Current Branch 1906 (SCCM Current Branch) is providing an updated discovery method to your Azure AD tenant. As you may be already aware, you have been able to discover your Azure AD users objects with SCCM for quite some time now. Well, this Azure AD discovery functionality has […]
SCCM – You can now discover your Azure AD Security Groups with SCCM Read More »
With the release of System Center Configuration Manager Current Branch 1906 (SCCM Current Branch), the co-management feature has been improved to allow you to define different device collection while piloting co-managed workloads. With the previous release you were able to pilot the co-management for specific workloads (compliance, device configuration, Windows Update…) but the piloting applied
SCCM – You can now use different collection for piloting co-management workloads Read More »
The new release (1906) of System Center Configuration Manager Current Branch (SCCM Current Branch) is now available. As always it will be available for install from your SCCM administration console within the next few days but if you want to force the detection and install you can use the script available here http://download.microsoft.com/download/4/9/3/493BC9DE-ACAC-4D11-8B7E-5AFCECC626C2/EnableEarlyUpdateRing1906.exe This new
SCCM – System Center Configuration Manager Current Branch 1906 is now available Read More »
As you may be aware, System Center Configuration Manager (SCCM) Current Branch has been providing insights about your devices using Windows Analytics, helping you in the upgrade process from previous version of Windows to Windows 10. Well, Windows Analytics is now evolving into Desktop Analytics to provide more recommendations and better application compatibility. To start
SCCM – Desktop Analytics is now available in public preview Read More »
As the latest release of System Center Configuration Manager Current Branch (1902) has been released, there has been quite few improvements. 2 of them apply (as many others) to Operating System Deployment (OSD): you can now import to SCCM only 1 index from the WIM file instead of the complete list of index you can
SCCM – Improvements in OSD with SCCM 1902 Read More »
The latest update for System Center Configuration Manager (SCCM) Current Branch has been made available. The new version (1902) will show up in the SCCM administration console (Administration Workspace\Update and Servicing). If you can not wait to get it, you can use the now famous script to force the update – https://gallery.technet.microsoft.com/ConfigMgr-1902-Enable-87eef616?redir=0 To get the
SCCM – The new version (1902) of SCCM Current Branch is available Read More »
With incoming April updates for Intune (version 1904), an update CSP path for email profiles is going to be deployed and will break your existing email profiles configured for Windows 10 (desktop and mobile). This fix is going to solve an identified issue with selective wipe. To be prepared, you need to capture every email
Intune – Be prepared as an updated CSP path is going to break your Email Profiles Read More »
After few months of waiting, the latest version (8456) of the Microsoft Deployment Toolkit (MDT) is now available for download. This version provides support for Windows 10 1809 and Windows Server 2019. You can get it from https://aka.ms/mdtdownload As always, you will have to update your existing MDT share and/or the SCCM integration.
SCCM/MDT – The latest version of the Microsoft Deployment Toolkit is available Read More »
As you may already know, System Center Configuration Manager (SCCM) and Intune can work together, delivering a co-managed device management solution. Well, you can now use the compliance state from SCCM with Intune. This setting will only apply to co-managed devices, if the devices are managed by Intune only, this will not be applicable. To
Intune – You can now check the compliance from SCCM Read More »
If you use System Center Configuration Manager (SCCM) to manage updates deployment, OS deployment and additionally keeping up to date your OS image (WIM), you need to know that SCCM offline servicing is incorrectly detecting Windows Server 2019 WIM image as Windows Server 2016. This has been confirmed as a bug in SCCM and should
SCCM – Offline servicing for Windows Server 2019 is not working Read More »
