MBAM error on client-TransferStatusDataFailed-2143485947 Access was denied by the remote endpoint.

After you have installed MBAM setup 2.5 and configured the roles, and start the testing.
You install the MBAM 2.5SP1 with Hotfix client.

On the client, in the Eventlog, you might get errors:
Eventid=4

Details:
-2143485947
Access was denied by the remote endpoint.

The reason is-MBAM client computer does not have sufficient access on the Portal Server.
Either add the test computer account as local Admin, or, give sufficient delegation.

Scan Error 0x80240fff in updatehandler.log

After you enable Win10 servicing in SCCM, you might get this error on Windows10 clients during update scan.
Reason is-in WSUS, there are duplicate entries for Feature update.....1607 and 1703.

Solution:
You need to go into WSUS console, search for 1607(or 1703), and decline the Feature Update to ....1607. All the results.

Also, try installing this update on the server:
https://blogs.technet.microsoft.com/configurationmgr/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/
 

RequestMPLocation failed; 0x80004005

Recently we were facing OS installation errors.
The smsts.log gave these errors:

Invalid MP cert info; no signature.Check MPs boundary group has site assignment set

CCM::SMSMessaging::CLibSMSMPLocation::RequestMPLocation failed; 0x80004005

How do you check the correct MP/Boundary?
Make a request to http://yourMP/SMS_MP/.sms_aut?MPLOCATION&ir=<IP>&ip=<IP subnet>

This string can also be found in the log.
This should return a MP certs and location. If empty, there is something wrong.

Solution:
The simple solution was to Check the settings on the Boundary Group properties-Use this site bioundary for site assignment.





Error fixed!
I think only applicable to 1702 environments.

 

Win10 TS error-failed to stage winpe code 0x8007000f

Sometimes, while doing OS Imaging for Win10 with UEFI selected, you light get this error in the Task Sequence. The smsts.log says-failed to stage winpe.

Reason is-Winpe is unable to stage on existing partitions, and requires a GPT partition for UEFI.

Solution-Before you select the Task Sequence to run, or when whn you get the error, press F8, and open cmd. Then run diskpart commands.

select disk 0
clean
convert gpt
create partition primary size=300
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
create partition efi size=100
format quick fs=fat32 label="System"
assign letter="S"
create partition msr size=128
create partition primary
format quick fs=ntfs label="Windows"
assign letter="C"

Then retry the Imaging and chose not to clean the Disk.

 

SCCM Software Updates process flowchart on clients

http://eskonr.com/wp-content/uploads/2015/04/image9.png

High CPU usage by the Sytem Process

Recently, we faced this situations where on Server2012 R2, the System process was causing high CPU. Around 40-60%.
Normally, it uses only 5%.

How do you troubleshoot?
Use Procmon.
Filter by Process Name like System. By default it is set to not include in the filter.

You will find that it is reading some files/folders in a loop. Delete those files.

Also, check you AV exclusions.

WMI error 0x8004106C smsprovider log

Symptoms: Sometimes, you get this error in SMS Provider log, in CM2012.
This is generally due to load on the server and WMI, during temporary processing of queries.

Resolution: This error can be fixed by increasing the quota values in __ProviderHostQuotaConfiguration WMI class.

Check out: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx

Changing values of Memory perhost and Memory allhosts is enough.

Method is described here: http://babaus.azurewebsites.net/2015/08/14/wmi-fine-tuning-for-config-mgr/

Another way is to run this script:

$WMIProviderConfig = Get-WmiObject @WMIHT            
$WMIProviderConfig.MemoryPerHost = 1024MB            
try {            
  $WMIProviderConfig.Put() | Out-Null            
  Write-Verbose -Message "Successfully changed the WMI provider settings" -Verbose            
} catch {            
  Write-Warning "Failed to modify the WMI provider because $($_.Exception.Message)"            
}