Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED After 1902 Upgrade - User Targeted, Software Center application installs fail immediately

Status
Not open for further replies.

Jeeves

New Member
Messages
1
Reaction score
0
Points
1
Upon the release of 1902 (FR), I watched for reports of problems. Not seeing any issues, we went ahead with the install.

However, a bug seems to have cropped up and a good portion of Software Center is currently non-functional.
In 1902: If a user tries to install anything from Software Center that is a 'user targeted' install they receive an immediate error:


At first, both AppCatalog roles were still installed (as they had been all along). However, seeing that they were deprecated (as of 1806) and largely unneeded, I removed them both (Application Catalog Web Service Point & Website Point). However, Removing these AppCatalog roles did not fix the problem.

The only logs that are modified when this failure appears are: SCClient_, SCNotify_ and CCMSDKPRovider:
The logs show that an exception is thrown when trying to handle or submit the DeviceID.
  1. SCClient log
  2. CCMSDKProvider log

The error "Failed to build instance path," sounded like a WMI problem however WMI is consistent:
Failed to build instance path for ScopeId_ ..... "Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at GetInstance."

"Server was unable to process the request. ---> DeviceId"

The logs also seem to show that the client may be handing off blank or empty fields to the MP. However, I also see no further way to debug this.

Has anyone seen an issue like this before or have a further idea how to troubleshoot it?
 
Solution
It is a known bug if the following is true:

  • You are using PKI for Client Communication (Administration > Sites > Properties > Client Computer Commnunication > Use PKI Client certicicate .... = Enabled
  • Your Client Certificate Key Length is using a greater value than '2,048' (Properties of Certificate > Details > Public Key = RSA (value larger than 2, 048))
Although this certificate was working before, this is actually a documented here ( https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements) and any value greater than 2048 is not supported.

"Maximum supported key length is 2,048 bits."
It is a known bug if the following is true:

  • You are using PKI for Client Communication (Administration > Sites > Properties > Client Computer Commnunication > Use PKI Client certicicate .... = Enabled
  • Your Client Certificate Key Length is using a greater value than '2,048' (Properties of Certificate > Details > Public Key = RSA (value larger than 2, 048))
Although this certificate was working before, this is actually a documented here ( https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements) and any value greater than 2048 is not supported.

"Maximum supported key length is 2,048 bits."
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,028
Messages
27,501
Members
17,681
Latest member
pozegatom
Back
Top