SCCM is device management tool for Windows devices. This is a client server application by Microsoft. How to manage devices with this tool for Windows devices? 90% of corporate Windows devices are managed by the this tool.
SCCM video posts in this blog will help you to understand in a better way. Most of the videos shared in this post are real time experience of this Windows Device managment.
SCCM is the short for System Center Configuration Manager. This tool is a software management suite provided by Microsoft that allows users to manage a large number of Windows based computers.
This tool features remote control, patch management, operating system deployment, network protection and other various services. Device management solution like has a great tech community.
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, 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
I have conducted a How to Manage Devices (HTMD) Community Teams meeting session (weekend learning) to share my real-world experience of SCCM Client Troubleshooting. The recording is available in this post is available in the below section of the post.
I have conducted a How to Manage Devices Community Teams meeting session to share my real-world experience of SCCM CMG Cloud Management Gateway design and implementation for more than dozen customers. The recording is available in this post is available in the below section of the post.
Many How To Manage Device Community members were looking for the recording of the session. So I thought of sharing the same with you all.
How to Find Out Devices Connected to CMG?
I have a couple of posts where I explained more details of Configuration Manager Cloud Management Gateway and troubleshooting of CMG with SCCM logs. You can refer below:
I have seen a discussion about controlling Microsoft Teams’ automatic updates (Disable Microsoft Teams Automatic Update) from the internet when most of the workforce is working from home. The idea is not to update Microsoft Teams automatically when the user is connected from home. There could be two potential options to stop Microsoft Teams Automatic Update to new versions.
Introduction
As per Microsoft, Teams desktop client updates are released every two weeks. I think this update is not on the same channel as of Office 365 pro plus updates. MSTeams update usually takes place on a Tuesday.
I don’t think Microsoft provides any direct way to control Teams automatic update via Group policy or some other method. The desktop client updates itself automatically. Teams desktop application checks for updates every few hours, downloads it (if there is any), and then wait for the Windows 10 to be idle before silently installing the update.
I have a couple of posts to help IT Pros to install Microsoft Teams using Configuration Manager (a.k.a SCCM). More details about the MSTeams installation are explained in the following post. If you are looking for step by step MSTeams installation guide using SCCM|ConfigMgr, then refer to the following guide.
In this post, you could help you to find out some potential solutions to block Microsoft Teams automatic update. I don’t think this method is optimal or recommended by Microsoft for the Teams installation on Windows 10 devices.
Block Microsoft Teams Automatic Update – Disable Automatic Update for Microsoft Teams
Create MS Teams Application with Disable Automatic Update for VDI & WVD
Application name: Teams Machine-Wide Installer
Publisher:Microsoft
Software version:
Deployment type name: Teams Machine-Wide Installer - Windows Installer (*.msi file)
Product Code: {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
Installation behavior:Install for MachineContent location: \cmmemcm\Sources\Package Sources\MSTeams for VDI\
Number of files: 1
Content files:Teams_windows_x64.msi
Make sure that you use the following command line to Diable Microsoft Teams Automatic Update
The ALLUSER=1 parameter is used only to specify a per-machine installation.
The ALLUSERS=1 parameter is used only if you want to have options – “all users can uninstall Teams if they have admin credentials.”
Install Behaviour – Make sure you selected -> Install for System
Block or Disable Microsoft Teams Automatic Update
The following metadata of Microsoft Teams application is the one that you should use for blocking the Microsoft Teams auto-updates behavior. As you can see in the below section, this is applicable only for VDI environments.
General Information:
• Application name: Teams Machine-Wide Installer
• Administrator comments:
• Publisher: Microsoft
• Software version:
• Optional reference:
Categories:
Deployment type name: Teams Machine-Wide Installer - Windows Installer (*.msi file)
Requirement rules:
Content:
• Content location: \cmmemcm\Sources\Package Sources\MSTeams for VDI\
• Installation program: msiexec /i "Teams_windows_x64.msi" /l*v TeamsInstall.log ALLUSER=1 ALLUSERS=1Detection Method:
• Product code: {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
User Experience:
• Installation behavior: Install for system
The secret to Disable Microsoft Teams Automatic Update?
So what is the secret here to Block Microsoft Teams Automatic Updates while installing an application using ConfigMgr?
As per Microsoft documentation, PER-Machine based installation helps to DISABLE automatic updates for Microsoft Teams.
Verification
The installation Microsoft Teams failed with an error “Installation has Failed – Cannot install for all users when a VDI environment is not detected.” The following are some of the snippets of Microsoft Teams installation log file.
As you can see in the above error, this is applicable only for VDI environments. I feel this is because of custom action checked included in the Teams MSI installation file. So what is the option to Disable Microsoft Teams automatic update? Let’s check the last section to get details.
CustomAction RunInstalledExecutable returned actual error code -2147467259 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (EC:58) [22:28:49:375]: Note: 1: 1722 2: RunInstalledExecutable 3: C:\Program Files (x86)\Teams Installer\Teams.exe 4: --allUsers
MSI (s) (EC:58) [22:28:49:375]: Note: 1: 2205 2: 3: Error
MSI (c) (40:2C) [22:28:49:391]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action RunInstalledExecutable, location: C:\Program Files (x86)\Teams Installer\Teams.exe, command: --allUsers
Cannot install for all users when a VDI environment is not detected – Disable Automatic Update for Microsoft Teams
Solution
I think Microsoft Teams update might be part of Office 365 pro plus update channel in near future. The only workaround which I came to know while writing this post is given below.
1. It seems you can disable the Microsoft Teams Automatic Update by blocking the traffic to update URLs via corporate proxy solutions.
What is Dead File Microsoft Teams? Are you looking for a script logic to confirm the uninstallation of Microsoft Teams? Is this a funny fact 🤣🤣😎 You can check for the existence of a file named “.dead”. You can find this “.DEAD” file in the AppData folder of the user profile.
Introduction
You can refer to the following blog posts to understand the installation option of Microsoft Teams MSI! .However, in this post, we will see more about the DEAD file? What does this DEAD file mean? Why the DEAD file is empty? Does the presence of a “.DEAD” file in the application folder means the Teams application is uninstalled from the Windows 10 device? YES! 🙂
The .DEAD file can be used as one of the detection methods for the un-installation of Microsoft Teams. Can’t we use MSI product code as a detection method? Of course yes.
“How to manage devices (HTMD)” team is arranging a series of LIVE digital events. We have already started the live online events on the following weekend. Recording Details are given below.
March 30th, 2020
April 4th and 5th April 2020
April 11th and 12th April 2020
April 18th and 19th April 2020
April 25th and 26th April 2020
May 2nd and 3rd May 2020
NOTE! – The recording of all the events are available in the following YouTube Channel.
We are a bunch of technical people trying to help the device management community (SCCM, ConfigMgr, Intune, etc) by sharing our experiences within the IT industry!
Let’s see the list of SCCM pre-release features vs full features after the release of the SCCM 2002 release. Excited to see many features are fully developed now and out of the PREVIEW tag with the 2002 version of ConfigMgr.
Yes, there is a PowerShell Script to Enable Opt-In version of SCCM. I get many questions related to PowerShell script which you need to use to enable the FAST (Early/Opt-in) Ring version of Configuration Manager.
You need to have an ONLINE Service connection point to enable the Opt-in (early update) ring of SCCM 2006.
NOTE! – You need to use the PowerShell script to enable the Opt-in version of ConfigMgr 2002 or Fast ring or Early Update ring version of 2006.
Once the 2002 version of Configuration Manager is Generally Available, then all your SCCM infra with the online service connection point will automatically get the 2006 update.
I know you have seen many steps by step videos and installation guides to update Configuration Manager current version. This guide is another one that shows how to upgrade from SCCM 1910 to 2002 version.
NOTE! – Well, I know it’s not SCCM. It’s called Microsoft Endpoint Manager Configuration Manager (MEMCM) or Microsoft Endpoint Configuration Manager (MECM).
Prerequisites of 2002 Version
NOTE! – If you have SCCM DPs and PXE servers running on Windows server 2008 R2. You need to plan to upgrade it before the latest supported version before upgrading to the ConfigMgr 2002 version of the current branch. Server 2008 R2 DP and PXE are not supported anymore. More details – here.
The following SCCM versions are supported for the upgrade to 2002.
Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
Check 2002 fast or Opt-in version update of ConfigMgr is already available or not?
If not, click on the “Check for Updates” button from the ribbon menu
Click OK to continue
SCCM 2002 Installation Step by Step Guide
Configuration Manager 2002 update is available and Downloading
SCCM 2002 Download Stuck
This stuck download issue is a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.
There are a couple of ways to fix this kind of issue if it’s not related to proxy and internet. You can refer to the previous blog posts to solve Update Download stuck problems.
More troubleshooting help on SCCM 2002 Download stuck and upgrade issues here and here .
Downloading – SCCM 2002 Installation Step by Step Guide
Log Files are Your Friend
DMPDownloader.log for SCCM 1910 source file download issues
ConfigMgrSetup.log for Redist Files Download Issue
CMUpdate.log for all the upgrade related activities
If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.
The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update’s redistribution files, restart the SMS_Executive service on the site server.
Another common download issue occurs when proxy server settings prevent downloads from silverlight.dlservice.microsoft.com, download.microsoft.com, and go.microsoft.com.
Right Click on the Update “Configuration Manager 2002” Update
Select PreRequisite Check
Once the Prerequisite Check is completed successfully proceed to the next step
Right Click on the Update “Configuration Manager 2002” Update
Click on Install Update to start the SCCM 2002 installation
Ready to Install – SCCM 2002 Installation Step by Step Guide
SCCM 2002 Update Prerequisite Check Stuck?
The SCCM upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 2002 update source files will be copied to primary servers.
You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks here.
NOTE! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.
Configuration Manager Update Wizard
Let’s continue with SCCM 2002 update wizard:
Click on “Ignore any prerequisite check settings and install the update regardless of missing requirements” box
Click on Next button
Select the features you want to enable after the upgrades from Features Included in Update Pack page
….
…..
Click on Next to continue
Features Included in Update Pack – SCCM 2002 Installation Step by Step Guide
Client Update Settings page configuration
Upgrade without validating (Direct Production Upgrade)
Validate in pre-production collection (Test the client before the upgrade)
Click NEXT button to continue
Client Update Settings Option
Client Update Settings is another important option in Configuration Manager Update Wizard for SCCM 1810 upgrade. SCCM Client update settings include an update for SCCM client. You can upgrade your clients immediately. Or validate this client in pre-production collection before you upgrade all your SCCM clients.
I would recommend validating the client version with pre-production collection devices before upgrading the SCCM 1810 client package to all your clients directly.
Upgrade without validating
If you select the SCCM client upgrade without validating option, this overwrites your current SCCM client package with the new SCCM client update. All new client installations and client upgrades use this new client update.
Validate in Pre-production collection
If you select the “Validate in Pre-production collection” option, then you will get an option to validate the new client update on members of pre-production collection while you keep your production client package intact. Later once you are confident with the new client package, you can overwrite the production package using Client Update Options in the Updates and Servicing node of the SCCM console.
Click on “I accept these License Terms and Privacy Statement“
Click on NEXT button to continue
License Agreement – SCCM 2002 Installation Step by Step Guide
Click on Close to continue to the installation process of 2002
Close – Start the Installation Process – SCCM 2002 Installation Step by Step Guide
Installation Progress
Once you complete the Configuration Manager update wizard, the SCCM 2002 upgrade process will kick start. And the updates and servicing node in the ConfigMgr console will show that the update is in installing state.
You can start monitoring ConfigMgr 2002 upgrade from this stage.
You can click on a link “Show Status” from related objects.
Show status will show you the details about the installation status in monitoring workspace.
I would recommend following the below screenshot to see the real-time updates of the SCCM upgrade. Let’s monitor the installation Monitoring workspace:
Navigate to – \Monitoring\Overview\Updates and Servicing Status
Updates and Servicing Status – SCCM 2002 Installation Step by Step Guide
Finish – SCCM 2002 Installation
The following sections have been successfully completed as part of the 2002 installation.
The last step of the ConfigMgr 2002 installation is by upgrading the console of Primary servers & CAS server.
You need to make sure all your remote SCCM console installations are upgraded to the latest version. This is not very critical if your remote SCCM console is already running with the n-1 version (where n = 2002 in this scenario).
But, if your remote SCCM console is not n-1 then, you need to make sure your console is updated otherwise you won’t be able to connect to the SCCM console.
SCCM 2002 Version Numbers
Let’s see what are the Configuration Manager version numbers.
Really need to setup SUP with default WSUS product selection (Default WSUS Product Selection)? The quick post to let you know the WSUS product list which is automatically selected underneath Windows and Products category for your ConfigMgr infrastructure.
I don’t think there is any cleanup done to remove the legacy products from the WSUS products list for many years. I could still see Server 2003 and Windows XP are part of the product list which are automatically selected by default.
Why do we need those? What you think? Let’s check out the default WSUS product selection (this is out of box experience).
List of Products
At first look, you will feel there are NO products selected! You are Wrong! When you expand, you could see there are many “LEGACY” office products and Windows versions are already selected by default.
I don’t know how many of you still need the following products. And moreover, the latest OS version Windows 10 is not selected by default 🙂
Office XP
Office 2003
Office 2007
Windows XP
Server 2003
Office – Windows Old version products
Best Options
My advice would be to remove all the default product selections and start from scratch.
If you are setting up a new ConfigMgr | WSUS, you just need Windows 10 and Server 2016 (optionally server 2012). What you say?
Windows 10 and Server 2016 – Default WSUS Product Selection
