Why no mouse cursor when running an SCCM OSD task sequence?

I am deploying a Windows 10 device using an SCCM OSD Task Sequence. During the Setup Windows and ConfigMgr task, the device restarts out of Win PE into Windows 10. If I press F8 to open a Command Prompt, no mouse cursor appears. Once the task sequence has finished running, the mouse cursor magically appears.

“401 – Unsuccessful with anonymous access. Retrying with context credentials. SendResourceRequest() failed. 80190191” error in smsts.log

My SCCM 1810 task sequence I use to deploy Windows 10 via PXE boot or task sequence media seems to be taking forever to run.

If I look in the smsts.log on one of the devices, I see the following error message:

Setting Media Certificate.
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: DPServerFQDN:443 PROPFIND /CCMTOKENAUTH_SMS_DP_SMSPKG$/PKGID
401 - Unsuccessful with anonymous access. Retrying with context credentials.
SendResourceRequest() failed. 80190191

How do I start or stop the SCCM Client Service (‘SMS Agent Host’) from a Command Prompt?

On an SCCM client, how do I start or stop the SCCM Client Service (‘SMS Agent Host’) from a Command Prompt?

---

ANSWER

What’s new in SCCM 1802?

Microsoft announced the release of SCCM version 1802 on 22nd March 2018. In this article, we look at What’s New in SCCM 1802 including details of new features and functions, as well as details of any changes since previous versions. The areas affected by this release are (in alphabetical order):

• Application Management
• Client management
• Co-management
• Compliance settings
• Management insights
• Operating system deployment
• Protect devices
• Reporting
• SCCM console
• Site infrastructure
• Software Center
• Software Updates

Application Management

The following are what’s new in SCCM 1802 with regards to Application Management:

• Allow user interaction when installing an application – This feature allows an end user to interact with an application installation during the running of the task sequence. For example, you may require a user to provide some user-specific information to the setup process for an application. You may also have other apps that cannot install silently. This new feature handles both of these scenarios.
• Approve application requests for users per device – 1802 includes a new, optional feature that when a user requests an application that requires approval, their device name is included as part of the request. If the request is approved by the administrator, then the user can only install the requested application on the device on which they initiated the request. If the user wishes to install the same application on a different device, they need to initiate a new request for the same application but from the new device.
• Do not automatically upgrade superseded applications – You may have specific applications that either have, or will be superseded, but you do not want these to be automatically upgraded by an application deployment. In SCCM 1802, when you create a deployment, you will now notice on the Deployment Settings page of the Deploy Software Wizard, that for both Available or Required installation purposes you now have the option of enabling the Automatically upgrade any superseded versions of this application option.
• Run scripts improvements – The Run Scripts previously available as a pre-release feature, is now a released feature. Any output from this feature is generated in JSON formatting.

Client management

The following are what’s new in SCCM 1802 with regards to Client management:

• Silverlight no longer automatically installed on clients – In SCCM 1802 Silverlight isn’t automatically installed on SCCM clients.
• Cloud Management Gateway no longer pre-release – The cloud management gateway (CMG) is no longer a pre-release feature in SCCM 1802.
• Azure Resource Manager supported by Cloud management gateway – In 1802, when you create an instance of the cloud management gateway (CMG), you now have the option to create an Azure Resource Manager deployment which eliminates the need for a classic Azure management certificate. Instead, the Azure Resource Manager manages all resources as a resource group which is a single entity, which allows your site to use Azure Active Directory (Azure AD) to authenticate and create the necessary cloud resources. Just bear in mind deploying the CMG with the Azure Resource Manager does not provide support for Azure Cloud Service Providers (CSP) – this solution still uses the classic cloud service.
• New Hardware Inventory classes can collect strings greater than 255 characters – When you add a new class for hardware inventory (that aren’t keys) in SCCM 1802, you can now configure the length of the string to be greater than 255 characters.
• Surface device dashboard – SCCM 1802 includes the Surface device dashboard (located under Monitoring > Surface Devices in the console), which provides information about the Surface devices in your environment such as model types, firmware versions, amongst others.
• Support for Linux and UNIX Clients ending around SCCM 1902 – Microsoft has announced that SCCM 1810 will be the last version of SCCM that will provide support for Linux and UNIX clients. After this release, these client types will no longer be supported. Once support for SCCM 1810 expires, these client types will no longer be supported by SCCM at all (for Linux take a look Microsoft’s Operations Management Suite).

Co-management

The following are what’s new in SCCM 1802 with regards to co-management:

• Co-management dashboard – SCCM 1802 includes a dashboard allowing you to see co-managed machines in your environment and those that might need some remediation.
• Transition Endpoint Protection workload to Intune – Once you have enabled co-management, you can transition the Endpoint Protection workload to Intune, simply by going to the co-management properties page and moving the slider from Configuration Manager to Pilot or All.

Compliance settings

The following are what’s new in SCCM 1802 with regards to Compliance settings:

• Compliance settings policies for Microsoft Edge – SCCM 1802 now allows you to create a compliance settings policy to configure Microsoft Edge settings which can then be deployed to your Windows 10 clients.

What is the Support End Date for each version of SCCM?

If you are trying to work end when official Microsoft support will end for your version of SCCM, then look no further than the table below (updated with the release of SCCM 1802) which answers the question, what is the support end date for each version of SCCM?

---

ANSWER

Release	Available	Support Ends
1511	8th December 2015	8th December 2016
1602	11th March 2016	11th March 2017
1606	22nd July 2016	22nd July 2017
1610	18th November 2016	18th November 2017
1702	27th March 2017	27th March 2018

 

What are the SCCM Version Numbers for Current Branch?

There have been multiple releases of SCCM Current Branch but I’m having trouble working out which version number relates to which release. What are the SCCM Version Numbers for Current Branch?

---

ANSWER

The following table lists the version numbers for SCCM Current Branch, updated for SCCM 1802:

Release	Version Number	Comments
1511	5.00.8325.1000	Baseline Release
	5.00.8325.1005	KB3125905
	5.00.8325.1010	KB3122677
	5.00.8325.1126	KB3163344
1602	5.00.8355.1000	Update Release
	5.00.8355.1306	KB3155482
	5.00.8355.1307	KB3174008
1606	5.00.8412.1000	Baseline Release: Site: 5.00.8412.1000 Console: 5.00.8412.1003 Client: 5.00.8412.1006
	5.00.8412.1204	KB3180992
	5.00.8412.1205	KB3184153
	5.00.8412.1207	KB3180992
	5.00.8412.1307	KB3186654
	5.00.8412.1309	KB3192616
1610	5.00.8458.1000	Update Release: Site: 5.00.8458.1000 Console: 5.00.8458.1500 Client: 5.00.8458.1005
	5.00.8458.1006-1008	KB3209501
	5.00.8458.1009	KB3214042
	5.00.8458.1520	KB4010155

 

Why can’t I select multiple Applications in the SCCM Software Center?

I am trying to select multiple Applications at once so I can perform one installation rather than installing apps on an individual basis. However, why can’t I select multiple Applications in the SCCM Software Center?

SCCM 1802 automated installation of new site fails with error a required parameter is missing

Why does an SCCM 1802 automated installation of new site fails with error a required parameter is missing? I have also tried running a silent install from a command-line but this fails with the same error.

---

ANSWER

This is because from SCCM 1802 the Customer Experience Improvement Program (CEIP) feature has been removed from the product.

However, the setup process has not been modified. So the end result is if you try to automate the installation of a new SCCM site either from an unattended script or a command-line you will see the error.

To workaround this issue,