SCCM Agent Issues - CCM Agent Notification Agent Disabled

Had issues with a CM Agent on a computer. This agent installed with BITS transfers in foreground:
 
ccmsetup.exe /BITSPriority:FOREGROUND
 
Source: http://blogs.catapultsystems.com/chsimmons/archive/2015/05/20/bits-error-0x80200013-during-configmgr-client-installation/
 
The agent wouldn't install normally.
 
After installed, the component "CCM Notification Agent" was stuck at status Disabled in the Configuration Manager Properties.
 
Found this in DataTransferService.log:
 
CDTSJob::HandleErrors: DTS Job '{4C558D5D-CA3F-4712-9483-5E3BBF7D811C}' BITS Job '{B02B8C90-482B-47C6-BBC1-2397BEA72C64}' under user 'S-1-5-18' OldErrorCount 16 NewErrorCount 17 ErrorCode 0x80070426
 
CDTSJob::HandleErrors: DTS Job ID='{4C558D5D-CA3F-4712-9483-5E3BBF7D811C}' URL='http://SCCM02.domain.com:80/SMS_MP' ProtType=1
 
The following forum gave me the idea to look into the BranchCache service:
https://social.technet.microsoft.com/Forums/en-US/7d1ac58d-afa5-490c-9f8d-f1964afbba2a/bits-transfer-errors?forum=configmanagerdeployment
 
Running the command "bitsadmin /list /allusers" listed a bunch of errors:
 
{4BD1CBD5-C107-49D7-A478-A4EEAD87E098} 'CCMDTS Job' TRANSIENT_ERROR 2 / 30 10868 / 271558
{B02B8C90-482B-47C6-BBC1-2397BEA72C64} 'CCMDTS Job' TRANSIENT_ERROR 2 / 6 164302 / 266990
 
Found out that the BrancheCache service was set to Disabled.
 
After changing the service to Manual and starting it, the agent went up and running perfectly.
 
Hope this helps someone out there!
 
Cheers
2019-02-12 @ 13:11:26 Configuration Manager Permalink

Kommentarer

Kommentera inlägget här:

Namn:
Kom ihåg mig?

E-postadress: (publiceras ej)

URL/Bloggadress:

Kommentar:

Trackback
Kategorier
Arkiv
RSS 2.0