In some cases this can be related to not having boundary and discovery methods configured. In others, DNS resolution to the client may not be working. In a case I worked recently, it was due to AV exclusions not being in place. This client runs Windows Defender, and they had not enabled management through ConfigMgr like they thought they had.

This information was buried pretty deep in the interwebs, so I wanted to put it here in a readable and useable format for myself and anyone else who may ever need it. Table ID tag is "ConfigMgrSiteUpdateStatusCodes" if you want to do some element grabbing.

The Discover Button in edge has, to the dismay of many, shown up with the recent batch of updates. Several posts have gone up around the internet about manual ways to adjust this, or even directly via the registry. For those in enterprise environments, it's possible to do directly via Group Policy (GPO).

In order for Dell and Lenovo drivers to show as applicable when deploying them as 3rd Party updates using Dell or Lenovo's 3rd-Party update catalogs in Configuration Manager, you will need to ensure that the "Dell OpenManage Inventory Agent" (for Dells) and the "Lenovo Updates Catalog Agent" (for Lenovos) are included in your driver updates deployments.

Sometimes it's hard to remember which Windows ADK components are required for Microsoft Endpoint Manager Configuration Manager and installing extras can take up a considerable amount of unnecessary space. So here is a short, sweet, and to the point post. The required components are:

Helped a SysAdmin today troubleshoot an issue that was driving them crazy. distmgr.log in their environment was throwing a "Thread_ProcessDPActions() failed with error code - 0x80004005" error constantly, preceded by and entry that stated "Failed to find DP properties for DP with ID - ".

Had an issue today where a site could not PXE boot. Other sites could PXE fine, however the SMSPXE log on this particular site's DP showed servicing rejected messages any time PXE booting was attempted.

Checked the following:

Due to the wide spread of installer types used by different vendors, application packaging in Windows can be a pretty confusing area to get started in. This blog series will provide a basic introduction early on, in hopes of delving into more specific topics as we go. Packaging an application can vary in difficulty from a straightforward installation taking around 20 minutes to a complex or tricky application soaking up weeks of your time to figure out.

We recently enabled peer cache in a large environment running SCCM/MEMCM 1906. A package that was previously tested to install successfully now started failing to install. Clients would reach downloading 99% before failing out without ever running the installation. CAS.log showed hash verification failures, and ContentTransferManager.log always showed that the content was downloaded from a peer source. Anti-Virus exclusions, etc. were proven out to be in place and working correctly, and so we added a bogus file to the package in order to get DistMgr to resnapshot the package and redistributed the content out. We then pushed out machine policy and deployment evals, and clients started successfully installing the application. This seemed to be resolved, however, the next day we were right back where we were before with hash validation issues.