M365 Apps Update fails to download by DownloadError = 30101 when unable to download from peer cache source.
The expected behavior is fallback to DP and continue to download even if fails to download from peercache, however an error occurs before fallback and client cannot continue to download from DP.

The Peer Cache cannot be used effectively, so we request improvement.

Enviroment

ConfigMgr version 2006 , 2010 and 2103
Microsoft 365 Apps Update in March, April and May.

Repro Step

1. Peer cache client's AlternateHandler begin to download.

BeginDownload: contentID =750d04a4-8178-4cb6-9c72-f8bf2a096a7a and contentVersion=1 AlternateHandler

1. Data Transfer Service download error from peer and switched to location next peer.
2. Data Transfer Service download error from 2nd peer.

(Now it is expected download from next peer or DP, but actually...)

1. AlternateHandler.log is DownloadError = 30101.
2. UpdateHandler.log is Error = 0x80077595.

• AlternateHandler.log
  DownloadStatus = eDOWNLOAD_FAILED
  DownloadError = 30101

• UpdateHandler.log
  CAS failed to download update (750d04a4-8178-4cb6-9c72-f8bf2a096a7a). Error = 0x80077595. Releasing content request

We need more control over User Notifications via dialog boxes rather than toast notifications. Currently we have the ability to "When software changes are required, show a dialog window to the user instead of a toast notification" for applications but not for software updates, standard packages, or non-critical task sequences.

Our users rarely see toast notifications so it needs to be more in your face. My users should not be expected to "notice" the toast notification, click on the icon, then click on "view required software". When I deploy a required software, I want it to pop up the dialog notification right away and give the user the ability to choose what they want to do before the software becomes required at the deadline.

In addition, the user notification dialog box needs to customizable.

We've opened a MS case because a lot of status messages are lost during our in-place upgrade task sequence and this makes it really hard to monitor our deployments. A CMG is in place and acts also as a distribution point. The clients are configured to prefer the management point from the boudaries and the CMG is part of the VPN boundary. During the task sequence the client will/can switch multiple times from intranet (vpn) to internet (cmg). This seems to be the cause of the lost status messages. We were told by Microsoft that this is not a tested/supported scenario. But I'm pretty sure that this is a wide spread scenario and should be totally supported. All ConfigMgr components should be able to handle these network changes dynamically. Please make sure the client always communicates to the correct MP. We cannot switch the clients to "Always Internet" because that would increase our Azure costs.

Allow Fallback DPs to be used for SourceList updating.

Source list updating sees Fallback DPs as remote and they are therefore ignored as possible sources.

Distribution Point='http:/.../SMSDPSMSPKG$/Content....', Locality='NEIGHBORBOUNDARYGROUP'
LS returned http://.../SMSDPSMSPKG$/Content... as remote DP when local DPs were requested
No Distribution points were found for package
No DP found for product... , skipping source update

This means systems in boundaries configured this way do not maintain current references to source, leading to later issues with MSI repairs, patching, etc. prompting for source.

SCCM should support the option (e.g. through client settings for CCM_SourceUpdateClientConfig) to allow RemoteDPs to be included for source list updating.

The ConfigMgr AdminService uses OData which accepts parameters/variables, etc via the URI like this

https://cm01.contoso.com/AdminService/wmi/SMS_R_System(123345678)

https://cm01.contoso.com/AdminService/wmi/SMS_R_System?$filter=Name eq 'MyDeviceName'

Other custom solutions like a Help Desk portal have similar options that support input via the URI.

Currently from Software Center, there's no way to pull in any information about the local client where the custom tab is being loaded. This request is to add options within Client Settings > Software Center > Custom Tabs that would allow the insertion of wildcards for things like UserName, DeviceName, DeviceID, UserID, etc, that can be added into the Custom Tabs URL that's specified in Client Settings.

So the URL in Client Settings would be:

https://cm01.contoso.com/AdminService/wmi/SMS_R_System?$filter=Name eq '%%SMS_DeviceName%%'

With the result on the client being:

https://cm01.contoso.com/AdminService/wmi/SMS_R_System?$filter=Name eq 'MyDeviceName'

This type of functionality would greatly improve the usability of the Custom Tabs Feature.

To take this a step further:
Client settings could also include an Ad-Hoc variable option where we could specify a powershell script or WMI command that would produce a single value that could then be used in the querystring. The script payload would be pushed to the client via policy where it could run when the user clicks the Custom Tab in Software Center. The script would capture the result and store it into the custom variable name which would then be populated in the URI to load the tab.

Some simple examples of ad-hoc options would be PowerShell Environment Varables like:

$env:COMPUTERNAME
$env:USERDOMAIN

get network adapter name

(Get-NetAdapter)[0].Name

Get Device Model from WMI

Get-CIMInstance Win32_ComputerSystem | Select -ExpandProperty Model

Basically, look at how Power BI handles their custom URL Builder for the ODATA connector type. See sample pictures.