SCCM is device management tool for Windows devices. This is a client server application by Microsoft. How to manage devices with this tool for Windows devices? 90% of corporate Windows devices are managed by the this tool.
SCCM video posts in this blog will help you to understand in a better way. Most of the videos shared in this post are real time experience of this Windows Device managment.
SCCM is the short for System Center Configuration Manager. This tool is a software management suite provided by Microsoft that allows users to manage a large number of Windows based computers.
This tool features remote control, patch management, operating system deployment, network protection and other various services. Device management solution like has a great tech community.
Core infrastructure, Updates for Configuration Manager, Supported configurations for Configuration Manager, Cloud-attached management of CM, Co-management for Windows 10, Manage clients on the internet, Windows as a service, CMPivot, Application management, Manage apps from the Microsoft Store for Business, OS deployment, Introduction to OS deployment, Upgrade to Windows 10, Phased deployments, Software update management, Introduction to software updates management, Manage Office 365 ProPlus updates
UPDATE – We, HTMD Community, have stopped the support of Android and iOS apps for the HTMD Forum. These apps will be retired soon.
This is really exciting news that we are announcing HTMD Forum App – iOS and Android Applications! We have announced this news during the Namaste🙏Techies Episode 3️⃣. As you know HTMD community has many WhatsApp, Telegram, Signal groups, this HTMD application is to empower the Device Management Community to help each other. Help each other is very significant here.
The Key value of the HTMD forum is to help your fellow device management admin with your experience and get some help from their experience. For us, it’s like Peer-to-Peer content sharing in the device management world. We have to spend a lot of time and effort publishing these applications for the device management community. Hopefully, this would be helpful to enrich the forum experience.
Features of HTMD Forum App
Native Mobile application
Create an Account (You don’t have to create a new account if you already have an HTMD Forum account)
One Time Login (No Need to log in every time)
No Advertisements
Access the HTMD Forum on the fly from your Android or iOS mobile
Post new questions
Answer Questions
Search the Forum for Solutions
Share the forum learnings with the community and spread the knowledge
iOS App
You can download and install the HTMD forum app from the apple store. It’s available for both iPad and iPhone.
You can just search the apple store with the“HTMD Forum” keyword.
Feedback is very important for us! This is the early version of the HTMD Forum App. It will improve with your feedback! We have created a thread to provide the feedback about HTMD Forum!
Hopefully, this post will give you more details to Configure collection size limits for Task Sequence Deployment Settings in Configuration Manager (a.k.a SCCM). This post will help you to configure and manage task sequence deployment settings with Configuration Manager. By configuring collection size limits in deployment verification site settings, will help admins to manage high-risk task sequence deployments and also reduce the accidental deployments that cause unwanted results. These settings warn administrators if they create a high-risk task sequence deployment.
Here lets check the available deployment verification settings –
Available Deployment Verification Settings
You can review and configure size limits in these following deployment verification settings from Primary Site server properties.
Collection size limits: When you target a deployment using configuration manager, configure collection size limits that hide collections if it include more clients than your specified limit.
Default size: When you create a deployment, this setting hides collections by default that include more clients than this limit. You can still see these collections when creating the deployment, but they’re hidden by default. The default value is 100. Select 0 to disable a configuration.
Maximum size: When you create a deployment, this setting always hides collections with more clients than this limit. The default value is 0, which ignores this setting. The Maximum size value must be greater than the Default size value.
How to Configure Collection Size Limits in Task Sequence Deployment Settings | Configuration Manager | SCCM
High-risk deployments are always limited to custom collections, collections that you create, and the built-in All Unknown Computers collection.
Configure Deployment Verification
Let’s start the process to configure deployment verification site settings –
In the Configuration Manager console, Navigate to the Administration\Site Configuration, select Sites, and then select the primary site to configure.
How to Configure Collection Size Limits in Task Sequence Deployment Settings | Configuration Manager | SCCM
In the primary site, Right click and select Properties
How to Configure Collection Size Limits in Task Sequence Deployment Settings | Configuration Manager | SCCM
In Primary Server Properties, move to the Deployment Verification tab. Configure the settings you want to use, and then select OK to save the configuration and close the properties.
How to Configure Collection Size Limits in Task Sequence Deployment Settings | Configuration Manager | SCCM
Results
Lets see the experience, if you set Default size to 100 and the Maximum size to 1000. When you target a deployment, the Select Collection window only displays collections that include fewer than 100 clients. If you clear the setting to Hide collections with a member count greater than the site’s minimum size configuration(100), the window displays collections that include fewer than 1000 clients as shown below.
How to Configure Collection Size Limits in Task Sequence Deployment Settings | Configuration Manager | SCCM
Where is the SCCM Task Sequence Available Deployment Options in Distribution Points Tab? And how to use this option in Task Sequence?
Let’s understand the available options in the Distribution Points tab during task sequence deployment using Configuration Manager. These dynamically depend on the selections in the deployment and attributes of the task sequence, so you may not be able to see all three deployment options available.
This post will help you to select the desired Deployment options on the Distribution Point pane when you deploy the task sequence to a collection.
Introduction
There are three deployment options available in the Distribution Points tab that appears when you deploy a Task Sequence.
Let’s check the options available –
Download content locally when needed by the running task sequence – Specify that clients download content from the distribution point as it’s needed by the task sequence. The client starts the task sequence. When a step in the task sequence requires content, it’s downloaded before the step runs.
Download all content locally before starting task sequence – Specify that clients download all the content from the distribution point before the task sequence runs.
Access content directly from a distribution point when needed by the running task sequence – Specify that clients run the content from the distribution point.
Scenario 1: One Deployment Option
You deploy an Operating System Deployment (OSD) task sequence that wipes the disk and applies an image. During the deployment process, we configured the following settings –
On the Deployment Settings page, for the Make available to the following setting selected Onlymedia and PXE.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Distribution Points page, there is only one deployment option: Download content locally when needed by the running task sequence:
The option to Download all content locally before starting the task sequence is not available because the deployment is made available to media and PXE.
The option to Access content directly from a distribution point when needed by the running task sequence is not available. As all the referenced content in the task sequence is not uses a package share.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
Scenario 2: Two Deployment Options
You deploy an Operating System Deployment (OSD) task sequence that wipes the disk and applies an image. During the deployment process, we configured the following settings –
On the Deployment Settings page, for the Make available to the following setting selected Only Configuration Manager clients.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Distribution Points page, there are two deployment options available:
Download content locally when needed by the running task sequence
Download all content locally before starting task sequence
The option to Access content directly from a distribution point when needed by the running task sequence is not available As all the referenced content in the task sequence is not uses a package share.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
Scenario 3: Three Deployment Options
You deploy a task sequence that has several Install-Package steps associated with it. In that, you need to make sure all the referenced package in the task sequence has the following setting on the Data Access tab selected Copy the content in this package to a package share on distribution points.
For Example – I am accessing the below package for validation.
In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node. Select the package and Right click, choose properties.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Data Access tab of this package properties, selected Copy the content in this package to a package share on distribution points.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Deployment Settings page, for the Make available to the following setting selected OnlyConfiguration Manager clients. This option is the only available. The task sequence is not for OS deployment, because it does not have a boot image associated with it.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Distribution Points page, there are three deployment options available:
Download content locally when needed by the running task sequence
Download all content locally before starting task sequence
Access content directly from a distribution point when needed by the running task sequence
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
Modify Existing Task Sequence Deployment Options
To change the deployment options for existing task sequence deployment. You must change the Deployment option “Make available to the following:” in the deployment properties. Here’s how –
In the Configuration Manager console, go to the Software Library workspace, expand Operating Systems, and select Task Sequences. Select the deployed task sequence to modify the deployment, and select Deployments tab.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
When you view the properties of existing task sequence deployment, the Deployment Settings tab appears on properties of the Deployment.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
On the Distribution Points tab, the following settings are available. You can change the deployment options from the drop-down list.
SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
Well, let’s find out what could be one of the reasons for the Intune error Server Returned Fault Code Subcode Value DeviceNotSupported. The error includes the following details as well “Server Returned Fault/Code/Subcode/Value=(DeviceNotSupported) Fault/Reason/Text=(OS Version 10.0.19041.0 lower than 10.0.19041.330).”
This is one of the errors which you want to happen for your users when required! Surprised! Well, read on! Let me help you to find more details about the enrollment error.
I used the Minimum version configuration using the following option Allow min/max range:
major.minor.build.rev for 1909= 10.0.18363.900
major.minor.build.rev for 2004= 10.0.19041.329
Server Returned Fault Code Subcode Value DeviceNotSupported Intune Enrollment Error
Try Enrolling – Server Returned Fault Code
+ Connect option might work fine for the Azure AD Registration scenario even though you have Device Type Restriction and blocked Windows 10 personal devices from enrolling in Intune MDM. More details about this option here.
I get the following error in the event log – Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin
The minimum version of Windows 10 allowed to enroll into Intune MDM is 10.0.19041.330. But, the version of Windows 10 which I tried to enroll was 10.0.19041.0.
Event Logs
Let’s check the event log errors when you configure device type restriction policy for Intune MDM enrollment restrictions.
Event ID 52 - MDM Enroll: Server Returned Fault/Code/Subcode/Value=(DeviceNotSupported) Fault/Reason/Text=(OS Version 10.0.19041.0 lower than 10.0.19041.330).
Event ID 59 - MDM Enroll: Server context (35b07916-950b-4c61-bb38-0430f8a17181).
Event ID 11 - MDM Enroll: Failed to receive or parse certificate enroll response. Result: (Unknown Win32 Error code: 0x80180014).
Event ID 71 - MDM Enroll: Failed (Unknown Win32 Error code: 0x80180014)
Server Returned Fault Code Subcode Value DeviceNotSupported Intune Enrollment Error
