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.
SCCM How do you hide tabs in New Software Center Customization? SCCM CB 1708 has introduced new features into software center customization. Earlier, enterprise-level customization of software centers was possible only with Intune subscription.
With the new software center feature, you can customize the software center without an Intune subscription. This post will show SCCM CB How to Hide Tabs in the New Software Center.
In the future version of SCCM CB, the Software center can be customized according to your enterprise customer requirements. The first step toward using new customization features is to enable a new software center policy in client settings.
Also, you must know that “Application Catalog” website support ends with the first update released after June 1, 2018.
SCCM How to Hide Tabs in New Software Center Customization
SCCM Admins can add enterprise branding elements to the software center, which will help specify each tab’s visibility. In the video below, you will get all the details on hiding tabs in New Software Center Customization.
SCCM How to Hide Tabs in New Software Center Customization – Video 1
The First Step to Getting New Customization Options in the Software Center?
Ensure you enable the client setting policy for the “New Software Center”. The SCCM team already documented that the previous version of Software Center will no longer be available.
The new policy can be enabled via client settings, Computer Agent > Use new Software Center.
SCCM How to Hide Tabs in New Software Center Customization – Fig.1
What are the New Features Coming up in the SCCM CB Software Center?
These options are available only with the preview version of SCCM CB 1708. I assume that these features (even more) will be available in the next production release of SCCM CB 1710.
Set Software Center-specific company name
Change/Set a Software Center color theme
Set a company logo
Hide/Disable tabs on Software Center for SCCM client devices
SCCM How to Hide Tabs in New Software Center Customization – Fig.2
What is the Recommendation for Implementing Software Center Changes?
The Recommendation is NOT to change default client setting policies. It’s better to create a new custom client setting policy to test new software centre features and deploy it to pilot client devices. Once you have tried and confirmed that everything is OK with testing new software centre features, you can deploy it to all SCCM CB client devices.
More Details about Logo Setting in SCCM CB New Software Center
Specify settings that apply to all clients in the hierarchy and can be modified by custom settings. You may disable new features for some client devices. You must say NO for the following location: “Select these new settings to specify company information.”
I could see that the following 3 settings of the new software center are disabled when I set NO to the “Select these new settings to specify company information” policy. When you put this policy to YES, you can set Company Name, color Scheme for the Software center can be selected from this option.
Ensure you have the correct logo dimension and size per the following description. Select a logo for the software center. The Maximum dimensions are 100×400 pixels, and the file cannot be larger than 750 kb. This is the information for the 1708 preview version of SCCM CB.
SCCM How to Hide Tabs in New Software Center Customization – Fig.3
How to Hide/Disable Options Tab in the SCCM Software Center
Disabling or hiding the options tab in SCCM CB’s new software center is easy. This option is part of the client-setting policy. It’s better to disable or hide the software center options tab from client devices when you don’t want to allow users to change their work hours settings.
You can disable or hide other tabs of the software center as per your requirements. For example, if you don’t want a user to see the Software update installations, you can turn off the UPDATES tab in the software center and all the tabs mentioned in the list below.
Select NO to disable or hide tabs in the new Software Center for SCCM CB client devices. At least one tab must be set to be visible or should be enabled.
Disable Applications tab
Disable Updates tab
Disable the Operating Systems tab
Disable the Installation Status tab
Disable the Device Compliance tab
Disable Options tab
SCCM How to Hide Tabs in New Software Center Customization – Fig.4
End-User Experience of New Software Center in Windows 10
I have disabled the Updates, Operating System, and Options tabs for my testing. Also, I have changed the colour theme of the new software center and deployed the client setting policies to Windows 10 devices.
The user on that device can see only three tabs in the Software Center: Applications, Installation Status, and Device Compliance.
The user on that device can see only three tabs in the Software Center
Applications
Installation Status
Device Compliance
SCCM How to Hide Tabs in New Software Center Customization – Table 1
SCCM How to Hide Tabs in New Software Center Customization – Fig.5
References
SCCM CB Software Center customization Preview – 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 discuss the SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification. SCCM CB 1708 version added a new feature called the “Reboot” action to the fast channel push client notification.
SCCM CB preview version 1708 has been released. I have the pleasure of upgrading my lab environment to this preview version.
We can use the SCCM console to identify client devices that are pending reboot. Once identified, the devices can be restarted using a client notification action.
This post will show the Video Experience of the SCCM Reboot Task for the Collection of Devices via Fast Channel Push Notification. The YouTube video tutorial is here.
This video provides all the details of the Reboot Task via Fast Channel SCCM CB 1708. The video details are shown below.
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification – Video 1
How to Restart Computers from the SCCM Console– SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification
Using the SCCM CB 1708 preview version, you can restart the computers in a device collection. The first step is to identify the computers in a “pending restart” state.
How Do you Find Out the Restart/Reboot of Pending Devices?
Once restart pending devices are identified, right-click on collection or device to initiate the REBOOT action. This reboot action is created via the FAST client notification channel.
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification – Fig.1
We don’t have a reboot script that can be deployed to machines. Most importantly, this “REBOOT” action is triggered via the PUSH channel of SCCM CB client notification.
SCCM Reboot Task for Collection of Devices
Assets and Compliance
Overview
Devices
All Desktop and server clients
Client Notification
Reboot
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification – Table 1
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification – Fig.2
Restart Action Failed on a Client Device?
I initiated a reboot action for the Pending reboot machine, and it didn’t work. Why? I checked the log files and ConfigMgr applet on a Windows 10 machine.
I realized that I had upgraded the SCCM CB server version (5.00.8549.1000) to 1708, but we didn’t upgrade the Windows 10 machine’s SCCM client version (5.00.8542.1000) to 1708.
CcmNotificationAgent.log is the best log to check for troubleshooting fast-channel push notification tasks.
You can check the status of the REBOOT action in the monitoring workspace, the “Client Operations” node in the SCCM console.
The operation name for the REBOOT action is Task 17! But I’m sure this will be changed in the production version of the release. The error logging can be improved because the error message was “Failed to execute task, error 0.”
CcmNotificationAgent LOG with Errors
<![LOG[NetworkInfo: IPAddress 20.20.20.23,fe80::b09e:95a3:172a:4212]LOG]!><time="21:07:18.726-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:124">
<![LOG[NetworkInfo: IPSubnet 255.0.0.0,64]LOG]!><time="21:07:18.726-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:147">
<![LOG[NetworkInfo: AccessMP SCCMTP1.Intune.com]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:155">
<![LOG[NetworkInfo: IsClientOnInternet 0]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:159">
<![LOG[Update the timeout to 900 second(s)]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbtcpclient.cpp:916">
<![LOG[Receive signin confirmation message from server, client is signed in.]LOG]!><time="21:07:18.851-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:221">
<![LOG[Receive task from server with pushid=1002, taskid=1007, taskguid=5AFF6AEA-67D5-4124-B04F-162FDB0E314E, tasktype=17 and taskParam=]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:312">
<![LOG[Failed to find action instance for task type 17]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="3" thread="6212" file="bgbcontroller.cpp:682">
<![LOG[Failed to execute task, error 0]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="3" thread="6212" file="bgbcontroller.cpp:646">
Results of Successful REBOOT PUSH Task
Upgraded the client version to 5.00.8549.1000 and reinitiated the REBOOT task by right-clicking on a collection – Client Notification – Reboot. This action created a new task for the devices (pending reboot) in that collection through SCCM PUSH fast channel notification.
What is the architecture flow of SCCM CB Fast channel push notification? I have explained fast channel architecture flow in the post here.
The SCCM fast channel push client notification service will immediately notify the client about the task assigned. However, the client won’t be restarted immediately after receiving the task from the notification server component. The SCCM client will check the policy settings for “Computer Restart” and schedule the restart per the policy.
The computer restart policy is 90 minutes by default, and you can customize this policy from the client settings tab. The reboot or restart notification is very well integrated with the “Software Center” experience, which is a great advantage of this feature.
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification – Fig.3
Resources
Update 1708 for Configuration Manager Technical Preview Branch – Available Now! – here
Capabilities in Technical Preview 1708 for System Center Configuration Manager – here
Video Guide to Troubleshoot SCCM CB Fast Channel Notification Issues – 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 discuss how to Troubleshoot SCCM Fast Channel Push Notification Issues. The fast channel notification feature has been in SCCM products since 2012 SP1. SCCM fast channel notification was mainly used to notify clients about vital policies, collect inventories, etc.
SCCM CB 1706 introduced the “RUN Script” option through the fast channel push notification. This post will use a video guide to troubleshoot SCCM CB fast channel push notification issues. A video tutorial about SCCM CB fast channel push notification is here.
Let’s understand Fast channel notifications for clients. SCCM Fast channel notification is a “PUSH” method of notifying clients about the new policies. This communication channel for SCCM client fast notification is TCP (port 10123) or HTTP (port 80).
How to Troubleshoot SCCM CB Fast Channel Notification Issues
In the video, you’ll find comprehensive details on troubleshooting SCCM CB Fast Channel Notification issues. This guide will cover scenarios where Fast Channel Notifications may fail or encounter issues within the SCCM environment.
Troubleshoot SCCM Fast Channel Push Notification Issues – Video 1
What is SCCM Fast Channel Push Notification?– Troubleshoot SCCM Fast Channel Push Notification Issues
The SCCM client communicates to its MP every 15 minutes to confirm that it’s still online. When your client does not show as ONLINE in the SCCM console, we may have a problem with the fast notification communication channel.
SCCM Push Vs. Pull
Historically, SCCM uses the PULL method, expecting the client to ask for new policies regularly. But, the fast channel uses the PUSH method. What is BGB in SCCM? BGB = Fast Channel Notification related components. I don’t know whether this notification channel was codenamed “Big Green Button” or not 😉
Troubleshoot SCCM Fast Channel Push Notification Issues – Fig.1
What are the Components of SCCM CB Fast Channel Notification?
SCCM CB fast channel notification has three components. The notification manager will be located along with site servers (Primary/Secondary). It generates “push messages” for clients, sends notifications to the BGB server (MP), and stores the results.
The notification manager initiates push notifications from the site server. The log file BGBmgr.log provides more details about the notification manager. Notification files (*.BOS files) are stored in the INBOX/BGB.box folder. The video tutorial here shows the BOS file being created.
As you can see in the following fast channel notification architecture diagram, when the primary server has an MP component, the notification manager and notification server are also on that primary server.
The notification server will be located along with the Management Point (MP) and secondary sites. It will have TCP and HTTP listeners. These will help listen to the notification manager (DB) push notifications and confirm the client’s online status.
The notification manager pushes result files (*.BTS) from clients. BGBServer.log is the file on the MP setup or site server setup directory.
The Notification Agent is a fast-channel notification component at the SCCM client end. It’s part of the SMS agent (CCMEXEC). The agent establishes a persistent connection with its notification server.
This will receive the PUSH messages from MP. CcmNotificationAgent.log is the log file on the SCCM client device. The log can note MP/Notification server communication errors.
What is the architecture flow of SCCM CB Fast channel push notification?
Troubleshoot SCCM Fast Channel Push Notification Issues – Fig.2
Why is the SCCM CB Client NOT Showing as ONLINE?
The problem is that the SCCM CB client is not showing as ONLINE in the console. Instead, it always stays offline. The problem is ONLY with FAST notification channel communication; normal deployments and policies are working fine.
Troubleshooting of SCCM CB Fast Channel Notification
First, you must ensure all the notification components are installed correctly on the server and client sides. The following log files can confirm this for installation issues and troubleshooting.
Installation Issues and Troubleshooting
SCCM CB Notification Server/Manager
BGBServer.log
BgbHttpProxy.log
BgbSetup.log
BGBisapiMSI.log
Troubleshoot SCCM Fast Channel Push Notification Issues – Table 1
Fast Channel Notification – Server-Side Troubleshooting
I checked the log files on my primary and MP (both are on the same server), and BGBServer.log shows a warning all the time: “WARNING: Notification Server (% systemroot%system32dllhost. exe) with TCP port 10123 is NOT allowed by Windows Firewall on all interfaces I.” But I thought it should work with the port 80 HTTP channel. It was not working as expected.
Following are the extracts of troublesome logs on the BGB notificationserver. BGBServer.log
Starting SMS Notification Server…~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.005-330> Server GC is OFF~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.006-330> Trigger to start TCP listener~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.022-330> The HTTP listener is started~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.030-330> Listening connections on port 10123. Waiting for clients to connect…~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.061-330> WARNING: Notification Server (%systemroot%\system32\dllhost.exe) with TCP port 10123 is NOT allowed by Windows Firewall on all interfaces.~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:16:02.062-330> Total online clients: 0 (TCP: 0 HTTP: 0)~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:21:02.039-330> Generated BGB online status FULL report C:\Program Files\Microsoft Configuration Manager\inboxes\bgb.box\Bgb72ul2.BOS (version: 0) at 08/15/2017 01:21:02~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:21:02.055-330> WARNING: Notification Server (%systemroot%\system32\dllhost.exe) with TCP port 10123 is NOT allowed by Windows Firewall on all interfaces.~~
lt;SMS_NOTIFICATION_SERVER><08-15-2017 01:21:02.067-330> Wait 300 seconds for notifications…
The notification agent was running. But, the CcmNotificationAgent.log log showed loads of errors. One of the errors indicated that there could be a communication issue between the server and the client.
Troubleshoot SCCM Fast Channel Push Notification Issues – Fig.3
Error 10060 means ==> A connection attempt failed because the connected party did not appropriately respond after a period, or an established connection failed because the connected host could not respond. BGBAgent component log :-
<![LOG[Bgb client agent is starting...]LOG]!><time="01:23:55.212-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="6372" file="agentendpoint.cpp:238">
<![LOG[BgbController main thread is started with settings: {bgb enable = 1}, {tcp enabled = 1}, {tcp port = 10123} and {http enabled = 1}.]LOG]!><time="01:23:55.259-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="6372" file="bgbcontroller.cpp:126">
<![LOG[Startup random sleep for 1 seconds.]LOG]!><time="01:23:55.290-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcontroller.cpp:416">
<![LOG[Critical Battery: [FALSE]]LOG]!><time="01:23:56.306-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcommon.cpp:60">
<![LOG[Connection Standy: [FALSE]]LOG]!><time="01:23:56.306-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcommon.cpp:61">
<![LOG[Network allowed to use: [TRUE]]LOG]!><time="01:23:56.306-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcommon.cpp:62">
<![LOG[Access point is SCCMTP1.INTUNE.COM. (SSLEnabled = 0)]LOG]!><time="01:23:56.415-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcontroller.cpp:276">
<![LOG[CRL Checking is Enabled.]LOG]!><time="01:23:56.431-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcontroller.cpp:284">
<![LOG[Both TCP and http are enabled, let's try TCP connection first.]LOG]!><time="01:23:56.431-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcontroller.cpp:792">
<![LOG[Connecting to server with IP: 20.20.20.22 Port: 10123
]LOG]!><time="01:23:56.447-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbtcpclient.cpp:699">
<![LOG[Failed to connect to server with IP v4 address with error 10060. Try next IP...
]LOG]!><time="01:24:17.468-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbtcpclient.cpp:703">
<![LOG[Failed to signin bgb client with error = 80004005.]LOG]!><time="01:24:17.468-330" date="08-15-2017" component="BgbAgent" context="" type="3" thread="5200" file="bgbcontroller.cpp:635">
<![LOG[Connecting to server with IP: 20.20.20.22 Port: 10123
]LOG]!><time="01:25:17.482-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbtcpclient.cpp:699">
<![LOG[Failed to connect to server with IP v4 address with error 10060. Try next IP...
]LOG]!><time="01:25:38.501-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbtcpclient.cpp:703">
<![LOG[Failed to signin bgb client with error = 80004005.]LOG]!><time="01:25:38.501-330" date="08-15-2017" component="BgbAgent" context="" type="3" thread="5200" file="bgbcontroller.cpp:635">
<![LOG[Fallback to HTTP connection.]LOG]!><time="01:25:38.501-330" date="08-15-2017" component="BgbAgent" context="" type="1" thread="5200" file="bgbcontroller.cpp:828">
[CCMHTTP] ERROR: URL=http://SCCMTP1.Intune.com/bgb/handler.ashx?RequestType=Continue, Port=80, Options=224, Code=0, Text=CCM_E_BAD_HTTP_STATUS_CODE
Successfully queued event on HTTP/HTTPS failure for server 'SCCMTP1.Intune.com'.
Failed to post continue request with error code 87d0027e.
Troubleshoot SCCM Fast Channel Push Notification Issues – Fig.4
Fix for SCCM CB Fast Channel Notification Issues
The Firewall port 10123 was not opened between the SCCM client and the primary BGB server. I ran the following command from the client, “Telnet 10123,” and it didn’t work (the port was not opened).
I checked the software and hardware firewalls on the server side and discovered that Windows Firewall was blocking the port communication 10123.
Disabled the Windows Firewall on the notification server for testing and restarted the client agent services (SMS Agent) on the client machine. This helped to resolve the fast channel notification issue with the SCCM CB environment.
In an ideal world, you should exclude/exempt port 10123/80 from the hardware and software firewall between the fast channel notification server and agent. This will help to resolve the issue.
More details are available in the video tutorial here
Troubleshoot SCCM Fast Channel Push Notification Issues – Fig.5
Server Side Logs – After Successful Actions on Fast Channel Notification
I finished sending push tasks (PushID: 1 TaskID: 3) to 1 client and generated the BGB online status DELTA report, two critical lines of SCCM CB fast notification channel server log BGBServer.log.
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.
Let’s discuss the SCCM CB 1708 Preview Upgrade Video Guide New Features. SCCM CB preview version 1708 has been released.
I enjoy upgrading my lab environment to the SCCM CB 1708 preview version. However, upgrading to SCCM CB preview version 1708 will fail if you have an SCCM primary server in passive mode.
It would help if you remembered that the SCCM ConfigMgr CB technical preview version should not be deployed to a production environment. This post will see the SCCM CB 1708 Preview Upgrade Video Guide. You can find the YouTube video tutorial here.
The SCCM CB preview version is similar to the Windows Insiders program, which helps SCCM admins test the new features of SCCM CB. Before installing this technical preview, you can review the limitations of the SCCM CB version here.
We can’t install the CAS version of SCCM CB with the preview version. The prerequisite for installing the SCCM CB 1708 preview version has not changed.
SCCM CB 1708 Preview Upgrade Video Guide New Features – Fig.1
How to Download SCCM CB Preview Version
The upgrade process is explained in the video tutorial here. Have you installed an SCCM CB preview version? If not, you can download the latest baseline version of ConfigMgr SCCM CB Technical Preview from here. One particular version of the SCCM preview has a maximum validity of only 3 months (90 days).
How to Upgrade from SCCM CB 1707 to 1708?
The SCCM CB update and servicing process are the same as before. Once the latest version of the preview is released, the update will be available in the SCCM console.
The update will automatically download to your server. This behavior depends on the Service connection point (SCP) mode. There are two modes for SCP: ONLINE and OFFLINE.
The next upgrade process step is the replication of new content to secondary servers. Once replication is completed successfully, the update component will start the prerequisite checks on the SCCM CB hierarchy. The prerequisite checks will run on all the site servers and site systems.
Detailed Status for the SCCM Technical Preview 1708
Details
Installation
In progress
Start WMI
Completed
Install Services
Not Started
SCCM CB 1708 Preview Upgrade Video Guide New Features – Table 1
SCCM CB 1708 Preview Upgrade Video Guide New Features – Fig.2
Once prerequisite checks have been completed, the update component will start the actual upgrade/installation process of SCCM CB 1708. After the upgrade process, the post-installation or upgrade process will begin. All these are explained in the video tutorial here.
New Features of SCCM CB 1708 Preview Version
One of the newest features added to SCCM CB 1708 is the ability to create and run scripts with optional parameters. This script deployment is done through SCCM CB’s new fast channel.
Supported Scenarios of Run Script Option Scenarios
There is no need to deploy the script as a package or application; rather, you can directly import the PowerShell script. This Script can be targeted to collections or devices without creating any deployment.
Create and run PowerShell scripts on collections of devices from the Configuration Manager console.
Create and run PowerShell scripts with parameters to devices and collections from the Configuration Manager console.
Create and run PowerShell scripts with optional parameters to devices and collections from the Configuration Manager console.
SCCM Infra Management insights is another option in SCCM CB 1708. This will give you valuable insights into your environment’s current state based on the data analysis in the site database. This will provide the details of EMPTY collections and applications without deploying your environment.
You can view the management insights below – \Administration\Overview\Management Insights.
Scenarios: Review a management insight to understand your environment better and take action based on the insight
SCCM CB 1708 Preview Upgrade Video Guide New Features – Fig.3
The two new features added to SCCM CB 1708 are initiating restarting computers from the admin console and the pending restart column. The restart computer action is also performed through SCCM fast channel notification.
The monitoring workspace in the SCCM CB 1708 console shows a different name for the Restart computer action: Operation Name #17.
SCCM CB 1708 Preview Upgrade Video Guide New Features – Fig.4
References
Update 1708 for Configuration Manager Technical Preview Branch – Available Now! – here.
Capabilities in Technical Preview 1708 for System Center Configuration Manager – 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 discuss the Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706. I continue to produce comparison videos with every production release of SCCM CB.
This post helps you go through the “Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706.” The previous week was busy because of the SCCM CB preview and production version release.
Being on a business trip didn’t stop me from upgrading my LAB environment to the SCCM CB 1706 production version. In this post, you will find all the details of the Feature Comparison Video between SCCM ConfigMgr CB 1702 and 1706.
The post provides a look at the differences and improvements between the two versions, helping you understand what has changed and how the updates can benefit your system management.
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706
In the comparison video tutorial, we see the SCCM console GUI changes. What are the new nodes added to the 1706 console? We also see some deep dives into new features, tools, and settings introduced in the SCCM CB 1706 version.
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706
Console
SCCM CB 1706
Version
1706
Console version
5:00.8540.1300
Site Version
5.0.8540.1000
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706 – Table 1
Console – SCCM CB 1706 = Version 1706
Console version: 5:00.8540.1300
Site Version: 5.0.8540.1000
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706 – Fig.1
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706
There are 24 Features in SCCM CB 1706, whereas only 21 in 1702. 3 new features were added in SCCM CB 1706 production release. The important point to note here is some pre-release features are still not ready for production release.
These are Cloud Management Gateway, Server Groups, TS Pre-Caching Device Guard, and Client Peer Cache, which are still in pre-release.
The new features introduced in SCCM CB 1706 are Create and Run Scripts, Surface Driver Updates, and PFX Create.
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706 – Fig.2
Compare the New Tools and Features of SCCM CB 1706
Client Peer Cache support for express installation files for Windows 10 and Office 365. There are improvements for SQL Server Always On Availability Groups.
Update Reset tool is released with the SCCM CB 1706 production version. The CMUpdateReset.exe tool helps to fix issues when in-console updates have problems downloading or replicating content to primary servers.
The SCCM CB 1706 production release includes improvements for software update points working with boundary groups.
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706 – Fig.3
You have improved the integration of SCCM and Azure AD (AAD). These improvements streamline how you configure the Azure services you use with SCCM and help you manage clients and users who authenticate through Azure AD.
There are some new Compliance Settings (Configuration Items) for Windows 10 Intune-managed clients. The updated/improved categories are Password, Device, Store, and Microsoft Edge.
Android for Work configuration items for the Allow data sharing between work and personal profile settings descriptions have been updated.
NEW Compliance Policy Rules in SCCM CB 1706 Production Version
The following are very important compliance policies available in the SCCM CB 1706 version. Required Password Type—Either Alphanumeric or Numeric is supported for Windows phones, Windows devices, and iOS.
Block USB debugging on Devices, Block apps from unknown sources, and Require threat scan on apps. Compliance policies are supported for Android Devices.
Feature Comparison Video SCCM ConfigMgr CB 1702 VS 1706 – Fig.4
New Additions in Application Management – SCCM CB 1706
We can deploy PowerShell Scripts from the SCCM CB 1706 console. Run scripts on collections of Windows client PCs and on-premises managed Windows PCs. The script runs in nearly REAL TIME on client devices.
NEW MAM Policy setting in SCCM CB 1706 – Block Screen Capture (only for Android), Disable contact sync, and Disable printing. Software Updates – Manage Microsoft Surface driver updates, which is ONLY possible when your SUPs are on SERVER 2016.
SCCM CB 1706 Security Improvement
SCCM CB 1706 can deploy Device Guard policy management. Device Guard is a group of Windows 10 features designed to protect PCs against malware and other untrusted software.
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 ConfigMgr CB 1707 Preview Upgrade Video Tutorial. The SCCM/ConfigMgr CB 1707 preview version was released last week. I enjoyed upgrading my SCCM CB 1706 preview version to 1707.
As expected, this was a straightforward process for me. I didn’t see any issues during the upgrade process of SCCM CB 1707. We see the SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial in this post.
Preview versions of SCCM CB should NOT be deployed to a production environment. This is similar to the Windows Insiders program, which helps SCCM admins test the new features of SCCM CB.
Before installing this technical preview version, you can review the limitations of the SCCM CB version.
SCCM 1707 Preview Guide Upgrade Process and New Feature Overview
In this video, you will find all the details about the SCCM 1707 Preview Guide Upgrade process and an overview of the new features. The guide will walk you through each step of the upgrade process, ensuring you understand how to implement it smoothly.
SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial – Video 1
SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial
The screenshot below provides a comprehensive look at the new features introduced in SCCM 1707, helping you make the most of the latest updates and improvements.
SCCM ConfigMgr CB 1707 Preview Upgrade Video Tutorial – Fig.1
What are the New Features Introduced in the SCCM CB 1707 Preview?
My favorite features of the SCCM CB 1707 preview version are Windows Defender application guard policies for Windows 10 RS3 and PowerShell Script parameter investments.
Client Peer Cache support for express installation files for Windows 10 and Office 365
Surface Device dashboard
Percent of Surfaces
Percent of Surface models
Top five operating system versions
Configure and deploy Windows Defender Application Guard policies for Windows 10 RS3
Add parameters when you deploy PowerShell scripts
Known Issues with SCCM CB 1707 Upgrade
SCCM CB 1707 upgrade process has not changed much. It’s the same as the preview SCCM CB preview upgrades. New features have been introduced in this preview version. There are some known issues with an upgrade when you install a passive primary server.
The issue is the only application for the SCCM environment with 1706 TP and used the site server always-on, a feature that means the passive site server was configured.
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 Upgrade Guide Updates and Servicing Configuration Manager. Microsoft SCCM team released the production version of SCCM 1706. The SCCM 1706 updates are available as an in-console update for previously installed sites that run SCCM CB versions 1606, 1610, or 1702.
The secret is the continuous improvements that Microsoft SCCM PG (Product Group) implemented in SCCM CB. There are loads of things involved in a constant improvement story.
Step by Step Guide Upgrade Process of SCCM CB 1702 to 1706
In this video, you will learn everything you need about upgrading the SCCM Current Branch from version 1702 to 1706. The guide breaks down the process into easy-to-follow steps. You’ll get clear instructions on preparing for the upgrade, running the upgrade, and verifying the upgrade’s success.
SCCM Upgrade Guide Updates and Servicing Configuration Manager – Video 1
What is the Secret of the SCCM Updates and Servicing Model?
This post will examine prerequisite checks during the console update and servicing process. SCCM PG uses feedback and telemetry data to improve prerequisite checks.
SCCM Upgrade Guide Updates and Servicing Configuration Manager – Fig.1
Why are the Prerequisite Checks Important in the Updates & Servicing Model?
Prerequisite checks are essential parts of the SCCM CB updates and servicing framework. Do you know how many prerequisite checks there are in this framework? SCCM CB updates and serves as a prerequisite checker that validates whether the entire SCCM CB infra is ready for an in-place upgrade. Hence, it can ensure a 99% success rate in the promotion.
The release of SCCM CB 1706 includes 62 prerequisite checks. I never knew that the SCCM CB upgrade process involves 62 reviews to ensure that everything is OK before starting the upgrade.
I have listed all the checks included in the production version of SCCM CB 1706. The prerequisite checks cover CAS, Primary servers, and remote site systems servers.
It also includes SQL version, Collation settings, and Replication link verification. SCCM CB prerequisite checks consist of unsupported configurations (NAP, System Health Validation Point) with an SCCM CB environment.
List of SCCM 1706 Prerequisites
Let’s discuss the list of SCCM 1706 Prerequisites. The list below helps you understand the SCCM Prerequisites.
Upgrade Assessment Toolkit is no longer supported
Administrative rights on-site system
Administrative rights on the central administration site
Connection to SQL server on CAS
Check Server Service is Running
Domain Membership
Active Directory Domain Functional Level Checks
Free Disk space on-site server
Pending System Restart
Read-Only Domain Controller
Site Server FQDN Length
Microsoft XML Core Services 6.0(MSXML6.0)
Windows Server 2003-based channel hotfix
Microsoft Remote Differential Compression (RDC) library is registered on the computer specified for SCCM site server installation.
Microsoft Windows Installer
Existing SCCM server component installed on target site server
Firewall Exceptions for SQL Server
Firewall Exception for SQL server (Standalone primary)
SQL server service running account
Dedicated SQL Server Instance
Parent/Child database collation
Minimum .NET Framework version for SCCM
Windows Deployment Tools Installed
User State Migration Tool (USMT) installed
Primary FQDN
Site Code in Use
Verify CAS version
Required SQL Server Collation
Backlogged Inboxes
DP package version
SQL Server Database collation
Share Name in Package
Software Update Point in NLB configuration
Migration active source hierarchy
Unsupported upgrade path
Active Replica MP
Parent Site replication status
Unsupported site system role “Out of band service point.”
The System health Validation point site system role is NO longer supported
Network Access Protection (NAP) is no longer supported
Verify Database Consistency
SQL Server Sysadmin rights
SQL server admin rights for reference site
Site Server computer account administrative rights
SQL Server Version
SQL Server Edition
SQL Server TCP port
Case-insensitive collation on SQL server
Validate FQDN of SQL server computer
Windows Failover Cluster
Windows PE Installed
SMS Provider machine has the same domain as the site server
Custom Client Agent Settings have NAP enabled
Default Client Agent Settings have NAP enabled
SQL Availability group configured for the readable secondary server
SQL Availability group configured for manual failover
SQL Availability group configured on the default instance
SQL Index creates Memory Option
SQL Server Supported version
Unsupported site server operating system version for setup
Unsupported Operating System version for Site System Role
SUP using a Load Balancer(NLB/HLB)is no longer supported
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 SCUP 2017 How to Publish 3rd Party App Patches. I have published a post about installing and configuring the SCUP 2017 preview version.
The SCUP installation process is straightforward. Similar to SCCM, the SCUP console has different workspaces. This post will show how to publish third-party app patches using SCCM SCUP 2017.
The first step is to import a third-party Application Catalog to SCUP 2017. The following are out-of-the-box Partner Software Update Catalogs with the SCUP 2017 preview version.
Adobe Acrobat X, Adobe Acrobat 11, Adobe Reader X, Dell Business Client, Dell Server, Fujitsu PRIMERGY, HP Client, and HPE ProLiant.
SCCM Built-in Third-party Software Update Publishing Feature without SCUP – NO Need for SCUP Anymore
This video provides comprehensive details about the SCCM built-in third-party software update publishing feature, eliminating the need for SCUP. SCCM now offers an easy process for publishing third-party software updates directly within its interface without relying on SCUP anymore.
SCCM SCUP 2017 How to Publish 3rd Party App Patches – Video 1
SCCM SCUP 2017 How to Publish 3rd Party App Patches
We must add third-party applications to SCCM SUP products like Abode, Dell, Fujitsu, and HP. To do so, navigate through SCCM Settings, Configure Site Components, Software Update Point, Products, and Adobe Systems. Inc. – Abode Acrobat.
SCCM SCUP 2017 How to Publish 3rd Party App Patches – Fig.1
SCUP 2017 Publish 3rd Party Apps Updates to SCCM
We are ready to publish the 3rd part of the app updates to SCCM. Right-click on all the updates from SCUP and publish them to SCCM CB.
Select the Automatic option while deploying the 3rd party app updates to SCCM. The automatic option is available only when SCCM integration is selected in SCUP.
Click Automatic to allow updates. The publisher will 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 SCCM. Only the software update definition(metadata) is published if neither threshold is met.
Confirmation
1 Updates were selected for publish
1 Updates were published metadata only
SCCM SCUP 2017 How to Publish 3rd Party App Patches – Table 1
SCCM SCUP 2017 How to Publish 3rd Party App Patches – Fig.2
We also need to Sign all software updates with a new publishing certificate when published software updates have not changed but their certificate has changed.
SCCM Software Update Sync after Publishing 3rd Party Apps
SCCM All Software Update Sync to have the newly added Acrobat 11 and other app product updates in the SCCM console.
We have published one new update from the SCUP console, bringing the total number of third-party updates to five. After the SYNC, SCCM should have five Acrobat updates.
SCCM SCUP 2017 How to Publish 3rd Party App Patches – 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.
Let’s discuss the SCUP 2017 Preview Installation and Configuration Video Guide. Microsoft recently released the preview version of System Center Updates Publisher (SCUP)2017, which adds support for Windows 10 and Windows Server 2016.
SCUP is a stand-alone tool that enables 3rd party applications (non-Microsoft apps) or LOB application developers to manage custom updates.
SCUP can be integrated with WSUS and SCCM. This post will provide a video guide for SCUP 2017 preview installation and configuration.
SCUP 2017 Preview Installation and Configuration Video Guide –Install SCUP 2017 on Server 2016
Those SCUP workspaces are Updates Workspace, Publications Workspace, Rules Workspace, and Catalogs Workspace. You can navigate to “Update Workspace – Overview” and add updated catalogs from partners like Adobe.
SCUP 2017 Preview Installation and Configuration Video Guide – Fig.1
Import 3rd Party Application Catalog to SCUP 2017
Add partner software updates catalogs allow us to download/Import third-party app catalogs like Adobe Acrobat 11 Updates. This initiates the Acrobat11_Catalog.cab file download. As part of the process, we must also accept the catalog’s security validation from a vendor like Adobe System.
Several updates are available in a catalog or cab file, like Acrobat11_Catalog.cab. The Adobe Acrobat 11 update catalog has 20 updates available, similar to Acrobat 11.0.18 Update and Acrobat 11.0.20 Update. All these updates are imported to SCUP.
There are options to edit/customize third-party application updates imported into SCUP. The package information tab has all the details about the location from which the actual source file, like AcrobatUpd11001.msp, will be downloaded.
We can also specify the installation command line, etc., for each update. There are several options to customize each update. The following are the main customization options for each update: the package, Information, Optional Info, Prerequisite, Supersedence, Applicability, Installed, etc.
SCUP 2017 Preview Installation and Configuration Video Guide – Fig.2
SCUP 2017 Integration with SCCM and WSUS
SCUP can be integrated with WSUS and SCCM. One prerequisite for this integration is SCUP and WSUS (+ SCCM) connectivity. This connectivity must publish third-party patch updates to WSUS and then to SCCM.
The SCUP console has a checkbox option to enable publishing updates to an update server (WSUS server). As you explained in the above video, you must create a self-signed certificate for WSUS connectivity. A similar option enables configuration manager (SCCM) integration with SCUP 2017.
SCUP 2017 Preview Installation and Configuration Video Guide – Fig.3
The configuration options and workspaces have not changed in the SCUP 2017 preview version (compared with previous versions of SCUP). I recommend installing WSUS and the SUP component from the SCCM console before connecting the SCUP with WSUS.
As you can see in the screenshot above, the test connection succeeded. However, no signing certificate was detected for the update server. You cannot publish content to the update server without registering a signing certificate.
SCUP 2017 Certificate Export and Import Activities
We need to export the WSUS certificate from MMC and import it to the locations mentioned below. We must also add the signing certificate used for publishing to the following certificate stores on the SCUP and WSUS computers: Trusted Publishers and Trusted Root Certificate Authorities.
The settings for this connection are not saved until we click OK on the Options dialog box.
The WSUS and SCCM connection tests were successful after the certificates were imported to MMC.
Now, we are ready to publish the updates to WSUS. Publish the updates to WSUS and SCCM via SCUP.
SCUP 2017 Preview Installation and Configuration Video Guide – Fig.4
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is 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……………
