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.
Microsoft released the latest version of SCCM 1802 in the fast ring. To get more details, I recommend reading the newest production version of SCCM CB 1802 and the step-by-step upgrade guide.
Also, I believe SCCM CB 1802 helps organizations keep their infra neat and clean with new management insight features. In this post, we can discuss the review of SCCM 1802 new features.
Enabling the third-party update option will cause Software Update Point (SUP) to download the signing certificate used by Windows Server Update Services (WSUS) to sign third-party software updates.
Table of Contents
Third-Party Updates – SCCM 1802 New Feature
If this option is enabled along with the software update client setting, the following local group policy, “Allow signed updates from an intranet Microsoft update service location,” will be created on a local machine.
The client will be configured to allow signed third-party updates, and the signing certificate will be installed in trusted publishers’ certificate stores on clients.
Enable third (3rd) party update support on clients – Enabled configuration by allowing signed third party updates policy and installing WSUS code signing certificate on clients. Enable Third-Party Software Update.
Duplicate Hardware Identifiers Improvement – SCCM 1802 New Feature
Navigate through SCCM console Administration – Site Configuration – Sites -Hierarchy Settings Properties – Client Approval and Conflicting Records. Some hardware is known to have duplicate IDs. Add them to the list so SCCM can ignore these PXE boot and client registration hardware IDs.
Add Duplicate Hardware ID – Specify the type of hardware ID and the value to include as a known duplicate. This ID will be ignored for PXE and client registration.
Duplicate Hardware Identifiers Improvement – SCCM 1802 New Feature
1. MAC address (12 hex characters)
2. SMBIOS GUID (32 hex characters)
Video Review of SCCM CB 1802 New Features – Table 1
Console Experience – SCCM 1802 Features
The primary user assigned to a device is available in the SCCM CB 1802 console. Navigate Assets and Compliance—Overview—Devices—Primary User(s).
Encryption Options – SCCM CB 1802 New Features
Configure client computers’ signing and encryption requirements when communicating with the SCCM site server. SCCM Clients always sign their client identification when communicating with the Application Catalog website.
Require Signing -Enabled by Default -This option requires that it’s signed when clients send data to management points.
Require SHA-256 -Enabled by Default – When clients sign data and communicate with site systems using HTTP. This option requires the client to use SHA-256 to sign the data. The client must support the SHA-256 hash algorithm to use this option. This option applies to clients that do not use PKI certificates.
Use Encryption – NOT enabled by default – This option uses 3DES to encrypt the SCCM client inventory data and state messages sent to the Management Points.
Video Review of SCCM CB 1802 New Features – Fig.1
Site Infrastructure Improvements – SCCM 1802 New Features
Let’s discuss the Site infrastructure Improvements – SCCM 1802 New Features. The list below will help you to see more details.
Reassign distribution point
Configure Windows Delivery Optimization(DO) to use SCCM boundary groups (Client Settings option)
Support for Windows 10 ARM64 devices
Improved support for CNG certificates
Boundary group fallback for management points
Cloud distribution point site affinity
Client Management Improvements – SCCM CB 1802 New Features
Let’s discuss the Client Management Improvements – SCCM CB 1802 New Features. The list below will help you to see more details.
Cloud management gateway support for Azure Resource Manager
Configure hardware inventory to collect strings larger than 255 characters
Surface device dashboard
Primary User Details in the SCCM console
Change in the Configuration Manager client install – No Silverlight installed
Application Management Improvements – SCCM CB 1802 New Features
Let’s discuss the Application Management Improvements – SCCM CB 1802 New Features. The list below will help you to see more details.
Allow user interaction when installing an application
Do not automatically upgrade superseded applications
Approve application requests for users per device
Run scripts improvements
SCCM CB Operating System Deployment Improvements
Let’s discuss the SCCM CB Operating System Deployment Improvements. The list below provides more details.
Windows 10 in-place upgrade task sequence via SCCM cloud management gateway (CMG)
Improvements to Windows 10 in-place upgrade task sequence
Improvements to operating system deployment
Deployment templates for task sequences
Phased deployments for task sequences
Software Center Changes – SCCM CB 1802 New Features
Let’s discuss the Software Center Changes – SCCM CB 1802 New Features. The list below will help you to see more details.
Install multiple applications in the Software Center
Use Software Center to browse and install user-available applications on Azure AD-joined devices.
Hide installed applications in the Software Center
Hide unapproved applications in the Software Center
Software Center shows users additional compliance information
Video Review of SCCM CB 1802 New Features – Video 1
SCCM 1802 – Site System Server Roles
Let’s discuss the SCCM 1802 – Site System Server Roles. The list below will help you to see more details.
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Let’s learn about Reset SCCM CB Critical Site Component Status Summarizer Counter ConfigMgr.We don’t like red alerts in SCCM monitoring nodes, especially those related to critical site Component status.
We can reset the SCCM site status message count on any component or site system to remove the red alerts from the console. However, I won’t recommend resetting the SCCM component or site system summarizer counter.
Instead, you need to check and understand why the SCCM site status summarizer contains a critical alert.
Check out the video tutorial on resetting the SCCM CB Critical Site Component Status. As mentioned above, I don’t recommend resetting the site or component status summarizer counter before fixing the issue. If you have a critical site status, then fix the issue before resetting the counter.
Table of Contents
Why Reset the SCCM Site Status Summarizer Counter?
SCCM/ConfigMgr site and component status message counts are automatically reset at the end of threshold periods. As part of troubleshooting, we may need to reset the counters to confirm whether everything is okay.
\Monitoring\Overview\System Status\Site Status
\Monitoring\Overview\System Status\Component Status
What is the SCCM Site Component Status Summarizer?
SCCM Status Summarizer helps admins determine the health or status of different SCCM/ConfigMgr CB Infrastructure aspects. The SCCM site and components status summarizers get input from status messages, states, and counts.
What are the Options for Reconfiguring the SCCM Site & Component Status Summarizers?
Application Deployment Summarizer – The application deployment summarizer can be used to get SCCM clients’ application deployment status. To Configure application deployment summarize.
What are the Options for Reconfiguring the SCCM Site & Component Status Summarizers?
Navigate via \Administration\Overview \Site Configuration\Sites – click on the status summarizer ribbon button.
In the Status Summarizers dialog box, click Application Deployment Summarize and Edit.
In the Application Deployment Summarizer Properties dialog box, configure the required summarization intervals and then click OK.
Reset SCCM CB Critical Site Component Status Summarizer Counter ConfigMgr – Table 1
Reset SCCM CB Critical Site Component Status Summarizer Counter ConfigMgr – Fig.1
Default Settings of Application Deployment Summarizer Frequency of status updates for deployment was modified in the last 30 days Number of Minutes: 60. The frequency of status updates for deployment was altered in the last 31 to 60 days. Number of Hours: 24. The frequency of deployment status updates was modified over 90 days ago. Number of days: 7
The Application Statistics Summarizer specifies how often application statistics should be updated. Intervals are based on the date the application was last modified. To change the application Statistics Summarizer configuration, follow the same steps mentioned above.
Summarization Frequency Frequency of the status updates for deployment was last modified in the last 30 days Number of minutes 240 Frequency of the status updates for deployment was later changed in the previous 31 to 90 days Number of hours 240 Frequency of the status updates for deployment was last modified over 90 days Number of days 7
Component Status Summarizer allows the setting of a threshold for each SCCM component. There are two (2) types of thresholds: the warning threshold and the critical threshold. We have options to disable SCCM status summarization for component status. Also, there are options to set the component status replication priority to the parent site.
To change the component Status Summarizer configuration, follow the same steps mentioned above to change the configuration.
Site System Status Summarizer allows disabling status summarization for site system status. It also allows you to set the replication priority of site system status for the parent site in your SCCM hierarchy. It gives the option to set a status summarization schedule. However, I have never used this option.
How to Reset the Critical Site or Component Status Summarizer Counters
The site System summarizer threshold allows you to specify the free space for displaying warning or critical icons in the site system. To change the configuration of Site System Status Summarize, follow the steps mentioned above.
Reset SCCM CB Critical Site Component Status Summarizer Counter ConfigMgr – Fig.2
The site and component status summarizer count can be reset from the SCCM console monitoring workspace. This will help eliminate some red alerts from your SCCM monitoring console.
How Do You Reset the SCCM Critical Site Status Summarizer Counters?
\Monitoring\Overview\System Status\Site Status
Open the SCCM CB console
Navigate via \Monitoring\Overview\System Status\Site Status
Select the site status message you want to reset
Click on the ribbon – Reset Counts icon
As you can see in the video tutorial, click the Refresh button to make RED alerts GREEN.
How Do You Reset the SCCM Critical Component Status Summarizer Counters?
\Monitoring\Overview\System Status\Component Status
Open the SCCM CB console
Navigate via \Monitoring\Overview\System Status\Component Status
Select the component status message you want to reset
Click on the ribbon – Reset Counts icon
As you can see in the video tutorial, click the Refresh button to make RED alerts GREEN.
Reset SCCM CB Critical Site Component Status Summarizer Counter ConfigMgr – Video 1
Resources
Status Message Queries – Track Who Deleted Modified Changed SCCM Settings
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
SCCM Management Insights Clean Healthy SCCM CB Environment Configuration Manager ConfigMgr. SCCM CB Management Insights is one of my favorite features. However, it is not listed in the features list in the SCCM CB 1802 console.
However, management insights were by default enabled in 1802 and later. Trust me, it is very useful to keep your environment neat and clean. As a central admin of a global SCCM team, I will love this feature.
In the previous post, I provided tips and tricks for maintaining an SCCM environment. My honest recommendation is to read those to get more details about SCCM health. MGMT insights is another way to track the health and tidiness of your SCCM environment.
Table of Contents
What is Management Insights in SCCM?
Management Insights is similar to a robotic assistant that will keep an on your SCCM environment for you and let you know the details. Who is not following your standard processes? Who is doing wrong or not recommended things within your SCCM hierarchy?
Management insight helps to gain valuable insights into the current state of the SCCM CB environment based on analysis of data in the site database. I assume the SCCM product group will provide an option to create custom management insights in the future. The Management Insights feature was introduced with the SCCM CB 1708 preview version.
What are the Features of Management Insights in SCCM?
We have five (5) built-in management insights options in SCCM CB 1802. Let’s take a look at those in detail. The below table helps you to show more details.
What are the Features of Management Insights in SCCM?
Software Center – Insights for managing the software center
Applications – Insights for your application management
Simplified Management – Insights that help you simplify the day-to-day management of your SCCM environment
Collection – Insights that help simplify your management by cleaning up and re-configuring collections
Cloud Services – Modernise and simplify your management infrastructure by leveraging the power of the cloud. SCCM is integrated with many cloud services, enabling more straightforward and more modern management of your devices.
Software Center – Insights for Managing Software Center
Software Center helps you get information and insights into software center versions available in your SCCM environment. A couple of out-of-the-box rules are created to find software center versions. Also, it helps to clean up the old version of SCCM software center and learn how to get new software center versions.
Rule 1 – Direct your user to the software center instead of the application catalog Rule 2 – Use the new version of the Software Center
The application catalog is depreciated, and you should deploy the new version of the software center – More details in Microsoft documentation.
Applications – Insights for Your Application Management
Application management options in management insight can help you find evil things happening within the application creation world. Using this feature, let’s clean up the OLD applications in your SCCM environment. This helps to keep the health of all your application echo systems.
Rule 1 – Applications without deployments
Simplified Management – Simplify the Day to Day MGMT of Your Environment
SCCM simplified management rule in the SCCM management insight feature helps to find out the non-SCCM CB client versions in your environment. This will help to keep your SCCM environment healthy and updated.
Rule 1 – Non-CB Client Versions
Collection – Simplify Device Management
SCCM management insights help simplify device management options for your organization. The following rule of MGMT insights helps you keep an eye on your environment’s collections. This helps you clean up and reconfigure collections.
Cloud services management insights are to get more details about modern management scenarios. One of the key modern management scenarios is enabling and keeping track of the co-management features.
Modernise and simplify your management infrastructure by leveraging the power of the cloud. SCCM is integrated with many cloud services, all of which enable simpler and more modern device management.
Rule 1
Assess co-management readiness. There are three (3) prerequisites for co-management. 1. Update clients to the latest Windows 10 version, 2. Configure Azure Services for use with SCCM and 3. Enable Devices to be hybrid Azure Active Directory Joined.
Rule 2
Configure Azure Services to use with SCCM
Rule 3
Enable Devices to be hybrid Azure Active Directory joined
Rule 4
Update Clients to the latest Windows Version
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Update: Microsoft already tweaked SCCM 1802 not to block upgrades for DPs running Windows 2008. Here is Djam’s tweeton this topic.
The 1802 production upgrade process should be initiated from top-level sever CAS or stand-alone primary. This upgrade process automatically upgrades Primary child servers and remote systems system servers (MP, DP, and SUP).
SCCM CB secondary site servers are not supported for automatic upgrade. I also produced a quick review after the SCCM CB upgrade to 1802 in this post.
Table of Contents
Step by Step SCCM CB upgrade to 1802 Primary Standalone – SCCM Primary Upgrade Video Guide
The 1802 production upgrade process should be initiated from top-level sever CAS or stand-alone primary. This upgrade process automatically upgrades CAS, primary servers, and remote system servers.
It does not support the automatic upgrade of SCCM CB secondary site servers. I also produced a quick review after the SCCM CB upgrade to 1802 in this post.
Step by Step Video to Perform SCCM 1802 Upgrade Configuration Manager ConfigMgr – Video 1
SCCM CB 1802 is the latest (NEW) baseline build. You can download SCCM CB 1802 from MSDN or the Volume Licensing portal. Once the 1802 baseline build is downloaded, then you can build a new SCCM infra with 1802. There are two scenarios where you can use the baseline version.
What is the Latest Baseline Build for SCCM CB?
I recommend using the following checklist before starting the SCCM CB upgrade process. For more details about the SCCM 1802 checklist, click here.
Use the latest baseline version when installing a new site in a new hierarchy.
SCCM CB 1802 Baseline version to upgrade from SCCM 2012
Plan the upgrade of remote SCCM CB 1802 consoles or the console published in Citrix. Even though SCCM CB 1802 supports a 1710 console.
Ensure that all sites run a version of SCCM that supports updates to 1802. The minimum supported version for the SCCM CB 1802 upgrade is 1702. If your existing SCCM CB environment is not 1702 or later, you won’t get the SCCM CB 1802 production update in the console.
Review the Windows ADK version for Windows 10—Make sure your Windows 10 ADK version is 1709 or later. I recommend updating the Windows ADK 1709 before the SCCM CB 1802 upgrade. This helps the default boot images get automatically updated to the latest version of Windows PE. Also, remember that the custom boot images must be updated manually.
Review the backlog of File and SQL-based Replication
Disable database replicas for MP at primary sites (Also, SUP with NLB)
Set SQL Server AlwaysOn availability groups to manual failover
Disable site maintenance tasks (backup, delete an aged client, and delete old discovery) at each site (primary and CAS)
Temporarily stop any antivirus software
Create a backup of the site database at the SCCM CAS and primary sites
Plan and Use client piloting for a newer version of the SCCM CB 1802 client
How to Start SCCM 1802 Upgrade
I hope you have already gone through before going through the upgrade process. Login to CAS or a stand-alone primary server and launch the SCCM CB console. Navigate the SCCM console via – Administration > Overview > Cloud Services > Updates and Servicing. Make sure you right-click and select “Install Update Pack”.
You can go through the Wizard, as I showed in the SCCM CB 1802 upgrade video tutorial. But remember to select pilot collection for new client version deployments. The following is a sample summary of my lab’s SCCM CB 1802 update package installation.
Success: Install Update Package Configuration Manager 1802 Prerequisite warnings will be ignored Turn on the following features: • Approve application requests for users per device • Enable third-party update support for clients • Support for Cisco AnyConnect 4.0.07x and later for iOS • Phased Deployments Test a new version of the client in the pilot
Find Out SCCM CB Update Stage IDs and Stage Names
SCCM CB 1802 production Upgrade process is straight, as you can see in the video tutorial for the 1802 upgrade. Check the status from the monitoring workspace (\Monitoring\Overview \Updates and Servicing Status\Configuration Manager 1802) and the logs.
If you have trouble downloading the SCCM CB 1802 production update, refer to my previous troubleshooting guide. The SCCM 1802 Upgrade is usually super easy, but in this case, it requires fixing the SCCM CB update Redist Download Issue.
Stage Id
Stage Name
10
Download
11
Replication
12
Prerequisite Check
13
Installation
14
Post Installation
Step by Step Video to Perform SCCM 1802 Upgrade Configuration Manager ConfigMgr – Table 1
SCCM CB 1802 Versions
All the features available in the SCCM 1802 preview version are unavailable in the production version of SCCM 1802. This is expected, and I noted this in the SCCM CB 1802 preview post. I’m pointing out the features listed below in the SCCM console.
SCCM CB 1802 Version 1802
SCCM CB 1802 Console Version 5.1802.1082.1700
SCCM CB 1802 Site Version 5.0.8634.1000
SCCM CB 1802 Build Number 8634
SCCM CB 1802 Client Version 5.00.8634.1007
Features Overview of SCCM 1802 Production Release
The SCCM CB 1802 production release has five (5) pre-release features and Fifteen (15) production features. Management Insight is one of the exciting features missing from the SCCM 1802 production release (at least from the SCCM console features GUI), but it is available on the product.
\Administration\Overview\Updates and Servicing\Features
Five(5) Pre-Release Features of SCCM CB 1802 Production Release
What is the SCCM Data Warehouse Service Point? Use the data warehouse service point to periodically copy data from your SCCM site database to another DB for long-term storage and trend analysis.
Windows Defender Application Control
Phased Deployments
Enable third (3rd) party update support on clients
Server Groups
Support for Cisco AnyConnect 4.0..7x and later for iOS
Fifteen(15) Release Features of SCCM CB 1802 Production Release
Let’s discuss the Fifteen(15) Release Features of the SCCM CB 1802 Production Release. The list below will help you to see more details.
PFX Create
Passport for Work
Windows Defender Exploit Guard Policy
Surface Driver Updates
OMS Connector
Device Health Attestation assessment for compliance policy for CA
Create and Run Scripts
Client Peer Cache
Approve Application requests for Users per Device
Run Task Sequence Step (Promoted)
Conditional Access for Managed PCs
Task Sequence Content Pre-Caching
Data Warehouse Service Point
Cloud Management Gateway
VPN for Windows
Not Listed Features?
Let’s discuss the Not Listed Features. The list below will help you to see more details.
Reassignment Distribution Point (The feature is by default enabled and removed from the features list)
Add a passive primary site server.
Surface Device Dashboard ( The feature is by default enabled and removed from the features list)
Management Insights ( The feature is by default enabled and removed from the features list)
Office 365 Support Volume Licensing SKU in C2R Wizard
Passport for Work ( The feature is by default enabled and removed from the features list)
Quick Explanation about New Features of SCCM 1802 Production Release
What is SCCM Cloud Management Gateway (CMG) – SCCM CMG Provides a simple way to manage SCCM clients on the Internet. The gateway server (Azure PaaS) is deployed to Microsoft Azure. This Connects internet clients to your on-premises SCCM infrastructure.
Windows Defender Application Control – Windows Defender Application Control helps lock down Windows 10 computers so that they can only run trusted software.
What are SCCM Phased Deployments – Phased Deployments automate a coordinated, sequenced roll-out of software across multiple collections
Enable third (3rd) party update support on clients – Enabled configuration by allowing signed third party updates policy and installing WSUS code signing certificate on clients.
Client Settings Changes After SCCM 1802 Upgrade
There are two (2) types of client setting policies. User Client Settings and Device Client Settings are two of them. However, there is one mother of client settings policy, and that is called Default Client Settings. Windows Analytics setting is only available in default policies.
22 categories are there in SCCM CB 1802 Default Client Settings Policies
20 categories are there in SCCM CB 1802 Device Client Setting (User and Device Affinity are missing)
3 categories are there in SCCM CB 1802 User Client Settings (Cloud Services, Enrollment, and User & Device Affinity)
Co-Management Changes – SCCM 1802 Production Release
For Windows 10 devices that are in a co-management state, you can have Microsoft Intune start managing different workloads.
Choose pilot Intune to have Intune Manage the workloads for only the clients in the pilot group. If you are not ready to move the workload to Intune, select SCCM (ConfigMgr). More details here.
You can move the co-management workloads with SCCM, Intune, or both. We can offload four (4) workloads to Intune. Endpoint protection (Windows Defender ) is newly added to the SCCM 1802 production version. I have a post about the co-management strategy.
Compliance Policies – Intune Compliance Policies
Resource Access Policies – Intune WiFi and VPN Profiles
Windows Update Policies – Windows Update for Business – Patching
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Let’s learn how to fix Microsoft SCCM Intune Documentation Configuration Manager ConfigMgr. How many of us complain about SCCM Intune documentation?
The documentation is not updated, relevant, etc. Here is the real opportunity to help yourself and update the SCCM and Intune documentation.
But don’t worry about the quality of the SCCM Intune documentation, as there are several steps to validate before your edits/changes are published. Hack a doc is the theme of this post 😉
We had a great MVPHackaDocsession with Aaron during the MVP Summit 2018. All the credits to Aaron taught me how to update SCCM/Intune documentation. I don’t recommend going around and editing or updating all the documentation. But start small before you leap.
Start Small
Learn to Fix Microsoft SCCM Intune Documentation – Video 1
The Microsoft documentation service (https://docs.microsoft.com) is hosted on the GitHub platform, which improves the user experience while reading the documentation.
Even SCCM and Intune documents have been migrated to a new platform. The following is my list of key features of the new docs on the Microsoft platform.
Readability
Estimated Reading Time
Content and Site Navigation
Shortened Article Length
Responsive Design
Community Contributions
Social Sharing
Friendly URLs
How to Start Updating SCCM Intune Documentation?
I hope you read a lot of Microsoft documentation every day. You found the wrong article and want to inform the Microsoft Doc team about this incorrect information.
If you don’t have one, create one. It took me one and two minutes to do so.
You can select the GitHub Free plan during the signup process and tailor your experience to include a short introduction about yourself.
Open the article you identified and click the EDIT button, as I showed in the video tutorial. You should open the article from the same browser you are already logged in to from your GitHub account.
Once you click on the EDIT button on that article, it will redirect to the GitHub editor.
You will perform all the updates in the GitHub editor.
Identify the Article and Start Contributing
How to Contribute to SCCM Intune Documentation
As Aaron mentioned in his “MVP Hack a Doc” session, start small. Standard GitHub accounts may not have access to edit live document code. And you will get the following error when you try to edit or update an article.
You’re editing a file in a project you don’t have write access to.
Submitting a change to this file will write it to a new branch in your fork.
AnoopCNair/SCCMdocs so that you can send a pull request.
As I have shown in the “Hack A Doc“ video, A perfect example of raising an issue from Jason. He raised a problem and a documentation BUG was filed to fix this issue.
I also tried creating a pull request, but I think that requires more access to edit the master file. A normal GitHub account may not have access to proceed with a pull request.
Another interesting thing I learned was how to select the best title, title suffix, description, and ms. Custom, ms. Date, and Ms. Prod for technical articles. As Aaron suggested, we can start doing the following things:-
Start Doing the Following Things
Clarifications
Examples
SDK, PowerShell
Guidance tips
Translations
See something, fix something
Learn to Fix Microsoft SCCM Intune Documentation – Table 1
I have tried raising an issue with documentation, which is the best and easiest part I learned during the MVPHackaDoc session. I have more details about the problems raised in Hack A Doc’s video tutorial.
Another useful option trying to try to track the documentation issues with th GitHub account. So we can rest assured that Microsoft is aware of this bug and will fix it soon. Following is the file structure of the GitHub article (for example) SCCMdocs/sccm/core/plan-design/hierarchy/accounts.md .
Start Contributing = Raising an Issue
Learn to Fix Microsoft SCCM Intune Documentation – Fig.1
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Free LinkedIn Learning Courses for SCCM Intune. I agree with the following sentence, so I’m sharing my experience with LinkedIn learning. Microsoft MVPs are notorious for passionately sharing their knowledge with the world.
In this post, we will learn about free LinkedIn learning courses available for SCCM and Intune (Learn SCCM Intune).
SCCM is great, and it will not die, as per Microsoft. But don’t abandon Intune learning. I strongly recommend going through the Intune learning process.
Microsoft MVPAward program celebrated its 25th anniversary. As part of the 25th-anniversary celebrations, LinkedIn unlocked 15 Courses Covering Key Technology Skills. The following is the list of 15 courses that LinkedIn has unlocked. This post will discuss more details about SCCM and Intune free study materials.
Table of Contents
Introduction
I have a full-blown post about systematic learning of SCCM and Intune. The approach to learning should be the same as I mentioned in the post, which was published back in 2015. I learned SCCM the hard way. There was no one to handhold and teach me.
Great Learning – What to Learn Intune? Great Resource Around you!
Free LinkedIn Learning Courses for SCCM Intune – Table 1
My Favourites Microsoft System Center Configuration Manager… SCCM CB Learning Microsoft Enterprise Mobility Suite (Azure AD and Intune) Office 365 for Administrators: Supporting Users Part 1 Windows 10: Deploy and Manage Virtual Applications Productivity Apps Excel 2016: Get & Transform PowerPoint: Designing Better Slides OneNote Tips and Tricks Visio Tips and Tricks Automation & Developer Microsoft Graph for Developers API Development in .NET with GraphQL ASP.NET Core: Razor Pages ASP.NET Core New Features Microsoft Cybersecurity Stack: Advanced Identity… Microsoft Cloud Services: Troubleshooting Online… Building and Securing RESTful APIs in ASP.NET Core
I never got a chance to attend training before being pushed to work on SCCM. That is a different experience, as I explained in the future of SCCM/Intune jobs post.
How Do You Get Access to Free SCCM and Intune Video Courses?
These 15 courses are free only for a limited period. As per the MVP Award program post, they are unlocked for the general public until the middle of April! So don’t waste time—start learning SCCM/Intune using LinkedIn study materials.
In the video tutorial here, I explain how to start learning through LinkedIn courses. However, the SCCM course won’t work from the following link. I recommend using the link I provided in the next section of the post.
No need to log in to LinkedIn to access these courses (anonymous access is allowed)
Open any of the 15 free courses available
Free LinkedIn Learning Courses for SCCM Intune – Fig.1
Start Free SCCM Online Course
To start the cause, you don’t need to log in with your LinkedIn account. Also, you don’t need to start the trial version of LinkedIn learning for a month. You can access the SCCM course from a private browser without logging in.
To start the Free SCCM online course from a private browser
Content of the SCCM CB Course
Introduction (More details about SCCM CB content at the bottom of the post)
Planning and Deploying a Standalone Primary Site
Designing and Deploying a Multiple-Site Hierarchy
Planning Resource Discovery and Client Deployment
Managing Content and Replicating Data in Configuration Manager
Configuring Internet and Cloud-Based Client Management
Maintaining and Monitoring SCCM CB
Upgrading to SCCM CB Conclusion
Start Free Intune Online Course
Intune course is part of EMS. So, the EMS course includes both Azure AD and Microsoft Intune. I have an Intune starter kit that can help you start learning Intune from scratch. More details are available in the Intune guide for beginners in the enterprise mobility world.
Start the course Directly from the following link
Content of the Intune Course
Microsoft Intune
With Intune, you can easily manage apps and devices. You can also configure Intune to manage iOS and Android. More details are explained below.
Manage apps and devices with Intune – 3m 30s
Configure Intune to manage iOS and Android – 4m 0s
Build and deploy a basic policy for iOS or Android – 5m 17s
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Let us learn about SCCM Audit Status Messages Track Who Deleted Modified Changed Settings. Track Who Deleted Modified Changed SCCM Settings (SCCM Audit Status Messages) Configuration Manager ConfigMgr.
SCCM Audit status messages are constructive in tracking who did what in your SCCM environment. The Audit Status messages will help you get answers for most of the unforeseen issues in the SCCM environment.
This post will show how to track who deleted, modified, or changed SCCM Settings. It’s important to note that SCCM Current Branch (CB) Audit status messages are purged from the database after 180 days.
All these SCCM audit status messages are under the MessageType = 768. I have uploaded a YouTube video to explain the process of audit reporting.
Table of Contents
SCCM Audit Status Messages Track Who Deleted Modified Changed Settings – Video 1
This Post will Give you Answers to the Following Questions
I have explained the best ways to look at the audit status messages. I think this will help you to track down the culprit. There are three (3) ways to track down and analyze SCCM CB audit status messages.
Who created/deleted Azure Services?
Who Approved the Script?
Who started the download of updates and the Servicing package?
Who deleted the collection? Who removed the member of a collection? Who modified the collection query?
Who deployed/deleted the application package or Task Sequence?
Who removed/modified the Boundary or Boundary Group?
Who installed/deleted site system server roles?
Who changed/deleted the client settings?
Who took the remote control of the machine?
In this post, I will explain how to review SCCM audit status messages using different methods.
Status Message Queries
SCCM SSRS Audit Reports
SQL Management Studio
SCCM Audit Status Messages Track Who Deleted Modified Changed Settings – Table 1
Review Audit Status Messages with Status Message Queries
The SCCM CB console has 17 out-of-the-box audit status message queries. These queries are built into the SCCM system, so you don’t need to create them manually.
Launch the SCCM console and navigate via \Monitoring\Overview\System Status\Status Message Queries. Make sure you filter the status message queries with AUDIT.
You have the following options for each query available under SCCM audit status messages. To protect the audit status messages, it is important to follow the proper RBAC policies in your environment.
Examples of these reports are available at the bottom of the post, or you can refer to the YouTube video tutorial here. I have also noted the specific Audit Status message IDs for each category in the following section of this post.
Show Messages – Review/Read the Audit Messages
Delete Messages – Delete the Audit status messages (Important)
Refresh – Refresh the query
Delete – Delete the Query from SCCM (Important)
Set Security Scope – To set security scope for specific audit status message query (Important)
SCCM Audit Status Messages Track Who Deleted Modified Changed Settings – Fig.1
Review Audit Status Messages with SCCM SSRS Reports
There are two ways to access SSRS reports. One from the SCCM console and the other from a web browser. How you prefer to read SCCM audit status message reports doesn’t matter. Your SCCM SSRS report is not working? I have a post that explains the SCCM SSRS reporting service point setup.
There are three (3) main audit status message reports in SCCM CB. All these are default out-of-the-box reports, and you don’t create any of them manually.
56943 – All audit messages for a specific user
42036 – Remote Control – All computers are remote-controlled by a particular user
40238 – Remote Control – All remote control information
Examples of these reports are available at the bottom of the post, or else you can refer to the YouTube video tutorial here. Also, I have noted down the specific Audit Status message IDs for each category in the following section of this post.
Review Audit Status Messages with SQL Management Studio
I prefer this method for advanced troubleshooting scenarios of SCCM audit status messages. However, it is not very useful in typical situations.
The following are the two (2) SQL queries that will help you track down issues related to accidental deployment or deletion in your SCCM environment.
The first query will return all the SCCM status messages related to AUDIT. The second query will return the status messages of a specific scenario. For example, MessageID 30015 is related to Collections Created, Modified, or Deleted.
Select * from vStatusMessagesWithStrings where MessageType = ‘768’
select * from vStatusMessagesWithStrings where component = ‘Microsoft.ConfigurationManagement.exe’ and MessageID = 30015
Meaning of Audit Status MessageIDs
The following list shows all the SCCM audit status message ID details. It is the list as per the latest SCCM CB 1802 (preview version).
Boundaries Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of boundaries.
MessageID >= 40600 and MessageID <= 40602
Client Component Configuration Changes - Audit status messages that track changes to the client components'' configuration kept in the site control file.
MessageID >= 30042 and MessageID <= 30047
Collection Member Resources Manually Deleted - Audit status messages that track the manual deletion of collection member resources by an administrator.
MessageID >= 30066 and MessageID <= 30067
Collections Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of collections.
MessageType = 768 and MessageID >= 30015
Deployments Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of deployments.
MessageID >= 30006 and MessageID <= 30008
Packages Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of packages.
MessageID >= 30000 and MessageID <= 30002
Programs Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of package programs.
MessageID >= 30003 and MessageID <= 30005
Queries Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of queries, including status message queries.
MessageID >= 30063 and MessageID <= 30065
Remote Control Activity Initiated at a Specific Site - Audit status messages that track the use of the Remote Control.
MessageID >= 30069 and MessageID <= 30087
Security Roles / Scopes created, modified, or deleted - Audit status messages that track the creation, modification, and deletion of security rights.
(stat.MessageID >= 31200 and stat.MessageID <= 31202 OR stat.MessageID >= 31220 and stat.MessageID <= 31222 OR stat.MessageID = 31207)
Server Component Configuration Changes - Audit status messages that track changes to the server components'' configuration kept in the site control file.
(MessageID >= 30033 and MessageID <= 30035) or (MessageID >= 30039 and MessageID <= 30041)
Site Addresses Created, Modified, or Deleted - Audit status messages that track the creation, modification, and deletion of site addresses.
MessageID >= 30018 and MessageID <= 30020
Following are the examples of Audit Status Messages
Let’s discuss the examples of Audit Status Messages. The sections below will help you to provide more details.
Message ID Description
30000 User "INTUNE\anoop" created a package named " 1802 Upgrade TS " (TP100020).
30001 User "INTUNE\anoop" modified the Package Properties of a package named " Windows 10 CYOD " (TP10001B).
30003 User "INTUNE\anoop" created a program named "Create Folder" that belongs to a package with package ID TP100012.
30006 User "INTUNE\anoop" created a deployment named "Windows10CYOD_TP10001B_Win10Upgrade" (TP120005) deploying program "*".
30008 User "INTUNE\anoop" deleted a deployment named "Windows10EnterpriseUpgrade_TP10001C_Win10Upgrade" (TP120003) deploying program "*".
30011 User "INTUNE\anoop" removed a package with package ID TP100019 from a distribution point on \\SCCMTP1.Intune.com at site "TP1 - New TP Server 1".
30015 User "INTUNE\anoop" created a collection named "Win10 Upgrade" (TP100017).
30016 User "INTUNE\anoop" modified the Collection Properties for a collection named "Win10 Upgrade" (TP100017). This collection is currently assigned to the following ConfigMgr Administrators: .
30031 User "INTUNE\anoop" modified site definition information in the site control file for site "TP1 - New TP Server 1" (Parent Site Code="").
30034 User "INTUNE\anoop" modified component "SMS_DMP_DOWNLOADER" on SMS Dmp Connector in the site control file at site TP1.
30036 User "INTUNE\anoop" added the role of Reporting services point to the Windows NT Server "\\SCCMTP1.Intune.com" in the site control file at site TP1.
30037 User "INTUNE\anoop" modified the role of the Windows NT Server "\\SCCMTP1.Intune.com" as a Software update point in the site control file at site TP1.
30038 User "INTUNE\anoop" deleted the role of the Windows NT Server "\\SCCMTP1.Intune.com" as a Reporting services point in the site control file at site TP1.
30043 User "INTUNE\anoop" modified client component "Client Component" in the site control file at site TP1.
30068 User "NT AUTHORITY\SYSTEM" updated a package named " Boot image (x64) 10.0.15063.0 " (TP100005) to the site distribution points.
30104 User "INTUNE\anoop" requested that the membership be refreshed for collection "All Systems" (SMS00001).
30108 User "INTUNE\anoop" requested that the CCR be generated for Machine "WIN10-1709-TRY" (2097152003).
30125 User "INTUNE\anoop" added new distribution points to a package named " Win10 en-US" (TP100019).
30152 User "INTUNE\anoop" created configuration item "16785030" (CI_UniqueID=ScopeId_0F705575-4F94-46DA-A1C4-8869FB8C68AD/ConfigurationPolicy_a98d1e90-5949-41e9-abb9-08c8728e1e09, CIVersion=1). .
30160 User "INTUNE\anoop" modified a CategoryInstance "16777553" (LocalizedCategoryInstanceName=Office 365 Client (Product:30eb551c-6288-4716-9a78-f300ec36d72b), CategoryTypeName=Product). .
30186 User "INTUNE\anoop" created the SUM deployment template with TemplateUniqueID "{BEA96FA5-8A7E-455C-AFC5-D9B6839BC35A}" (Name = "New 1802 TS Deployment Template"). .
30196 User "INTUNE\anoop" created updates assignment 16778230 ({96BD5FC5-E4CE-4F89-A2DD-63BBF4134ED6}). .
30197 User "INTUNE\anoop" modified updates assignment 16777225 ({b91576af-7116-4fa5-b1a4-36a1bc9e4ded}). .
30198 User "INTUNE\anoop" deleted updates assignment 16777225 ({b91576af-7116-4fa5-b1a4-36a1bc9e4ded}). .
30209 User "INTUNE\anoop" requested to execute summary task (Calculate EP Antimalware Policy Summary). .
30210 User "INTUNE\anoop" created user account INTUNE\anoop. .
30214 User "INTUNE\anoop" submitted a registration record at site "SCCMTP1.Intune.com - TP1" (SMSID=1c2c6362-ccc4-4c1c-a8ee-d39168e0ada4).
30215 User "INTUNE\anoop" received policies for Task Sequence using Deployment "{55D8F97F-0D35-4FF0-8720-0CDC5AD1F158}".
30216 User "INTUNE\anoop" received client configuration policies.
30219 User "INTUNE\anoop" created authorization list "16783798" (CI_UniqueID=ScopeId_0F705575-4F94-46DA-A1C4-8869FB8C68AD/AuthList_DC06C5C2-4227-4FE9-80E5-12240CBD6B4A, CIVersion=1). .
30220 User "INTUNE\anoop" modified authorization list "16784011" (CI_UniqueID=ScopeId_0F705575-4F94-46DA-A1C4-8869FB8C68AD/AuthList_4fcf3f8f-9679-4aaf-b952-095c60d3896f, CIVersion=2). .
30226 User "INTUNE\anoop" created a deployment of application "Office 365 Client Install" to collection "All Desktop and Server Clients".
30228 User "INTUNE\anoop" deleted the deployment of application "64 Bit PS" to collection "All Desktop and Server Clients".
40300 User "INTUNE\anoop" created client settings object (ID=16777218).
40301 User "INTUNE\anoop" modified client settings object (ID=16777217).
40303 User "INTUNE\anoop" created client settings assignment (SettingsID=16777217, CollectionID=TP100017).
40501 User "INTUNE\anoop" modified Boundary Group "Test1".
40503 User "INTUNE\anoop" created Boundary Group Relationships "16777218" "16777217" .
40600 User "INTUNE\anoop" created Boundary "IPS".
40700 User "INTUNE\anoop" created configuration policy assignment 16778232 ({CF5E4157-A7AC-4E3A-BAEF-12D64109D7B3}). .
40701 User "INTUNE\anoop" modified configuration policy assignment 16778228 ({0D7BEB54-0873-4A8E-8A86-6654976633FB}). .
40800 User INTUNE\anoop initiated client operation 135 to collection INTUNE\anoop.
40801 User INTUNE\anoop initiated client operation 8 to 1 members of collection SMSDM003.
42031 User "INTUNE\anoop" created Auto Deployment Rule "Office 365 Updates New" (AutoDeploymentID = 3).
52200 User INTUNE\anoop updated the state of package A69042F2-64AA-4592-B77A-24FDE17058DF to state 2 with flag 2.
52203 User INTUNE\anoop requested download for package 51D629D3-C355-4B80-AD6F-BA44B27F84ED.
52500 User INTUNE\anoop created Script with Guid 9d85fb2f-2d2e-4cc1-a114-31e882958dae.
52501 User INTUNE\anoop approved script with Guid D7A08315-7731-49B5-9601-BF7268BA98C7.
53401 User INTUNE\anoop created Azure Cloud Service
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Let’s Set up and Configure the SCCM Reporting Services Point. SCCM has rich capabilities for collecting information from endpoints, which is stored in SCCM SQL DB. We can make beautiful reports with the data collected by SCCM.
SCCM has about 500 default reports that are available out of the box. To access these default SCCM reports, you must set up the Configure SCCM CB Reporting Services point.
I have uploaded a video tutorial to cover the following topics regarding SCCM CB Reporting Services.
This post provides all the details of the Setup Configure SCCM Reporting Services Point Configuration Manager ConfigMgr.
Table of Contents
Setup Configure SCCM Reporting Services Point – Video 1
Setup Configure SCCM Reporting Services Point Configuration Manager ConfigMgr
I have a previous blog post listing default SCCM 2012 reports, “List of SCCM 2012 Default Reports“. The table below will help you to see more details.
SQL Server Reporting Services (SSRS) is a SCCM CB reporting services point requirement. The SQL reporting service is part of the SQL Server installation. Ensure that the SSRS component is installed before going to the next step.
Architecture
The reporting services point in SCCM communicates with SSRS to copy SCCM reports to a specified report folder. SCCM will configure the Reporting Service’s general and security settings. Reporting Services connects to the SCCM site DB to retrieve returned data when you run reports.
SQL Server Reporting Services Configuration Checks
Login to the SQL server (or the primary server where the SQL management console is installed) and Launch SQL Server Reporting Services Configuration Manager from the Start menu. Click All Programs, and click Microsoft SQL Server 2014.
Setup Configure SCCM Reporting Services Point – Fig.1
Connect to the SQL Report Server Instance. Make sure the report service status is in the started stage. If not prompted, click on START.
SQL Server Instance: MSSQLServer
Instance ID: MSRS12.MSSQLSERVER
Edition: ENTERPRISE EDITION
Product Versions: 12.0.4100.1
Report Server Database Name: ReportServer
Report Server Mode: Native
Report Service Status: Started 3.
Make sure the reporting server service account is configured correctly and that all the following sections are precisely set up. The YouTube video provides more details.
Web Service URL
Database
Report Manager URL
E-mail Settings
Execution Account
Encryption Keys
Scale-out Deployment
SCCM CB Reporting Services Point Installation and Configuration
Launch the SCCM CB console and navigate via \Administration\Overview\Site Configuration \Servers and Site System Roles. Select the Site system – Add Site System role. In the Add new site system role wizard, select the “Reporting services point” role. Reporting Services Point page configurations
Site Database Server Name: SQL_Server_Name\SQL_Instance_Name
Database Name: CM_TP1
Folder Name: ConfigMgr_TP1
Reporting Services Server Instance: MSSQLSERVER (Default instance)
Reporting Services Point Account: Intune\anoop
The following is the main configuration page for the SCCM reporting services point. Click on the VERIFY button to confirm connectivity with the SQL server and access rights. Then click NEXT—NEXT to finish the wizard.
Setup Configure SCCM Reporting Services Point – Fig.2
Check SCCM CB Reporting Services Point Log Files
Once the SCCM CB reporting services point installation wizard is completed, you can check and confirm the success of the log file installation.
The first log I would prefer to look at is srsrpsetup.log, and make sure the following lines are present at the end of the log file.
Cannot delete old installation directory C:\Program Files\SMS_SRSRP. Error Code=5. The installation will continue. No versions of SMSSRSRP are installed. Installing new SMSSRSRP. No versions of SMSSRSRP are installed. Installing new SMSSRSRP. Enabling MSI logging. srsrp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\srsrpMSI.log Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\srsrp.msi SRSRPINSTALLDIR=”C:\Program Files\SMS_SRSRP” SRSRPLANGPACKFLAGS=0 srsrp.msi exited with return code: 0 Installation was successful. Installation was successful. ~RoleSetup().
The next stage in the SCCM CB reporting services point installation verification is with srsrp.log. This log will take 5 minutes to complete and create all the default reports in SCCM. It shows all the report and folder creation details.
Successfully created srsserver~ $<02-27-2018 12:11:41.899-330> Reporting Services URL from Registry [http://sccmtp1/ReportServer/ReportService2005.asmx]~ $<02-27-2018 12:11:42.049-330> Reporting Services is running $<02-27-2018 12:11:42.073-330> Retrieved datasource definition from the server. $<02-27-2018 12:11:42.120-330> Retrieved datasource definition from the server. $<02-27-2018 12:11:42.340-330> [SCCMTP1.Intune.com] [CM_TP1] [ConfigMgr_TP1] [SCCMTP1.INTUNE.COM]~ $<02-27-2018 12:11:42.358-330> [MSSQLSERVER] [1] [] [INTUNE\anoop]~ $<02-27-2018 12:11:42.480-330> [1] [0]~ $<02-27-2018 12:11:42.603-330> Confirmed version [12.0.4100.1] for the Sql Srs Instance. $<02-27-2018 12:11:43.024-330>
Check the Results – Launch SCCM CB SSRS Default Reports
Let’s wait for some time before launching the report server URL to check the availability of SCCM default reports. You can confirm whether the report creation process is completed from the above log file. There are two methods to access the SCCM SSRS reports.
Launch the reports from the web browser (http://sccmtp1/ReportServer/)
Launch reports from SCCM Console via \Monitoring\Overview\Reporting\Reports
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 from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
