SCCM (A.K.A ConfigMgr) Explained
SCCM is Microsoft Microsoft Endpoint Manager Configuration Manager. This solution is used by most of the organizations in the world to manage their enterprise devices. This is the best resource to Learn and troubleshoot on issues.
How is SCCM (A.K.A ConfigMgr) Used?
SCCM solution is mainly used to manage Windows devices. But it has rich capability to manage and Mac OS devices as well. As per Microsoft, this tool is managing more than 75% of enterprise devices of the world. Linux and Unix devices are not supported by MEMCM (A.K.A Microsoft Endpoint Manager Configuration Manager)
How CAN SCCM Be Applied to Your Organization?
This solution can be used to install the application within your organization. OS deployment is another feature of this solution used within most of the enterprises. Another important use of this solution is to deploy patches across the enterprise and secure those devices.
There are 1000000 devices managed by this solution around the world. And SCCM device management solution is used within organizations to deploy millions of applications.
Server Client Application
This solution is a server-client application. All the managed clients’ inventory is stored in the CM SQL database.
SCCM Core infrastructure, Updates for Configuration Manager, Supported configurations for Configuration Manager, Cloud-attached management of CM, Co-management for Windows 10,
Manage clients on the internet, Windows as a service, CMPivot, Application management.
Other Uses for SCCM
SCCM can used for Manage apps from the Microsoft Store for Business, OS deployment, Introduction to OS deployment, Upgrade to Windows 10, Phased deployments, Software update management, Introduction to software updates management, Manage Office 365 ProPlus updates.
SCCM MVP community group is one of the known community groups in the IT Industry.
Let’s discuss troubleshooting SCCM Issues with SuperFlow: A Newbie Guide Configuration Manager ConfigMgr. I have a post about troubleshooting steps for newbies using flowcharts. SCCM flowcharts are the best way to understand the workflow/data flow/process of each SCCM component.
The SuperFlow is an interactive content model. The SCCM SuperFlow provides an interactive content model structured for viewing documentation.
In this post, you will find all the information you need to troubleshoot SCCM issues using SuperFlow. This guide is perfect for newbies navigating Configuration Manager (ConfigMgr).
Learn the SCCM Client Installation process with SuperFlow
Learn the SCCM Client Assignment Process with SuperFlow
Learn the SCCM Backup Process with SuperFlow
Learn the SCCM Restore Process with SuperFlow
Download SCCM SuperFlows
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Table 1
What are SCCM SuperFlows? SCCM Troubleshooting Guide for Newbies with SuperFlow
I have a YouTube channel. Subscribe here to watch and learn about SCCM with the video tutorials about SCCM-related issues and installations. I also have a Facebook page here. This is also where I usually upload the SCCM/Intune-related videos.
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Video 1
What is SCCM SuperFlow?– Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr
Each SuperFlow includes comprehensive information about a specific SCCM data flow, workflow, or process. The SCCM SuperFlow Contains the following.
Detailed Information
Procedures
Sample Log entries
Best practices
Real-world scenarios
Troubleshooting information
Security information
Animations
Learn the SCCM Client Installation Process
The CCMSetup process superflow explains how CCMSetup installs the SCCM clients.
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Fig.1
The CCMSetup client installs flow for the SCCM CB version has not been updated. However, it is better to get the basics right about installing the SCCM Client. When you have a problem with SCCM client installation, this superflow will help you troubleshoot and resolve the issue.
Two log files are associated with this CCMSetup superflow and SCCM client installation process. SCCM client setup file “CCMSetup.exe” searches for the SCCM Management Point (then Distribution Point) server for the rest of the client installation and prerequisite files.
CCMSetup.log
Client.MSI.log
Learn the SCCM Client Assignment Process with SuperFlow
The client assignment starts once the SCCM client is installed successfully on a workstation. The client will be able to receive the policies from the server after the client is assigned to a particular SCCM site.
When the SCCM client is installed successfully, it is considered an unmanaged device but not assigned to a site. There are two methods for assigning clients: manual and auto-site. The SCCM client superflow explains these two methods.
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Fig.2
Learn the SCCM Backup Process with SuperFlow
The SCCM backup process is changed in SCCM CB. Microsoft fully supports SQL backup, so there is no need to take a full SCCM backup. However, in some scenarios, we still need one. SCCM backup SuperFlow helps to understand the process of SCCM full backup.
SCCM backup is initiated by a scheduled maintenance task or manually starting the SCCM backup service. Once the backup service is created, the backup snapshot destination is prepared, and backup logging starts.
The SMS VSS writer (SMS_SITE_VSS_WRITTER) and SQL server VSS writer (SMS_SITE_SQL_BACKUP) services will be triggered as part of the SCCM backup. These two services will help start VSS snapshots for site settings and databases. The Smswriter.log file provides more troubleshooting details.
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Fig.3
The first step is to specify the backup files to restore. SCCM will verify the backup patch to determine whether you have a valid backup. Site data and the SQL database will then be verified and restored.
Troubleshoot SCCM Issues with SuperFlow A Newbie Guide Configuration Manager ConfigMgr – Fig.4
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
Download SCCM ConfigMgr PREVIEW Version Configuration Manager ConfigMgr. SCCM Product Group released the newest version of ConfigMgr CB Preview 1710. This is not the production version of SCCM CB 1710.
I hope the production version 1710 will be released somewhere in November 1710. This post will see “How to Download SCCM ConfigMgr 1710 PREVIEW Version.”
The download link below should be used ONLY when the SCCM preview version is not installed in your LAB environment or has expired. The SCCM CB Preview version is valid only for 90 days or 3 months.
For example, if you have installed SCCM CB preview 1708 and skipped 1709 and 1710, you won’t be able to upgrade the 1708 version to 1711. In the above example, you need to build a new SCCM CB preview infra with the latest baseline build of the preview version.
Download SCCM ConfigMgr PREVIEW Version Configuration Manager ConfigMgr
If you already have a preview version and it’s working fine, the latest SCCM CB 1710 update will automatically appear in the console. You should NOT install this version of SCCM in a production environment. Technical preview versions of SCCM CB will be released every month.
Download SCCM ConfigMgr PREVIEW Version Configuration Manager ConfigMgr – Fig.1
High-level View SCCM 1710 Preview Upgrade
I recommend that SCCM admins install the preview version of SCCM CB in their lab environment. This will help them keep up with the new features enabled in every preview release.
SCCM ConfigMgr CB 1710 Preview – Download the content
SCCM ConfigMgr CB 1710 Preview – Available to Install
SCCM ConfigMgr CB 1710 Preview – Installation Process
SCCM ConfigMgr CB 1710 Preview – Post Installation Steps
SCCM ConfigMgr CB 1710 Preview – Console Upgrade
What are the Known Issues of SCCM 1710 Preview?
When configuring a task sequence, we must carefully use an operating system upgrade package or image. This is because Windows 10 1709 fall creators update media includes multiple editions, so we need to select the one SCCM/ConfigMgr supports. More details are available
I have a post and video tutorial about creating Windows 10 1709 upgrade TS and operating system upgrade package. You can look at the post from the following link “How to Create SCCM Windows 10 1709 Upgrade Task Sequence.” More details about the known issues of the 1710 preview version are available
Download SCCM ConfigMgr PREVIEW Version Configuration Manager ConfigMgr – Fig.3
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr. SCCM offers methods for upgrading existing Windows 10 devices to the newest version of Windows 10 1709, the Windows 10 Fall Creators Update.
One way to upgrade Windows 10 is using the “Windows 10 servicing” option in SCCM CB 1706. The other way is using the method I will explain in this post. This post will see “How to Create SCCM Windows 10 1709 In-Place Upgrade Task Sequence.”
Let’s understand what an SCCM Task Sequence is. A task sequence performs multiple steps or actions on a client computer at the command line level without user intervention.
Select the type of task sequence to create. A task sequence template (provided by default) is offered to upgrade the Windows 10 operating system to the latest version.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr
How to Create SCCM CB Task Sequence to Upgrade Windows 10 1709. There are methods in SCCM to upgrade existing Windows 10 devices to the newest version of Windows 10 1709.
The latest version of Windows 10 1709 is called Windows 10 Fall Creators Update. One way to upgrade Windows 10 is using the “Windows 10 servicing” option in SCCM CB 1706.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Video 1
How Do You Create a Windows 10 OS Upgrade Package in SCCM?
Before creating the Windows 10 upgrade task sequence, let’s complete the prerequisite: create a Windows 10 operating system upgrade package. Navigate via SCCM CB console—Software Library workspace, right-click the Operating System Upgrade Packages node, and select Add Operating System Upgrade Package.
Browse the data source for the operating system upgrade package. Specify the operating system upgrade package. Provide the Windows 10 1709 Enterprise x86 or x64 binary network share location. Select the Windows 10 architecture and the base language.
On the next page, enter the name of the Windows 10 1709 upgrade package. That’s it; you’re done.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Fig.1
How to Create Windows 10 in-place Upgrade Task Sequence
Navigate via SCCM CB console – Software Library workspace – right-click the Task Sequences node, then select Create Task Sequence. On the Create a new task sequence page, select Upgrade an operating system from the upgrade package and click Next.
Enter the name of the Task sequence—Windows 10 1709 Enterprise Upgrade. Upgrade the wizard’s Windows operating system page. As a first step, you must select the Windows 10 1709 upgrade package we created. The wizard will list all the available Windows 10 editions as part of the upgrade package.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Fig.2
Select the Windows 10 1709 Edition – Enterprise x64
With this upgrade task sequence, I plan to upgrade the Windows 10 Enterprise version to the latest one called Fall Creators Update (1709 – RS3). Also, you can enter licensing details if you have any. Otherwise, you can use the KMS server to activate Windows after the upgrade (Whenever required).
Select the Software Updates that Should Be Installed
If you already have an enterprise version of Windows 10 1703, it won’t ask for activation again (after the 1709 upgrade). In the “Include software updates” page of Create Task Sequence, we have 3 options.
Select the Software Updates that Should Be Installed
Details
Required for installation
Mandatory software updates only
Available for installation
All Software Updates
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Table 1
Required for installation – Mandatory software updates only
Available for installation – All Software Updates
Do not install any software updates.
On the next page, we can select the applications to be installed as part of the Windows 10 1709 upgrade process. I have added Mozilla Forex to the Windows 10 1709 in-place upgrade.
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Fig.3
Overview SCCM CB Windows 10 in-Place Upgrade Task Sequence
There are 5 groups in the Windows 10 Enterprise 1709 Upgrade task sequence. Prepare for Upgrade is the first stage, where it will analyze the machine to determine whether it’s eligible for a Windows 10 1709 upgrade. Enough disk space and memory are available on the device.
Upgrade the operating system is the task sequence group where the actual in-place upgrade of Windows 10 1709 will happen. Post-installation is the stage where we set the installation of the packages or applications.
One group missing in the video tutorial is the Software Update group or task. The last and final group of this Windows 10 1709 upgrade task sequence is for rollback. This action will take place when the upgrade is failed.
Success: The task sequence has been created successfully.
Success: Create a new task sequence – • Name: Windows 10 Enterprise Upgrade
Success: Upgrade the Windows operating system – • Installation source media: Win10 en-US• Edition index: 3
Success: Include software updates• Install software updates: Do not install any software updates
Success: Install applications• Install the application: Mozilla Firefox (ach)• If an application installation fails, continue installing other applications in the list: No
How to Create SCCM Windows 10 Upgrade Task Sequence Configuration Manager ConfigMgr – Fig.4
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager. The SCCM CB standalone media wizard helps the admin create an ISO file (.iso). This ISO file helps build machines that are not connected to the network.
Standalone media in SCCM contains everything required to deploy the operating system on a computer. The machine should not be connected to an SCCM CB site or the network. This post will see whether we could “Install Dynamic Applications using SCCM CB Full Standalone Media.”
This post will also discuss creating SCCM CB offline standalone media with applications, collection variables, etc.
SCCM Standalone media contains everything required to build a machine’s operating system. However, the applications and packages referenced in the Task Sequence will not be automatically installed as part of this offline media process.
Check Out the Offline Build Standalone Media Video – Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager
Is this true for all the SCCM CB builds? Yes, indeed, the dynamic apps or packages won’t get installed automatically. But, we have a user voice item to include these features in offline standalone media. You can check out the User Voice item from here.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Video 1
As you can see in the above picture, development work has already started on this User Voice item. The latest version of SCCM CB 1709 does not include the installation of dynamic applications and packages. However, the SCCM CB standalone media wizard can consist of the content of dynamic applications referenced in the Task Sequence.
We can use SCCM SDK to build offline standalone media solutions and include dynamic application installation features as part of SCCM standalone media. But it would be great to have this option as a native feature of SCCM.
I think the apps/packages referenced in the original task sequence will get installed automatically.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Fig.1
How to Create SCCM CB Standalone Media?
Navigate via the SCCM Console Software Library work space—Operating Systems—Task Sequences. Click on the “Create Task Sequence Media” button from the ribbon menu of the SCCM CB console. The Create Task Sequence Wizard has four media creation options. This post will show how to create standalone media for SCCM CB.
Create SCCM CB Standalone Media
Details
Standalone Media
Creates media used to deploy operating systems without network access.
Bootable Media
Creates media to deploy operating systems using SCCM infra connectivity. This media does not contain OS images and applications.
Capture media
Creates media used to capture operating system deployment images from a reference computer.
Prestaged media
Prestaged media creates a file, including an operating system image, to be prestaged on a new hard drive.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Table 1
Standalone Media – Creates media used to deploy operating systems without network access.
Bootable media—Creates media to deploy operating systems using SCCM infra connectivity. This media does not contain OS images and applications.
Capture Media – Creates media used to capture operating system deployment images from a reference computer.
Prestaged Media creates a file, including an operating system image, to be prestaged on a new hard drive.
More details are available in the video tutorial here Explained above.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Fig.2
Specify the media type – The media type page has two options. One for removal of media like a USB drive. Another option is a CD/DVD set. You can also specify the media size – 4 GB, Unlimited, etc… You can select the path where you want to save the ISO file of standalone media.
Select security settings for the media—To increase safety and avoid accidental OS re-imaging; we can set a password for standalone media and select an expiration date.
Select the Task Sequence, which will help rebuild the machine. This page will show you the details of the Task Sequence content. On the next page, Select application content to add. You can select the apps you want to be part of Offline standalone media. The content of the selected apps and packages will be available for manual installation on the device.
On the Distribution Points page, specify the distribution points containing the content required by the task sequence, then click Next. You must have Read access rights to the content library on the distribution points. Make sure these contents are distributed to the DP. Otherwise, you won’t be able to create SCCM CB Standalone media.
More Details are Available in the Video Tutorial here
Specify the variables that the task sequence uses to deploy the operating system. This will help customize the Operating system during the build. It could also help with installing the language pack, setting up timezones and regional settings, etc.
You will also have the option to specify any prestart commands you want to run before the task sequence to SCCM standalone media.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Fig.3
How to Troubleshoot SCCM Standalone Media Creation Issues?
Most offline media issues are WMI-related or memory-related. If the machine where you are trying to create offline media doesn’t have enough memory, you could get errors.
Install Dynamic Applications using SCCM CB Full Standalone Media Configuration Manager – Fig.4
Conclusion
Installation of Dynamic Applications using standalone offline media is not supported with SCCM CB 1709. The content of these apps is part of standalone media, which helps to install the apps manually on the machine. I hope SCCM PG will include this feature to improve the experience for SCCM admins/operation teams.
Sample SCCM CB Standalone
Also, we can have a look at the log fileCreateTsMedia.log. This log file will be located in the same location where your SCCM console is installed. C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog.
Success: Task sequence media information Success: Task sequence media information• Media type: CD/DVD set• Media size: Unlimited• Output path: \\SCCMTP1\Sources\Windows 10\Offline Media\Win10 Offline Media 1709 Copy1.iso• Allow unattended operating system deployment: No• Protect media with password: No• Task sequence: TP10001B-Windows 10 CYOD• Prestart command: No• Distribution point(s): SCCMTP1.INTUNE.COM• Total size of media content, MB: 4631• SHA256 checksums: \\SCCMTP1\Sources\Windows 10\Offline Media\Win10 Offline Media 1709 Copy1.iso403CB70C4620245E85ACFA735D0C2B64C90DC3AAEC3792A55D8E523039377EC0 Success: Applications:• Mozilla Firefox (ach) Success: Packages:• Microsoft Corporation User State Migration Tool for Windows 10.0.15063.0• Configuration Manager Client Package.
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr. Many organizations are looking for more simplified management options for Windows devices.
There are two ways of managing: the traditional way of control and the Modern way of governance. Both are explained in detail below.
They also want an easier transition from SCCM and Domain Join devices (Traditional) to a modern management approach with Intune and Azure AD Join devices (Modern). This post will show How to set up SCCM CB and InTune Co-Management.
In this video, you will learn all the details about setting up SCCM CB Intune Co-Management. Below is more information about the SCCM CB 1709 upgrade and Co-Management setup viaVideo Tutorial.
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Video 1
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr
The co-management option is available only on a Preview release of SCCM CB 1709. I don’t know whether it will make it to the SCCM CB 1710 Production release in a few months. However, Co-Management will be available in the SCCM CB 1710 production release.
Modern IT
Multiple Devices
User and Business Owned
Cloud Managed & SaaS Apps
Automated
Proactive
Self Service
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Table 1
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Fig.1
What is Co-Management?
In simple terms, SCCM CB co-management is a dual management capability offered for Windows 10 1709 (Fall Creators Update) devices. InTune and SCCM can manage Windows 10 1709 devices simultaneously.
For example, eligible Windows 10 devices will be managed via the SCCM client, and the Intune MDM channel will handle other workloads. The section below this post provides more details about the Workloads.
This co-management is only available for the Intune subscriptions; set INTUNE as MDM authority.
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Fig.2
You might wonder how we can handle policy conflicts in the SCCMCo-Management scenario. Yeah, disputes regarding configuration/compliance policies will be controlled via Co-Management Configuration policies in SCCM CB.
You can select which workloads can be managed via Intune. All other SCCM workloads will be handled through the SCCM management method.
Where Can We Set up SCCM Co-Management Policies?
Install or Upgrade SCCM CB 1709 or a later version of SCCM. Navigate the SCCM CB 1709 (or later) console via \Administration\ Overview\ Cloud Services\Co-management. Click on the button “Configure Co-Management” to create Co-management Production or Co-Management Pilot policies.
There are 2 staging options available in SCCM CB co-management. Following are the 2 options:-
Co-Management Production Policies (CoMgmtSettingsProd)
Co-Management Pilot Policies (CoMgmtSettingsPilot)
Configure Roll-out Groups – Pilot Collection
Configuring co-management will only be enabled for a selected pilot collection. Selected Window 10 1709 or later devices will be in the pilot group for Co-Management. This pilot group of this collection can be used for a staged co-management roll-out.
We can initiate automatic enrollment or move workloads to InTune for devices in the pilot group before you roll out co-management to all supported Windows 10 devices in your production environment.
Configure Co-management for Production Collection with Exclusion Collection
Configure co-management policy for production. You may select an exclusion group that will be excluded from co-management in your production environment. Exclusion groups can be any collection of Windows 10 devices.
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Fig.3
How Can SCCM Co-Management for SCCM Clients and Intune Managed Devices be Enabled?
There are two ways to enable SCCM co-management for Windows 10 1709 devices.
Enable Co-management for SCCM Clients
Enable Co-management for Intune-managed devices
Enable Co-management for SCCM Clients
You must select the following option to enable co-management for SCCM-managed devices with Intune: To enable co-management for devices managed by SCCM and configured, select ALL or Pilot from the drop-down menu to manage all/pilot SCCM clients via Intune.
Enable Co-management for Intune Managed Devices
You must create an Intune application to enable co-management for Intune-managed devices with SCCM. This application will install the SCCM client onto Intune-managed devices.
The SCCM team provided a sample command line to install the SCCM client. Following is the sample command line provided in the wizard
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Fig.4
What are SCCM Co-Management Workloads?
SCCM Co-Management workloads are functionalities/features of device management. For example, the Compliance policies, Configuration Policies, Software Updates, Resource Access policies (WiFi Profiles/VPN Profiles, etc..), Application deployment, etc., are co-management workloads.
How Do You Configure/Select Workloads for Co-management?
SCCM continues to manage all device management workload functionalities even after enabling the co-management option. When you decide you are ready for co-management, you can use Intune to manage available workloads.
Co-Management Configuration Wizard provides the ability to select these functionalities /features. Following are the 3 features enabled for co-management
Compliance Policies (this will work with Conditional Access)
Resource Access Policies (WiFi, SCEP, etc..Anything comes under the SCCM console Company Resource Access node)
Windows Update Policies (Patching without on-prem WSUS/SUP)
For Windows 10 devices that are in a co-management state. You can have Microsoft Intune start managing different workloads/features. Choose pilot Intune to have Microsoft Intune start managing different workloads.
Choose Pilot Intune to have Intune manage the workloads for only clients in the pilot groups. If you want to manage these workloads with SCCM, select ConfigMgr/SCCM. If you’re going to manage these workloads with Intune, select Intune.
How to Setup SCCM CB Intune Co-Management Configuration Manager ConfigMgr – Fig.5
Resources
Co-management for Windows 10 devices – SCCM 1709 Preview – here
Migrate hybrid MDM users and devices to Intune standalone – here
Microsoft 365 and SCCM Windows 10 Co-Management – here
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
SCCM’s latest version (SCCM 1902) introduced many new ways to manage Office 365 ProPlus updates better. SCCM uses the existing Software Update workflow to update Office 365 ProPlus update management.
SCCM’s latest version has a unique dashboard for Office 365 Client management. This dashboard can be used to manage your organization’s Office 365 ProPlus apps.
This post will show how to Deploy and Install Office 365 Software Updates with the SCCM Automatic Deployment Rule (ADR). The video tutorial provides more details.
How to Deploy and Install Office 365 Software Updates with SCCM CB ADR
SCCM has the ability to manage Office 365 client updates and patching. SCCM uses the Software Update workflow to update using the Software Update management workflow. Configuration Manager can update Office 365 ProPlus, Visio Pro for Office 365, Project Online Desktop Client, and Office 365 Business.
SCCM to Deploy and Install Office 365 ProPlus Updates – Video 1
What is the High-level Workflow of O365 ProPlus Updates Deployment via SCCM?
SCCM Office 365 ProPlus Automatic Deployment rule can create an end-to-end workflow. This will help us to automate Office 365 app installation and management. I have another post on How to Deploy and Install Office 365 Applications via SCCM CB.
1. Office publishes Office 365 app update metadata to Microsoft Update service 2. SCCM gets the notification about the updates from Microsoft update services via scheduled WSUS sync 3. SCCM refers to office CDN for file lists and downloads required files for on-prem SCCM server sharing. This can be done using SCCM ADR (Automatic Deployment Rule) or a normal Software update process. 4. SCCM Clients get a new policy to deploy the latest updates for Office 365 apps as per the scheduled deployment
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.1
What are the Prerequisites to Managing Office 365 ProPlus Updates via SCCM CB?
There are 3 prerequisites to manage Office 365 updates/patches via SCCM CB at a high level. I assume all the devices are managed via SCCM CB and all the SCCM client prerequisites have already been met.
#1 and #2 – Enable Classification and Product for Office 365 Updates
We must enable the following classification and product to manage Office 365 updates via SCCM CB. Navigate via SCCM console – \Administration\Overview\Site Configuration\Sites. Click on Settings – Configure Site Components – Software Update point component – Properties. Go to the Classification tab and enable Updates.
Once updates from the classification tab are enabled (to support Office 365 updates), you can go to the Products tab to enable “Office 365 Client“. More details are available in the video tutorial here.
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.2
#3 – Enable Client Settings for Office 365 Updates
We must enable the following settings to manage Office 365 updates via SCCM CB. Navigate the SCCM console via \Administration\Overview\Client Settings. Go to Client Settings – Software Updates tab – Enable Management of Office 365 Clients = YES.
How to Create Automatic Deployment Rule for Office 365 ProPlus Updates?
Use Automatic Deployment Rule Wizard (from Office 365 Client Management node) to automate Office 365 application updates/patches through SCCM CB. Using ADR, you can eliminate the repetitive process of creating a Software Update Group, Packages, and Deployments.
You can automatically deploy software updates by adding new ones to an update group associated with an active deployment. You can use an automatic deployment rule (ADR) to create a new deployment for complex scenarios.
Be very careful before creating and implementing SCCM ADR. I recommend testing ADR in a pre-prod environment before implementing it in production. The video tutorial here has end-to-end details about this process.
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.3
What Should Be the Search Criteria for Office 365 ProPlus Updates?
Search Criteria are the brain of SCCM ADR. When selecting the criteria to add new updates to the existing Software Updates group, it would be best to be careful. In this post, I said the search criteria should include Monthly channel updates for the last month.
Software updates that meet the specified criteria are added to the associated software update group. I have included details of the requirements that I selected below.
Date Released or Revised ==> Last Month
Product ==> Office 365 Client
Title ==> Update – Monthly Channel
Other Office 365 Update Channels as well in the Criteria
Monthly Channel (formerly Current Channel)
Monthly Channel (Targeted)
Semi-Annual Channel (Differed Channel)
Semi-Annual Targeted (formerly First Release for Deferred Channel)
SCCM to Deploy and Install Office 365 ProPlus Updates – Table 1
Remember to hit the PREVIEW button to check whether you get the expected search results. The video tutorial provides more details. Specify the settings for the Automatic Deployment Rule, automatically deploy all software updates found, and approve any license agreement.
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.4
Specify the Recurring Schedule for the Office 365 ProPlus Updates ADR
You can select “Run the rule after any software update point synchronization” or SCCM CB ADR according to your schedule.
Configure Schedule Details for the Deployment
In this ADR wizard, you need to confirm whether the ADR rule for the Office 365 App update has been completed. The package has been deployed to DPs, the deployment has been scheduled, etc. I selected all the default settings.
Specify the scheduled deployment time. There are 2 options for setting the deployment time. The time can be the client’s local or Universal Coordinated Time (UTC). The default setting is Local client Time. The video tutorial provides more details.
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.5
Configure Office 365 ProPlus Update Available Time
Specify when software updates should be available for users in the Software Center. Once this ADR rule is run, software updates will be distributed to the DP servers.
Office 365 ProPlus Updates are available to install as soon as possible or per the schedule. I usually set this as ASAP so the user can go into the SCCM CB software center and run.
Installation Deadline for SCCM CB Office 365 ProPlus Updates
In this section of the ADR wizard, you can specify a deadline for required Office 365 updates. The deadline is determined by adding the deadline time to the installation time.
When the deadline is reached, the required Office 365 software updates will be installed on the device. I have selected the Deadline of 7 days from the deployment available time. You can also have a deadline as soon as possible, which will help you deploy apps as quickly as possible on the device.
You have another granular option while setting up the installation deadline. According to user preferences, this deployment is delayed up to the grace period defined in client settings.
More details are available in the video tutorial here.
User Experience – SCCM ADR for Office 365 ProPlus Updates
The default user experience behavior is Hide in Software Center and All notifications. There are loads of granularity options in setting up the deadline behaviour, Device restart behaviour, Write filter handling for Windows Embedded (IoT) devices, and Software updates deployment re-evaluation behaviour upon restart.
If any Office 365 software update in this deployment requires a system restart, run the updates deployment evaluation cycle after the restart.
SCCM to Deploy and Install Office 365 ProPlus Updates – Fig.6
As you can see in the above picture, Office 365 updates are stuck at 50% downloading on Windows 10 machines. I couldn’t find a solution while writing this post. I will update this post whenever I have an update on the resolution or fix for this issue.
References
Ignite Video Deploy Microsoft Office 365 Client using SCCM – here
Manage updates to Office 365 ProPlus with SCCM – here
Troubleshooting Office 365 ProPlus patching through SCCM – here
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
About the Author: Vidya is a computer enthusiast. She is here to share quick tips and tricks with Windows 11 or Windows 10 users. She loves writing about Windows 11 and related technologies. She is also keen to find solutions and write about day-to-day tech problems.
Let’s find the best way to Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM. This is the best and easiest method to deploy and install all the Microsoft 365 apps to Windows 11 or 10 devices.
The latest version of SCCM makes creating Office 365 ProPlus client packages accessible. In this post, you will learn how to create an Office 365 ProPlus client application. I have already created a video tutorial to explain the wizard’s process (Install Office 365 ProPlus).
SCCM Learn How to Deploy Install Office 365 ProPlus Applications Configuration Manager ConfigMgr. We can deploy Office 365 ProPlus apps (Word, Excel, PowerPoint, Outlook, etc..) to clients using SCCM CB.
You can start the Office 365 ProPlus application Installer from SCCM version 1702, starting from the Office 365 ProPlus Client Management dashboard.
The new feature will let us configure Office 365 ProPlus installation settings, download files from Office Content Delivery Networks (CDNs), and deploy the files as an application.
What is Office 365 ProPlus Microsoft 365 Apps Client Installer?
The Office 365 client installer is nothing but an installer for Office 365 client applications. Is that a bit clearer? So, which are those Office 365 Client applications? Word, Excel, PowerPoint, OneDrive, Outlook, etc.
OFFICE 365 ProPlus or Microsoft 365 Apps Client installer will help install all these applications to end-user devices like Windows 11, Windows 10, Windows 8, and Windows 7.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM
Start the Office 365 client installation wizard from the SCCM console – \SoftwareLibrary\Overview\Office 365 Client Management dashboard. Click on the + Office 365 Installer to launch the Office 365 installer from the SCCM CB console.
Office 365 client installation files will be downloaded to this location if they do not already exist. Without the internet, you can’t proceed to the 2nd page of this wizard. This is in case you have not downloaded the Office 365 configuration files.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.1
You can set up all the client settings using the “Import Client settings” option in Office 365 Client Installation Wizard. You can import the configuration.xml file to automatically configure all the Word, Excel, PowerPoint, Outlook settings, etc.
Otherwise, you can select the option to manually configure all the settings via the Office 365 or Microsoft 365 apps installation wizard.
Select the List of Office 365 Applications You Want to Install
Select the Office Suite as part of the O365or Microsoft 365 apps installation wizard. There are four office suites available as part of the installation wizard.
Four Office Suites Available as Part of the Installation Wizard
Microsoft 365 Business Basic
Microsoft 365 Business Standard.
Microsoft 365 Business Premium
Microsoft 365 Apps
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Table 1
You will also get an option to select Office 365 ProPlus or Microsoft 365 Applications, including installation. I don’t want to install OneDrive for Business (Groove) application as it’s the old sync client.
The rest of the apps will be installed on the Windows device based on the application selected from the wizard.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.2
Access
Excel
OneDrive for Business
OneNote
Outlook
PowerPoint
Publisher
Skype for Business
Word
You have an option to select additional office products like Visio and Project. For those two products, there is a special licensing option.
Those license options are available in Office 365 Subscription Standard Edition—Volume License and Professional Edition —Volume License. The video tutorial provides more details.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.3
Select Office 365 ProPlus Microsoft 365 Apps Architecture using SCCM
Select the Architecture for Office 365 applications like Word, Excel, PowerPoint, etc. There are two versions: 32bit Vs. 64bit. There are 4 update channels available in the SCCM Office 365 client to install the wizard.
However, these updated models have recently changed. The following are the latest Office365 update models: Monthly Channel (formerly Current Channel), Monthly Channel (Targeted), Semi-Annual Channel (Differed Channel), and Semi-Annual Targeted (formerly First Release for Deferred Channel).
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Video 1
You can select different languages for Office 365 applications. You can choose the language of applications depending on your preference or region. This wizard will help you download the languages that will be downloaded for Office 365.
You can also configure it to “Accept EULA” and auto-activate the applications. You can also have Pin Icons in the Windows 8 and Windows 7 taskbar. The pin option is not applicable for Windows 10 devices. More details are provided in the video tutorial here.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.4
Deployment and Scheduling Options for Office 365 ProPlus Microsoft 365 Apps using SCCM
Deployment options/settings are also part of the Office 365 Client Installation Wizard. You must select the collection you want to deploy the Office 365 client on your SCCM CB environment. Select the content locations or DPs from the Content page.
There are two Office 365 client installation options: mandatory and Optional deployments. You can schedule the deployment according to your organization’s requirements.
General • Collection: All Desktop and Server Clients • Use default distribution point groups associated with this collection: False • Automatically distribute content for dependencies: True
Success: Content (1): • SCCMTP1.INTUNE.COM
Deployment Settings • Action: Install • Purpose: Required • Pre-deploy software to the user’s primary device: False • Send wake-up packets: False • Allow clients to use a metered Internet connection to download content: False
Scheduling • Time based on: UTC • Available Time: As soon as possible • Deadline Time: Disabled • Delayed enforcement on deployment Disabled
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.5
End-User Experience of Office 365 App on Windows 10 Devices
You can see the Office 365 app listed in the Software Center. It was a mandatory deployment and was automatically installed on Windows 10.
All O365 Applications were installed on Windows 10 or Windows 11 Devices. The Office365 update channel is the Current Channel (Monthly channel).
Excel, PowerPoint, Outlook, etc., apps are installed successfully on Windows 10 or 11 devices. However, the Windows 10 device had no internet connection, so the activation didn’t happen automatically.
The License will automatically be assigned according to the user’s subscription. After the installation, you can launch all the applications (Word, Excel, PowerPoint, OneDrive, etc.) from your Windows 10 machine.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.6
The Office 365 Client Management dashboard details the number of managed O365 clients in your SCCM CB hierarchy. The video tutorial provides more details on creating an Office 365 ADR and deploying Office 365 Software Updates.
Example of Office 365 Microsoft 365 Client Installation Wizard Configuration –
Now, let’s learn how to Deploy and Install Office 365 ProPlus or Microsoft 365 Apps using SCCM or Configuration Manager.
User Experience • User notifications: Display in the Software Center and show all notifications • Ignore Maintenance Windows: False • System restart (if required to complete the installation): False • Commit changes at the deadline or during a maintenance win&dow (requires restarts): True
Alerts • Enable System Center Operations Manager maintenance mode: False • Generate System Center Operations Manager alert when a software installation fails: False • Create a deployment alert when the threshold is lower than the following: False • Create a deployment alert when the threshold is higher than the following: False
Sample Configuration.XML file configuration for Office 365
There are a few new application installations, maintenance, and removal technologies. In this post, we are going to see more aboutClick-to-Run technologies.
Click-to-Run is an alternative to the traditional Windows Installer-based (MSI) method. It uses virtualization technology to run an Office product in a self-contained environment. Click-to-run virtualization capabilities are taken from APP-V.
The UWP application comes with various installation options, the most prominent of which are web-based and Windows store-based. Both use the App Streaming Install method to install the application. Office has a UWP app version, which will be available in the Microsoft store.
UWP is dead? This was one of the news spread on Twitter. And the reason for that Twitter news was because of the information about Progressive Web Applications (PWA).
PWA are Web pages designed to work as applications. PWA is supported by Chrome, Edge, and Safari (Apple has also started working on it). PWA is one of the new app technology which I’m excited about.
Office Click-to-Run Installation Options with SCCM
This click-to-run installation technology used in SCCM CB is an alternative to traditional MSI installation. Click-to-run Office client installation is independent of SCCM SUP and WSUS software updates.
As mentioned above, the SCCM console requires an internet connection to download the latest updates from Office CDN. More details about creating a Click to Run Office App in SCCM are available.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – video 2
Office updates via SCCM SUP and WSUS depend on Click-to-Run client installations. If the office is installed using a click to run the installation, you can have office updates or upgrades through SCCM/SUP.
#1 – You should have the latest version of SCCM Current Branch to get a better experience and integration of Office 365 client package creation and Office 365 patches/updates.
#2—You must build two Office 365 ProPlus installation packages in SCCM. One is a Semi-Annual channel, and the other is a Semi-Annual Channel (Targeted).
#3 – Deploy to two deployment groups: a pilot group that receives the Semi-Annual Channel (Targeted) and a broad group that receives the Semi-Annual Channel.
#1 – You should have SCCM 1806 or later to create Office 365 proplus package with an office customization tool. If you have not upgraded to the 1806 version, I recommend reading my previous post, “How to Deploy and Install Office 365 Applications via SCCM CB“.
#2 – The SCCM client Application installation wizard has integrated with the Office Customization Tool. This tool needs an internet connection on the machine where the console is running. This office customization tool renders the online website in the background to create a Configuration.XML file.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Fig.7
#3 – You should have requiredRBAC permissions on the SCCM console to perform Office 365 ProPlus client package creation.
Video Tutorial – Office 365 ProPlus Client Package Creation
The video below provides more details about creating the Office 365 ProPlus package. You can also learn SCCM, Intune, and other device management topics via videos from my new Video Blog website,https://howtomanagedevices.com/.
Deploy Office 365 ProPlus Microsoft 365 Apps using SCCM – Video 3
How to Create Office 365 ProPlus Client Package (Install Office 365 ProPlus)
The following steps will help you create your organisation’s Office 365 Proplus client package. As recommended above, it would be great to create two packages (Semi-Annual and Semi-Annual Targeted) for the Office 365 ProPlus client package.
Launch the SCCM console from an internet-connected machine
Navigate to \SoftwareLibrary\Overview\Office 365 Client Management dashboard
Click on the + Office 365 Installer from the Office 365 Client Management Dashboard
Give the NAME of the Office 365 ProPlus Client Package and the Description of the package
Browse to a location mainly on the file server or SCCM server package source folder
Click on the Next button
This is the primary step in the Office 365 proplus client configuration. Click on the Office Customization tool (More details about the tool are in the section below this post) to customize and import your XML to the SCCM application engine.
As you can see in the screenshot above, you must complete all the above sections to create a configuration.xml file for the Office 365 proplus client package.
Ensure you have a tick mark symbol for all the sections in the Office Customization tool; otherwise, it won’t be able to create the XML file. The video tutorial above provides more details.
In the General section, you need to give a name and Organization details and click the Next button to go to the next section.
You can select the Office 365 product and architecture (x64) you want to deploy in the Product and Releases section. I selected Office ProPlus and Clicked on the Add button. You must also choose which update channel and Version you wish to use for your Office 365 clients. I selected the Semi-Anual Channel for updates.
Select the Language of the Office 365 ProPlus Client you want to deploy. You also need to select the installation options, such as shortcut behavior. Click on NEXT to proceed to the next section of the wizard.
Select the upgrade options from the Update and Upgrade section of the office customization tool. I have enabled the toggle for the Upgrade Office Click-to-run products. Also allows options to Uninstall any MSI versions of the office including visio and project. Click on NEXT.
Complete the Licensing and Activation settings and click on NEXT.
Application Preferences gives IT pros a wide range of customization options for each office product, such as Word and Excel.
Click the Finish button to complete and Review the Office 365 ProPlus client.
Click on the SUBMIT button to IMPORT configuration.xml to the application package.
Click the NEXT, NEXT, NEXT, and CLOSE buttons to finish the Microsoft Office 365 Client Installation Wizard. This wizard takes 30-40 minutes to complete depending on the internet connection.
Deploy this Office 365 ProPlus client package to test machines.
Learn More about The Office Customization Tool
The Office Customization Tool for creating a configuration.XML file that controls Office 365 Proplus client behavior. This tool is an Azure-based cloud service that allows you to create XML configuration files that are used with the Office Deployment Tool. Install Office 365 ProPlus.
Previously, you needed to create the configuration files in Notepad or another text editor. The Office Customization Tool makes this part of the deployment process more accessible and less likely to introduce errors. Now, this tool is also integrated with SCCM version 1806 or later.
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager. SCUP 2017 has four 3rd party software update catalogs.
Dell, HP, Fujitsu, and Adobe are the four third-party software update catalog providers in the SCUP 2017 Preview version.
In previous blog posts and video tutorials, I explained the installation, configuration, and integration process of SCUP with SCCM.
This post will show how “How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB“. We must follow the same process for publishing HP and Fujitsu software updates.
How to Publish Dell BIOS Firmware Updates Via SCUP and SCCM CB
Dell Software updates Catalog (Bios, Drivers and Applications, Firmware) are added to the SCUP console. Click on the Dell Folder and expand the Dell folder to see subfolders.
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Video 1
How to Add Dell Software Update Catalog to SCUP
Open the SCUP 2017 console. Navigate to “Update Workspace—Overview” and click Add Partner Software Updates catalogs. Select Dell and click on the Add button.
This will add the Dell updates to the SCUP database. Dell updates include Dell Bios, Drivers, Applications, and Firmware updates.
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Fig.1
How Do you Publish Dell Software Updates to SCUP, WSUS, and SCCM CB?
Dell Software updates Catalog (Bios, Drivers and Applications, Firmware) are added to the SCUP console. Click on Dell Folder. Expand the Dell folder to see subfolders. Select the updates from the right pane of the SCUP console that you want to publish to SCCM CB.
Specify the publish option—There are three options while posting updates: Automatic, Full content, and Metadata Only. I usually recommend selecting the Automatic option. The reasons for choosing the Automatic option are given below. This has been shown in the videohere.
Click Automatic to all updates publisher to query SCCM to determine whether the selected software updates are published with full content or only metadata.
In this mode, software updates are only published when they meet the client request count and package source size thresholds specified on the SCCM server page of the Options dialog box. Automatic is available only when SCCM integration is selected on the SCCM server page.
Select the checkbox at the bottom of the SCUP publish wizard. When published software updates have not changed, but their certificate has changed, this checkbox will sign all software updates with a new publishing certificate.
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Fig.2
How to Select Dell Products from SUP Component Properties in SCCM?How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr
Once the updates are published from the SCUP console, you can go to the SCCM CB console to configure the rest. Navigate SCCM console – \Administration\Overview\Site Configuration\Sites.
Click on Settings—Configure Site Components—Software Update point component—Properties. Go to the Products tab and Select Dell, Bios, Drivers and Applications, and Firmware. This is the same thing I showed in the video.
Dell
Bios
Drivers and Applications
Firmware
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Table 1
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Fig.3
Once the appropriate products are selected, navigate \Software Library\ Overview\Software Updates in the SCCM CB console. Right-click on the Software Updates node & select Synchronize Software Updates.
This will help sync and get the Dell updates to the SCCM CB console. WsyncMgr.log will provide you with the details about Dell updates.
How to Deploy Dell Updates via the Software Updates Deployment Method?
As shown in the video, select all the Dell Bios and Firmware updates you want to deploy from the All Software Updates node. Once selected, right-click those updates and click on Deploy.
How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr – Fig.4
For Dell software updates, you must provide the Deployment name and software update group name. On the next screen, select the collection name from the list.
The members of that collection will get the Dell software updates deployment. Schedule the deployment and make sure you set a good user experience.
Also, provide the new Dell software update package name and the shared folder location to store the Dell software updates. You also need to select the DPs to distribute this package.
Example of the Dell Software Update Deployment via SCUP and SCCM – How to Deploy Dell Bios Firmware Updates Via SCUP and SCCM CB Configuration Manager ConfigMgr
It would be best to have an internet connection to the server to download the Dell updated from Dell. Otherwise, you must have already downloaded the binaries from Dell and stored them in a shared location, as shown in the video here.
Do you want to download these Dell software updates in different languages? If so, you can select other languages on the Language Selection page.
• Dell Latitude 10 ST2 System BIOS,A09 0XM7C(Article ID) • Dell Latitude 10 ST2e System BIOS,A07 T47W6(Article ID) • Dell Latitude 12 Rugged Extreme 7204 System BIOS,A11 J6PG2(Article ID) • Dell Latitude 12 Rugged Tablet,A15 X2GXX(Article ID) • Dell Latitude 3180/3189 System BIOS,1.1.1 M6HF7(Article ID) • Dell Latitude 3330 System BIOS,A08 800F5(Article ID) • Dell Latitude 3340 System BIOS,A13 48CH6(Article ID) • Dell Latitude 3350 System BIOS,A09 0468G(Article ID) Success: General: • Deployment Name: 3rd Party Updates SCUP - Dell Software Updates • Collection: All Desktop and Server Clients Deployment Settings: • Send wake-up packets: No • Verbosity Level: Only success and error messages Scheduling: • Deployment schedules will be based on: Client local time • Available to target computers: 23-09-2017 07:25:00 • Deadline for software update installation: 30-09-2017 07:23:00 • Delayed enforcement on deployment: False User Experience: • User Notifications: Display in Software Center and show all notifications • Install software updates outside the maintenance window when deadline is reached: No • Restart system outside the maintenance window when deadline is reached: Suppressed • If a restart is required it will be: Allowed • Commit changes at deadline or during a maintenance window (requires restarts): Yes • If any update in this deployment requires a system restart, run updates deployment evaluation cycle after restart: No Alerts: • On software update installation error generate a Window Event: No • Disable Window Event while software updates install: No Download Settings: • Computers can retrieve content from remote distribution points: No • Download and install software updates from the fallback content source location: Yes Package: Success: The software updates were placed in a new package: • 3rd Party Updates SCUP - Dell Software Updates Success: Content (1): • SCCMTP1.INTUNE.COM Software updates downloaded from the internet Success: Dell Latitude 10 ST2 System BIOS,A09 Success: Dell Latitude 10 ST2e System BIOS,A07 Success: Dell Latitude 12 Rugged Extreme 7204 System BIOS,A11 Success: Dell Latitude 12 Rugged Tablet,A15 Success: Dell Latitude 3180/3189 System BIOS,1.1.1 Success: Dell Latitude 3330 System BIOS,A08 Success: Dell Latitude 3340 System BIOS,A13 Success: Dell Latitude 3350 System BIOS,A09 Language Selection: English
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
Let’s discuss the SCCM Management Insights Configuration Manager ConfigMgr Details. SCCM team introduced a new feature called Management Insights with SCCM CB 1708 preview version.
I mentioned the management insights feature in my previous post, “SCCM CB 1708 Preview Upgrade Video Guide and New Features”. In this post, we will look at the details of management insights, and you will get some ideas about SCCM CB Management insights. Video tutorial here.
Management Insights will help you gain valuable insights into the current state of the SCCM CB environment based on data analysis in the site database.
One of the scenarios in the management insight would be useful for better understanding your environment and taking action based on that insight.
I hope the SCCM team will include loads of other data or details into management insights in future releases of SCCM CB. You don’t have to dig into the SQL Database and run SQL queries to find out these details anymore!
Where Can You Find the Node for SCCM CB Management Insights?
Navigate through SCCM CB 1708 preview console – \Administration\Overview\Management Insights\All Insights. I have explained this in the video tutorial here.
How Do We Find Applications without Deployments in the SCCM CB Environment?
You can find the details or list of applications without deployments from the SCCM CB console. This is under \Administration\Overview\Management Insights\All Insights – Application without deployments node.
I have explained the scenario in the video tutorial here. From the Application without the deployment node, you will get an option to delete the application directly.
You don’t have to go to the Software Library—Applications node to delete a particular application without deployment.
The last run time tab will tell you the last time the rule ran against your SCCM CB site database. To simplify the list of applications, we can find the list of undeployed applications.
How to Find Out Applications without Deployments in the SCCM CB Environment?
How Do You Find Empty Collections in the SCCM CB Environment?
The details or list of Emptycollections can be found in the SCCM CB console. This is beneficial information, as you no longer need to dig into SQL DB and run SQL queries to find these details.
This is under \Administration\Overview\Management Insights\All Insights – EMPTY Collections node.
In the following screenshot, you can see the list of empty collections of the SCCM CB environment from the management insights node in the SCCM console.
You may also delete the empty collections from the “Management Insights – All Insights – Empty Collections” node.
You can Right-click on the empty collection and delete it. Otherwise, you can select the collection you want to delete and click the “Delete” button from the ribbon menu of the SCCM CB console. More details in the video tutorial are here.
Is SCCM CB Management Insights not Working as Expected?
Check out the log SMS_CLOUDCONNECTION.log and look for any error in the log file. Registry Key details of SCCM CB management insights component:- HKEY_LOCAL_ MACHINE \SOFTWARE \Microsoft\SMS\Components\SMS_CLOUDCONNECTION.
ERROR: Found exception System.IO.FileLoadException: Could not load file or assembly 'Microsoft.ConfigurationManager.ManagementInsights.MIWorker, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)~~File name: 'Microsoft.ConfigurationManager.ManagementInsights.MIWorker, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)~~The Zone of the assembly that failed was:~~MyComputer~~ at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)~~ at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)~~ at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)~~ at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)~~ at System.Reflection.Assembly.Load(String assemblyString)~~ at Microsoft.ConfigurationManager.TaskExecutionManager.TaskExecution.InvokeWorker(String assemblyToLoad, String typeToLoad, String componentName)
What is SCCM CB Management Insights – Find Out Unused Collections and Applications
The Management Insights node in the SCCM CB console. This feature will help you maintain SCCM infra. At the moment, it will help you get the details of EMPTY collections and Applications without deployments.
SCCM Management Insights Configuration Manager ConfigMgr Details – Video 1
References
SCCM CB 1708 Preview Upgrade Video Guide and New Features – Here
Update 1708 for Configuration Manager Technical Preview Branch – Available Now! – here
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
Let’s understand the differences between SCCM Package Vs Application 32 Vs 64 Context. Discussing the differences between SCCM CB packages and the application model is not new.
I have seen several posts and discussions about the advantages of using an application model rather than “classic” packages. Let’s see more details about the SCCM Package Vs. Application.
I recommend using applications rather than packages for several reasons. I’m not getting into the details of the advantages of using the SCCM CB application model.
In this post, we will see a video experience of the SCCM CB package running in 32-bit and the application running in a 64-bit context. SCCM 2007 was a 32-bit application, and if I understand correctly, SCCM 2007 packages always run in a 32-bit context.
SCCM CB Package Runs in 32 Bit Context and Application in 64-bit– SCCM Package Vs Application 32 Vs 64 Context
In this video, you will get all the details about the SCCM CB Package Runs in 32 Bit Context and Application in 64 Bit. Create and RUN Powershell script almost in real-time through the SCCM CB version. Real-time example scenarios are explained in the video.
SCCM Package Vs Application 32 Vs 64 Context – Video 1
History of SCCM Packages?
This could be because the package implementation is simply a 32-bit code. The packages can’t run in a 64-bit context. Is this true for SCCM CB as well?
SCCM Package Vs Application 32 Vs 64 Context – Fig.1
Per my testing and video tutorial here, the packages in SCCM CB always run in a 32-bit context. This statement is true for Windows 10 32-bit and 64-bit machines. It won’t be easy to understand and reproduce this scenario when deploying MSI or EXE applications as a package.
The MSI/EXE applications, packaged to run only with 32-bit, will work fine with SCCM CB packages. However, these apps will fail when trying to convert these 32-bit packages into a new application model.
To fix this issue, we need to enable an option in the SCCM app model (Deployment type properties) called “Run installation and uninstall the program as 32-bit process on 64-bit clients“.
Programs
Run installation and uninstall the program as 32-bit process on 64-bit clients
SCCM Package Vs Application 32 Vs 64 Context – Table 1
SCCM Package Vs Application 32 Vs 64 Context – Fig.2
How to Confirm SCCM Packages Run with a 32bit Code?
I created a PowerShell script to use package options in SCCM CB. Navigate \ Software Library \ Overview\Application Management\Packages” and right-click and create a package with the PowerShell script. Deploy the script to a Windows 10 64bit machine.
When we deploy the PowerShell script to a Windows 10 64-bit machine, the Windows PowerShell 32-bit application is executed, as shown in the video above. This proves that the SCCM CB package uses 32-bit code, which can’t run in a 64-bit context.
You can deploy 64-bit MSI/EXE/Scripts using SCCM packages. The best method is to run the package from the SysNative context. Sysnative is a virtual folder that will help us access the 64-bit System32 folder from a 32-bit application or script.
SCCM Package Vs Application 32 Vs 64 Context – Fig.3
SCCM CB Software Center client is still a 32-bit application. The app SCClient(32-bit) is visible in the above picture. This proves that the new software center is a 32-bit client on a Windows 10 64-bit machine.
How to Confirm SCCM Applications Run with 64-bit Code?
SCCM CB application always runs in a 64-bit context. By default, all the applications created using the SCCM CB app model use 64-bit context to start the execution. Your 32-bit application will fail if you create and deploy an SCCM application to clients.
When a specific requirement to run within a 32-bit context exists, you need to enable the following option: “Run installation and uninstall the program as a 32-bit process on 64-bit clients.” You can find this option in Application—deployment type properties.
To prove SCCM applications use 64bit context to run MSI/EXE/Scripts, I have created an application via \Software Library\Overview\Application Management\Applications. I used the same PowerShell script (which I used to develop the SCCM package). Deployed application to Windows 10 device.
As you can see in the video here, I initiated the PowerShell execution from the software center. The PowerShell script (Windows PowerShell) runs within a 64-bit context. When deployed as an SCCM package, the same PowerShell script ran in a 32-bit context.
SCCM CB Task SequenceRuns within a 64bit Context
The Task Sequence in SCCM CB runs within a 64-bit context. However, the SCCM CB TS engine provides a similar option for applications to run 32-bit applications/scripts.
The option is to enable the following: “Run installation and uninstall the program as 32-bit process on 64-bit clients“.
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
Let’s discuss the SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr. SCCM CB fast channel has an option to push PowerShell scripts to devices. These PowerShell scripts can be pushed almost in real time.
The video tutorial attached above explains this real-time push of the RUN PowerShell script. This post will see “SCCM Run Scripts options and architecture“.
For more details about the run PowerShell script option, refer toSCCM CB Run PowerShell ScriptDirectly from the Collection post.
SCCM 1810 Updates – Improvements in SCCM Run Scripts
There have been many improvements to SCCM run script deployment in recent releases. One of the latest releases is SCCM 1810, and the following are some upgrades that Microsoft brought in.
With SCCM 1810, you can view detailed script output in raw or structured JSON format. The following SCCM script performance and troubleshooting improvements apply from the SCCM 1810 version onwards:
Updated SCCM 1810, clients return output of less than 80 KB to the site over a fast communication channel. This change increases the performance of viewing script or query output.
Additional logs for troubleshooting, as I mentioned in the CMPivot post.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.1
What is the Process of Pushing PowerShell Scripts using the SCCM Right Click Option?
SCCM CB 1706 supports pushing normal PowerShell scripts using this method. However, the SCCM team included two new features in the Run Script option in SCCM CB preview releases. The architecture details of SCCM Run Scripts are explained.
Enable the Create and Run Script feature
Import PowerShell Script
Approve or Decline the PowerShell Script
Right-click on Device Collection and run the script
Get the status of PowerShell script execution via the Monitoring workspace
Read parameters from the PowerShell script.
The capabilities of PowerShell script parameters have been improved. They now detect mandatory and optional parameters and prompt you to enter mandatory and optional parameters.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.2
Why is the “Script” Node Not Visible in the SCCM CB Console?
Create and Run Script is a pre-release feature of SCCM CB 1706. The script node is visible in the Software Library workspace. So, if you have not enabled this feature from “Administration – Updates & Servicing – Features, “Navigate through the console path \Administration\ Overview\Updates and Servicing\Features. Right-click on the “Create and Run Script” feature and select Turn On.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.3
How to Import PowerShell Script to SCCM CB?
As I explained in the video, navigate the SCCM console Software Library workspace (“\Software Library\Overview\Scripts”) and click on the Scripts node. Right-click on the script node and select the Create Script option. Script wizard will guide you through importing PowerShell script to SCCM CB.
Provide the appropriate Script name, “Create Files and Folders.” The supported script language is ONLY PowerShell now. We may soon have some other supported options. Don’t expect SCCM to check the PowerShell script syntax errors before importing.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.4
How to Approve PowerShell Script via Fast Channel Push Method?
The SCCM team included an approval flow into the Run Script engine to avoid accidental PowerShell script pushes to devices. By default, you can’t approve your PowerShell script.
To enable the approval script option to yourself, you must disable the following option from Hierarchy settings properties “Do Not Allow Script authors to approve their scripts“.
You can right-click on the script you want to execute and select the Approve/Deny button. The Approve or Deny script wizard will walk you through the script Approval process. The video guide has more details.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.5
How to Execute the PowerShell Script via SCCM CB Fast Channel using the Push Method? SCCM Run Scripts?
Once SCCM approves the Script, that script will be available for execution. The PowerShell script is initiated from “\Assets and Compliance\Overview \Device Collections” in the SCCM CB console.
Select the device collection you want to target to execute the PowerShell script and right-click on the group – select the Run Script (SCCM Run Scripts) option.
The Run Script wizard will not show all the PowerShell scripts imported into SCCM. It will only show the scripts that admins have approved. You can select one approved script at a time from the SCCM Console.
How to Execute the PowerShell Script via SCCM CB Fast Channel
Device Collections
All Desktop and Server Clients
Run Script
Confirm the Script Execution Details
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Table 1
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.6
End-User Experience of Run PowerShell Script via Fast Channel Push Method?
Once the script is initiated for a collection, all the devices with the correct SCCM client version (SCCM CB 1706 and above) will get a push notification to execute a script (SCCM Run Scripts). The SCCM client Windows 10 devices will immediately execute the script on the device.
As you can see in the video here, I initiated a file and Folder creation script for Windows 10 devices. The SCCM client received a notification from the notification server and immediately executed the script on the Windows 10 machine.
The script created 20 files and folders in the C drive root of the Windows 10 device. I have another post explaining troubleshooting of running a script, “What is Fast channel push notification“.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.7
How to Monitor the Execution of PowerShell Scripts through Push channel?
Once the PowerShell script is executed on a Windows 10 machine, the client will send the result to the SCCM notification server. You can see the results in “\Monitoring \Overview\ Client Operations”. If I’m not wrong, the operation Name is “Run Script (SCCM Run Scripts)”, and each task will be active for 1 hour.
SCCM CB Run PowerShell Script Directly from Collection Configuration Manager ConfigMgr – Fig.8
References
Video Guide to Troubleshoot SCCM CB Fast Channel Push Notification Issues – here
Fast channel notification and MP replica issues – Here
What’s New With ConfigMgr’s Client Notification Feature – Here
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.
