Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Client on Management Point doesn't work after in place OS upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-2607736%22%20slang%3D%22en-US%22%3EClient%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2607736%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EFollowing%20the%20docs%20here%26nbsp%3Bhttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmem%2Fconfigmgr%2Fcore%2Fservers%2Fmanage%2Fupgrade-on-premises-infrastructure%26nbsp%3B%26nbsp%3Babout%20in%20place%20OS%20upgrade%20for%20a%20CM%202010%20install.%20The%20servers%20went%20from%202012%20R2%20to%202019.%20The%20upgrade%20worked%20fine%20for%20the%20primary%20site%20server%20which%20holds%20most%20of%20the%20roles%20(SQL%20server%2C%20Reporting%20services%2C%20WSUS%2FSUP%20with%20shared%20content%20folder).%20I%20then%20upgraded%20our%20management%20point%20which%20also%20serves%20as%20a%20secondary%20SUP.%20I%20removed%20WSUS%20on%20both%20before%20the%20upgrades%20and%20added%20them%20back%20as%20described%20in%20the%20docs.%20The%20upgrade%20went%20fine.%20I%20did%20a%20site%20reset%20to%20ensure%20everything%20is%20good%20and%20there%20were%20no%20issues%20in%20the%20console.%20Clients%20are%20working%20fine%20for%20all%20features.%3C%2FP%3E%3CP%3EAfter%20a%20few%20days%20I%20noticed%20that%20the%20management%20point%20is%20no%20longer%20compliant%20with%20the%20configuration%20baselines.%20Turns%20out%20it%20hasn't%20run%20any%20of%20them%20since%20the%20upgrade.%20I%20reinstalled%20the%20client%20and%20it%20finished%20with%20no%20errors.%20It%20seems%20to%20register%20fine.%20The%20certificate%20is%20fine%20but%20then%20when%20it%20tries%20to%20download%20policy%20or%20upload%20messages%20to%20the%20MP%20(itself)%2C%20the%20jobs%20all%20error%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20DataTransferService.log%20show%20the%20following%20sorts%20of%20errors%20repeated%3A%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7BE27D24C3-091D-4793-92D6-CB8040D35D4C%7D'%20BITS%20Job%20'%7B4EA2941A-D5F2-4760-9947-DC6EC8ACD937%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%20415%20NewErrorCount%20416%20ErrorCode%200x80072EFE%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7B3C7E4C35-2A83-4614-9565-608585A49D1C%7D'%20BITS%20Job%20'%7B57E58E15-8BEF-41AF-BD25-2F47AA42BC17%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%20131%20NewErrorCount%20132%20ErrorCode%200x80072EFE%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20ID%3D'%7B3C7E4C35-2A83-4614-9565-608585A49D1C%7D'%20URL%3D'https%20%3A%20%2F%2F%3CMP%20fqdn%3D%22%22%3E%3A443%2FSMS_MP'%20ProtType%3D3%3C%2FMP%3E%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7BECDFDEFC-2DCF-4570-A0D9-03701B0FF9D2%7D'%20BITS%20Job%20'%7BC0EB62DB-F1DC-42E5-94E8-DAE216713B0F%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%20113%20NewErrorCount%20114%20ErrorCode%200x80072EFE%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20ID%3D'%7BECDFDEFC-2DCF-4570-A0D9-03701B0FF9D2%7D'%20URL%3D'https%20%3A%20%2F%2F%3CMP%20fqdn%3D%22%22%3E%3A443%2FSMS_MP'%20ProtType%3D3%3C%2FMP%3E%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7B8F8B924E-04B6-4CD1-8928-963E00DE343C%7D'%20BITS%20Job%20'%7B5EF47274-86E8-44AA-B9F0-EEDD903D0F37%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%20208%20NewErrorCount%20209%20ErrorCode%200x80072EFE%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20ID%3D'%7B8F8B924E-04B6-4CD1-8928-963E00DE343C%7D'%20URL%3D'https%3A%2F%2F%3CMP%20fqdn%3D%22%22%3E%3A443%2FSMS_MP'%20ProtType%3D3%3C%2FMP%3E%3C%2FFONT%3E%3CBR%20%2F%3E%3CFONT%20size%3D%223%22%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7BAC6517A8-EEC9-42F3-9205-215B281F2240%7D'%20BITS%20Job%20'%7B64F4719A-9053-400C-BA90-C0AAE00210B9%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%20131%20NewErrorCount%20132%20ErrorCode%200x80072EFE%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20error%20source%20is%20WinHTTP%20and%20means%20%22The%20connection%20with%20the%20server%20was%20terminated%20abnormally%22.%20I%20see%20an%20entry%20in%20the%20IIS%20logs%20with%20a%20403%20error%2C%20but%20I%20don't%20know%20how%20to%20get%20more%20details%20about%20what%20is%20causing%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20with%20bitsadmin%20it%20shows%20the%20following%3A%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%7B5211F5B3-89FF-47AC-9BDC-5C67B990CFA7%7D%20'CCM%20Message%20Upload%20%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D'%20TRANSIENT_ERROR%200%20%2F%201%200%20%2F%2014138%3CBR%20%2F%3E%7B73F46E79-CD10-4846-840E-7ECD0CCBB976%7D%20'CCM%20Message%20Upload%20%7B6CE3E579-1C78-4E2D-A1C6-C7118BBAA75E%7D'%20TRANSIENT_ERROR%200%20%2F%201%200%20%2F%2024650%3CBR%20%2F%3E%7B9B0D204F-0D88-4683-8800-ADE66C176A0C%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B63EA641C-266A-4EC5-A428-D3DC30266040%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7BB6C82074-7794-4A34-999A-3938A2216933%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%2028%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7BD68CF136-7EFB-4F5F-8E56-7B03C6C83830%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B47152487-B6AA-4134-BBD8-83A85467B8E5%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B90F73916-3F8C-48CD-B201-7F3AD9A5003F%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%203%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7BDF682297-9FFE-4348-B104-FB344B178C13%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B6A839CF0-45BB-453A-98D9-F75343BE97D5%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7BEA51C2C6-EEB4-4018-AC8A-E0475BD53513%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B2471FF3C-FD78-4BB4-A037-7E146619FDB8%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%204%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B6E50A082-1771-4147-B06A-76DD40DD6DAD%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%2028%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B454513C9-AC01-43E1-B0E8-102FBE25779E%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%2057%200%20%2F%20UNKNOWN%3CBR%20%2F%3E%7B34F8B723-1371-461C-A4C5-A4866323EC44%7D%20'CCMDTS%20Job'%20TRANSIENT_ERROR%200%20%2F%2057%200%20%2F%20UNKNOWN%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20delete%20the%20bits%20jobs%2C%20they%20just%20come%20back%20again%20of%20course.%26nbsp%3B%3CSPAN%3EI%20don't%20know%20if%20it%20is%20useful%20to%20anyone%2C%20but%20when%20I%20run%20a%20bitsadmin%20on%20the%20job%20I%20get%20the%20following%20info.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3Ebitsadmin%20%2Finfo%20%7B5211F5B3-89FF-47AC-9BDC-5C67B990CFA7%7D%20%2Fverbose%3C%2FP%3E%3CP%3EBITSADMIN%20version%203.0%3CBR%20%2F%3EBITS%20administration%20utility.%3CBR%20%2F%3E(C)%20Copyright%20Microsoft%20Corp.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EGUID%3A%20%7B5211F5B3-89FF-47AC-9BDC-5C67B990CFA7%7D%20DISPLAY%3A%20'CCM%20Message%20Upload%20%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D'%3CBR%20%2F%3ETYPE%3A%20UPLOAD%20STATE%3A%20TRANSIENT_ERROR%20OWNER%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3EPRIORITY%3A%20NORMAL%20FILES%3A%200%20%2F%201%20BYTES%3A%200%20%2F%2014138%3CBR%20%2F%3ECREATION%20TIME%3A%207%2F30%2F2021%205%3A26%3A37%20PM%20MODIFICATION%20TIME%3A%208%2F3%2F2021%207%3A27%3A22%20PM%3CBR%20%2F%3ECOMPLETION%20TIME%3A%20UNKNOWN%20ACL%20FLAGS%3A%3CBR%20%2F%3ENOTIFY%20INTERFACE%3A%20UNREGISTERED%20NOTIFICATION%20FLAGS%3A%203%3CBR%20%2F%3ERETRY%20DELAY%3A%20600%20NO%20PROGRESS%20TIMEOUT%3A%201209600%20ERROR%20COUNT%3A%201193%3CBR%20%2F%3EPROXY%20USAGE%3A%20NO_PROXY%20PROXY%20LIST%3A%20NULL%20PROXY%20BYPASS%20LIST%3A%20NULL%3CBR%20%2F%3EERROR%20FILE%3A%20https%20%3A%20%2F%2F%3CMP%3E%3A443%2FCCM_Incoming%2F%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D%20-%26gt%3B%20D%3A%5CSMS_CCM%5CServiceData%5CLocalPayload%5C%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D%3CBR%20%2F%3EERROR%20CODE%3A%200x80072efe%20-%20The%20connection%20with%20the%20server%20was%20terminated%20abnormally%3CBR%20%2F%3EERROR%20CONTEXT%3A%200x00000005%20-%20The%20error%20occurred%20while%20the%20remote%20file%20was%20being%20processed.%3CBR%20%2F%3EDESCRIPTION%3A%3CBR%20%2F%3EJOB%20FILES%3A%3CBR%20%2F%3E0%20%2F%2014138%20WORKING%20https%20%3A%20%2F%2F%3CMP%3E%3A443%2FCCM_Incoming%2F%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D%20-%26gt%3B%20D%3A%5CSMS_CCM%5CServiceData%5CLocalPayload%5C%7B9EF459CF-4EB2-4A75-8FFF-FF400050A3B8%7D%3CBR%20%2F%3ENOTIFICATION%20COMMAND%20LINE%3A%20none%3CBR%20%2F%3Eowner%20MIC%20integrity%20level%3A%20SYSTEM%3CBR%20%2F%3Eowner%20elevated%20%3F%20true%3C%2FMP%3E%3C%2FMP%3E%3C%2FP%3E%3CP%3EPeercaching%20flags%3CBR%20%2F%3EEnable%20download%20from%20peers%20%3Afalse%3CBR%20%2F%3EEnable%20serving%20to%20peers%20%3Afalse%3C%2FP%3E%3CP%3ECUSTOM%20HEADERS%3A%20NULL%3CBR%20%2F%3ECLIENT%20CERTIFICATE%20INFORMATION%3A%3CBR%20%2F%3ECertificate%20Store%20Location%20%3A%20CERT_STORE_LOCATION_LOCAL_MACHINE%3CBR%20%2F%3ECertificate%20Store%20Name%20%3A%20MY%3CBR%20%2F%3ECertificate%20Hash%20%3A%2041C2067A522B94550F626B1A136015C4C6FE46D9%3CBR%20%2F%3ECertificate%20Subject%20Name%20%3A%20NULL%3C%2FP%3E%3CP%3EHTTP%20security%20flags%3CBR%20%2F%3EEnable%20CRL%20Check%20%3Atrue%3CBR%20%2F%3EIgnore%20invalid%20common%20name%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20date%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20certificate%20authority%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20usage%20of%20certificate%20%3Afalse%3CBR%20%2F%3EURL%20redirection%20policy%20%3ARedirects%20will%20be%20automatically%20allowed.%3CBR%20%2F%3ERedirection%20from%20HTTPS%20to%20HTTP%20allowed%20%3Afalse%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3EThe%20certificate%20hash%20in%20the%20job%20is%20the%20same%20one%20that%20shows%20in%20the%20ClientIDManagerStartup.log%20in%20the%20client%20log%20folder.%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3B%26gt%3B%20Client%20selected%20the%20PKI%20Certificate%20%5BThumbprint%2041C2067A522B94550F626B1A136015C4C6FE46D9%5D%20issued%20to%20'%3CMP%20fqdn%3D%22%22%3E'%20ClientIDManagerStartup%208%2F3%2F2021%205%3A59%3A50%20PM%205304%20(0x14B8)%3C%2FMP%3E%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20been%20scouring%20the%20web%20for%20a%20few%20days%20now%20and%20can't%20seem%20to%20find%20anything%20to%20help.%20I%20see%20no%20other%20obvious%20errors%20in%20the%20log%20files.%26nbsp%3B%20Again%2C%20no%20other%20machines%20are%20having%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20I%20could%20probably%20remove%20the%20MP%20role%20and%20reinstall%20or%20bring%20up%20a%20new%20MP%2C%20but%20I%20would%20rather%20not%20as%20this%20is%20my%20dev%20server%20that%20I%20was%20testing%20the%20in%20place%20upgrade%20on%20before%20I%20did%20the%20same%20thing%20in%20prod%20and%20I'm%20not%20looking%20forward%20to%20having%20to%20make%20those%20sorts%20of%20changes%20this%20close%20to%20the%20start%20of%20the%20semester%20on%20the%20prod%20side%20if%20the%20same%20thing%20happens%20when%20I%20upgrade%20prod.%20Anyone%20have%20any%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2607736%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2676107%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2676107%22%20slang%3D%22en-US%22%3EAnyone%20have%20any%20ideas%3F%20I%20am%20seeing%20other%20computers%20that%20aren't%20config%20manager%20servers%20also%20showing%20similar%20problems%20in%20the%20dataTransfer.log%20file.%20They%20aren't%20sending%20in%20hardware%20inventory%20to%20the%20management%20point%20or%20they%20are%20having%20issues%20downloading%20bits%20jobs%20from%20the%20management%20point.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20inplace%20server%20OS%20upgrade%20has%20not%20been%20a%20smooth%20process.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2686248%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2686248%22%20slang%3D%22en-US%22%3EI%20posted%20to%20Reddit%20as%20well%20and%20got%20some%20pointers%20saying%20you%20need%20to%20remove%20the%20MP%20role%20if%20you%20fully%20reinstall%20the%20client.%20No%20links%20to%20any%20specific%20docs%2C%20more%20just%20%22I've%20heard%22%20sort%20of%20thing.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20removed%20the%20MP%20role%2C%20but%20left%20the%20SUP%20role.%20This%20seemed%20to%20remove%20the%20client%20at%20the%20same%20time.%20At%20least%20it%20removed%20the%20Control%20Panel%20entry.%3CBR%20%2F%3EI%20then%20reinstalled%20the%20MP%20role%20and%20then%20installed%20the%20client.%20They%20both%20exited%20setup%20with%20error%20code%200%2C%20but%20the%20issue%20still%20remains.%3CBR%20%2F%3EI%20dug%20into%20the%20logs%20a%20bit%20more%20and%20it%20seems%20like%20it's%20something%20to%20do%20with%20the%20certs%20maybe.%3CBR%20%2F%3EKeep%20in%20mind%20this%20is%20all%20on%20the%20management%20point%20itself%20and%20we%20do%20require%20HTTPS%20via%20an%20internal%20ADCS%20PKI.%20If%20I%20look%20at%20one%20of%20the%20errors%20in%20the%20DataTransferService.log%20and%20grab%20the%20BITS%20job%3A%3CBR%20%2F%3E%3CBR%20%2F%3ECDTSJob%3A%3AHandleErrors%3A%20DTS%20Job%20'%7BF0AD54F5-7364-49BE-91C4-33BA0DED45DC%7D'%20BITS%20Job%20'%7B20FFFB81-7308-4187-832D-500312F8B7D6%7D'%20under%20user%20'S-1-5-18'%20OldErrorCount%201397%20NewErrorCount%201398%20ErrorCode%200x80072EFE%20DataTransferService%208%2F25%2F2021%209%3A46%3A47%20PM%201316%20(0x0524)%3CBR%20%2F%3E%3CBR%20%2F%3EThen%20checking%20the%20bits%20job%2C%20I%20can%20get%20the%20URL%20(%3CA%20href%3D%22https%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%3C%2FA%3E)%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3Ebitsadmin%20%2Finfo%20'%7B20FFFB81-7308-4187-832D-500312F8B7D6%7D'%20%2Fverbose%3CBR%20%2F%3E%3CBR%20%2F%3EBITSADMIN%20version%203.0%3CBR%20%2F%3EBITS%20administration%20utility.%3CBR%20%2F%3E(C)%20Copyright%20Microsoft%20Corp.%3CBR%20%2F%3E%3CBR%20%2F%3EGUID%3A%20%7B20FFFB81-7308-4187-832D-500312F8B7D6%7D%20DISPLAY%3A%20'CCMDTS%20Job'%3CBR%20%2F%3ETYPE%3A%20DOWNLOAD%20STATE%3A%20TRANSIENT_ERROR%20OWNER%3A%20NT%20AUTHORITY%5CSYSTEM%3CBR%20%2F%3EPRIORITY%3A%20HIGH%20FILES%3A%200%20%2F%201%20BYTES%3A%200%20%2F%20UNKNOWN%3CBR%20%2F%3ECREATION%20TIME%3A%208%2F20%2F2021%204%3A11%3A01%20PM%20MODIFICATION%20TIME%3A%208%2F25%2F2021%209%3A30%3A13%20PM%3CBR%20%2F%3ECOMPLETION%20TIME%3A%20UNKNOWN%20ACL%20FLAGS%3A%3CBR%20%2F%3ENOTIFY%20INTERFACE%3A%20REGISTERED%20NOTIFICATION%20FLAGS%3A%2011%3CBR%20%2F%3ERETRY%20DELAY%3A%2060%20NO%20PROGRESS%20TIMEOUT%3A%2028800%20ERROR%20COUNT%3A%201380%3CBR%20%2F%3EPROXY%20USAGE%3A%20NO_PROXY%20PROXY%20LIST%3A%20NULL%20PROXY%20BYPASS%20LIST%3A%20NULL%3CBR%20%2F%3EERROR%20FILE%3A%20%3CA%20href%3D%22https%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%3C%2FA%3E%20-%26gt%3B%20D%3A%5CSMS_CCM%5CStaging%5C%7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.3.00.tmp%3CBR%20%2F%3EERROR%20CODE%3A%200x80072efe%20-%20The%20connection%20with%20the%20server%20was%20terminated%20abnormally%3CBR%20%2F%3EERROR%20CONTEXT%3A%200x00000005%20-%20The%20error%20occurred%20while%20the%20remote%20file%20was%20being%20processed.%3CBR%20%2F%3EDESCRIPTION%3A%3CBR%20%2F%3EJOB%20FILES%3A%3CBR%20%2F%3E0%20%2F%20UNKNOWN%20WORKING%20%3CA%20href%3D%22https%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2FSERVER-FQDN%3A443%2FSMS_MP%2F.sms_pol%3F%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%3C%2FA%3E%20-%26gt%3B%20D%3A%5CSMS_CCM%5CStaging%5C%7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.3.00.tmp%3CBR%20%2F%3ENOTIFICATION%20COMMAND%20LINE%3A%20none%3CBR%20%2F%3Eowner%20MIC%20integrity%20level%3A%20SYSTEM%3CBR%20%2F%3Eowner%20elevated%20%3F%20true%3CBR%20%2F%3EThis%20job%20is%20read-only%20to%20the%20current%20CMD%20window%20because%20the%20job's%20mandatory%3CBR%20%2F%3Eintegrity%20level%20of%20SYSTEM%20is%20higher%20than%20the%20window's%20level%20of%20HIGH.%3CBR%20%2F%3EPeercaching%20flags%3CBR%20%2F%3EEnable%20download%20from%20peers%20%3Atrue%3CBR%20%2F%3EEnable%20serving%20to%20peers%20%3Atrue%3CBR%20%2F%3E%3CBR%20%2F%3ECUSTOM%20HEADERS%3A%20NULL%3CBR%20%2F%3ECLIENT%20CERTIFICATE%20INFORMATION%3A%3CBR%20%2F%3ECertificate%20Store%20Location%20%3A%20CERT_STORE_LOCATION_LOCAL_MACHINE%3CBR%20%2F%3ECertificate%20Store%20Name%20%3A%20MY%3CBR%20%2F%3ECertificate%20Hash%20%3A%2041C2067A522B94550F626B1A136015C4C6FE46D9%3CBR%20%2F%3ECertificate%20Subject%20Name%20%3A%20NULL%3CBR%20%2F%3E%3CBR%20%2F%3EHTTP%20security%20flags%3CBR%20%2F%3EEnable%20CRL%20Check%20%3Atrue%3CBR%20%2F%3EIgnore%20invalid%20common%20name%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20date%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20certificate%20authority%20in%20server%20certificate%20%3Afalse%3CBR%20%2F%3EIgnore%20invalid%20usage%20of%20certificate%20%3Afalse%3CBR%20%2F%3EURL%20redirection%20policy%20%3ARedirects%20will%20be%20automatically%20allowed.%3CBR%20%2F%3ERedirection%20from%20HTTPS%20to%20HTTP%20allowed%20%3Afalse%3CBR%20%2F%3E%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3EFinally%20if%20I%20look%20in%20the%20IIS%20Log%20for%20that%20URL%20I%20see%20a%20403.7%20error%20which%20from%20what%20I%20can%20tell%20indicates%20a%20mutual%20cert%20auth%20error.%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3E2021-08-26%2001%3A46%3A47%2010.10.28.120%20HEAD%20%2FSMS_MP%2F.sms_pol%20%257B33B321B6-72BD-4827-95FF-623A04B7CE53%257D.SHA256%3A52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB%20443%20-%2010.10.28.120%20Microsoft%2BBITS%2F7.8%20-%20403%207%2064%201%3CBR%20%2F%3E%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3EIn%20order%20to%20rule%20out%20every%20issue%20with%20certs%2C%20I%20deleted%20all%20the%20certs%20except%20one%20that%20is%20configured%20for%20both%20client%20and%20server%20auth%20and%20is%20the%20one%20setup%20for%20IIS.%20I%20verified%20in%20the%20ClientIDManagerStartup.log%20that%20it%20had%20selected%20that%20cert%20for%20the%20CM%20client.%20Going%20to%20the%20IIS%20server%20from%20the%20client%20browser%20shows%20no%20issues%20and%20of%20course%20other%20machines%20can%20talk%20just%20fine%20to%20the%20MP.%3CBR%20%2F%3EAnyone%20have%20any%20other%20ideas%20or%20know%20how%20to%20get%20more%20detailed%20logging%20from%20BITS%20on%20IIS%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2703646%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2703646%22%20slang%3D%22en-US%22%3EI've%20now%20removed%20the%20CM%20roles%2C%20all%20pre-requisites%20and%20then%20reinstalled%20and%20I%20am%20still%20seeing%20BITS%20errors%20from%20multiple%20clients%20talking%20to%20the%20MP.%20Some%20downloads%20and%20uploads%20seem%20to%20work%20fine%2C%20but%20others%20don't.%20It%20seems%20very%20similar%20to%20the%20issues%20described%20in%20this%20blog%20post%2C%20but%20this%20is%20an%20old%20issue%20for%20Windows%20Server%202016%20and%20we%20have%20upgraded%20to%202019%20with%20all%20the%20latest%20updates.%20%3CA%20href%3D%22https%3A%2F%2Fsystemcenterdudes.com%2Fsccm-hardware-inventory-problem-windows-10-1607%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsystemcenterdudes.com%2Fsccm-hardware-inventory-problem-windows-10-1607%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2704295%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704295%22%20slang%3D%22en-US%22%3ESo%20at%20this%20point%20is%20the%20MP%20role%20still%20in%20an%20errored%20state%3F%20Also%20based%20on%20the%20logs%2C%20seems%20like%20you%20have%20SSL%20enabled%20on%20the%20MP%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2704496%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704496%22%20slang%3D%22en-US%22%3EThe%20MP%20role%20itself%20doesn't%20show%20any%20errors.%20It%20thinks%20it's%20working%20fine%2C%20but%20the%20clients%20are%20having%20issues%20with%20some%20BITS%20transfers.%20The%20clients%20can%20talk%20to%20the%20MP%20and%20find%20out%20what%20apps%20and%20updates%20are%20available%20and%20download%20them%20from%20the%20DPs%20with%20no%20issues.%20Uploading%20client%20data%20like%20hardware%20scans%20or%20baseline%20compliance%20and%20downloading%20some%20config%20baselines%20are%20the%20main%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20all%20HTTPS%20with%20an%20internal%20PKI.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2704682%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2704682%22%20slang%3D%22en-US%22%3EThat%20sounds%20like%20a%20phantom%20issue.%20Since%20CM%20was%20originally%20installed%20on%202012%20R2%2C%20the%20pre-reqs%20were%20different.%2C%20Perhaps%20go%20grab%20the%20SCCM%20Preq%20Tool%20and%20re%20run%20it%20for%20your%20server.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fmsendpointmgr.com%2Fconfigmgr-prerequisites-tool%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsendpointmgr.com%2Fconfigmgr-prerequisites-tool%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20run%20it%20Primary%20Site%2C%20DP%20and%20MP%20roles%20to%20ensure%20you're%20not%20missing%20any%20components.%20Then%20see%20if%20that%20fixes%20your%20BITS%20issues%2C.%20Keep%20us%20posted%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2705239%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2705239%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20suggestion.%20That%20tool%20did%20find%20a%20few%20things%20that%20need%20to%20be%20installed.%3CBR%20%2F%3EFor%20the%20management%20point%20it%20installed%3A%3CBR%20%2F%3ENET-Framework-45-Features%3CBR%20%2F%3EBITS-Compact-Server%3CBR%20%2F%3ERSAT-Bits-Server%3CBR%20%2F%3EWeb-ASP%3CBR%20%2F%3EFor%20the%20primary%20site%20it%20installed%20UpdateServices-RSAT%20and%20for%20the%20DP%20role%20it%20installed%20Web-Scripting-Tools.%20After%20it%20was%20done%20I%20removed%20the%20MP%20role%20and%20added%20it%20back%2C%20but%20the%20issue%20is%20still%20happening.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2705494%22%20slang%3D%22en-US%22%3ERe%3A%20Client%20on%20Management%20Point%20doesn't%20work%20after%20in%20place%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2705494%22%20slang%3D%22en-US%22%3EI%20thought%20that%20would%20help%20for%20sure!%20Any%20reboots%20after%20the%20component%20updates%3F%3C%2FLINGO-BODY%3E
Occasional Contributor

Following the docs here https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/upgrade-on-premises-infrastructure  about in place OS upgrade for a CM 2010 install. The servers went from 2012 R2 to 2019. The upgrade worked fine for the primary site server which holds most of the roles (SQL server, Reporting services, WSUS/SUP with shared content folder). I then upgraded our management point which also serves as a secondary SUP. I removed WSUS on both before the upgrades and added them back as described in the docs. The upgrade went fine. I did a site reset to ensure everything is good and there were no issues in the console. Clients are working fine for all features.

After a few days I noticed that the management point is no longer compliant with the configuration baselines. Turns out it hasn't run any of them since the upgrade. I reinstalled the client and it finished with no errors. It seems to register fine. The certificate is fine but then when it tries to download policy or upload messages to the MP (itself), the jobs all error out.

 

The DataTransferService.log show the following sorts of errors repeated:

=============

CDTSJob::HandleErrors: DTS Job '{E27D24C3-091D-4793-92D6-CB8040D35D4C}' BITS Job '{4EA2941A-D5F2-4760-9947-DC6EC8ACD937}' under user 'S-1-5-18' OldErrorCount 415 NewErrorCount 416 ErrorCode 0x80072EFE
CDTSJob::HandleErrors: DTS Job '{3C7E4C35-2A83-4614-9565-608585A49D1C}' BITS Job '{57E58E15-8BEF-41AF-BD25-2F47AA42BC17}' under user 'S-1-5-18' OldErrorCount 131 NewErrorCount 132 ErrorCode 0x80072EFE
CDTSJob::HandleErrors: DTS Job ID='{3C7E4C35-2A83-4614-9565-608585A49D1C}' URL='https : //<MP FQDN>:443/SMS_MP' ProtType=3
CDTSJob::HandleErrors: DTS Job '{ECDFDEFC-2DCF-4570-A0D9-03701B0FF9D2}' BITS Job '{C0EB62DB-F1DC-42E5-94E8-DAE216713B0F}' under user 'S-1-5-18' OldErrorCount 113 NewErrorCount 114 ErrorCode 0x80072EFE
CDTSJob::HandleErrors: DTS Job ID='{ECDFDEFC-2DCF-4570-A0D9-03701B0FF9D2}' URL='https : //<MP FQDN>:443/SMS_MP' ProtType=3
CDTSJob::HandleErrors: DTS Job '{8F8B924E-04B6-4CD1-8928-963E00DE343C}' BITS Job '{5EF47274-86E8-44AA-B9F0-EEDD903D0F37}' under user 'S-1-5-18' OldErrorCount 208 NewErrorCount 209 ErrorCode 0x80072EFE
CDTSJob::HandleErrors: DTS Job ID='{8F8B924E-04B6-4CD1-8928-963E00DE343C}' URL='https://<MP FQDN>:443/SMS_MP' ProtType=3
CDTSJob::HandleErrors: DTS Job '{AC6517A8-EEC9-42F3-9205-215B281F2240}' BITS Job '{64F4719A-9053-400C-BA90-C0AAE00210B9}' under user 'S-1-5-18' OldErrorCount 131 NewErrorCount 132 ErrorCode 0x80072EFE

========================

 

That error source is WinHTTP and means "The connection with the server was terminated abnormally". I see an entry in the IIS logs with a 403 error, but I don't know how to get more details about what is causing it.

 

Looking with bitsadmin it shows the following:

===================

{5211F5B3-89FF-47AC-9BDC-5C67B990CFA7} 'CCM Message Upload {9EF459CF-4EB2-4A75-8FFF-FF400050A3B8}' TRANSIENT_ERROR 0 / 1 0 / 14138
{73F46E79-CD10-4846-840E-7ECD0CCBB976} 'CCM Message Upload {6CE3E579-1C78-4E2D-A1C6-C7118BBAA75E}' TRANSIENT_ERROR 0 / 1 0 / 24650
{9B0D204F-0D88-4683-8800-ADE66C176A0C} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{63EA641C-266A-4EC5-A428-D3DC30266040} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{B6C82074-7794-4A34-999A-3938A2216933} 'CCMDTS Job' TRANSIENT_ERROR 0 / 28 0 / UNKNOWN
{D68CF136-7EFB-4F5F-8E56-7B03C6C83830} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{47152487-B6AA-4134-BBD8-83A85467B8E5} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{90F73916-3F8C-48CD-B201-7F3AD9A5003F} 'CCMDTS Job' TRANSIENT_ERROR 0 / 3 0 / UNKNOWN
{DF682297-9FFE-4348-B104-FB344B178C13} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{6A839CF0-45BB-453A-98D9-F75343BE97D5} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{EA51C2C6-EEB4-4018-AC8A-E0475BD53513} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{2471FF3C-FD78-4BB4-A037-7E146619FDB8} 'CCMDTS Job' TRANSIENT_ERROR 0 / 4 0 / UNKNOWN
{6E50A082-1771-4147-B06A-76DD40DD6DAD} 'CCMDTS Job' TRANSIENT_ERROR 0 / 28 0 / UNKNOWN
{454513C9-AC01-43E1-B0E8-102FBE25779E} 'CCMDTS Job' TRANSIENT_ERROR 0 / 57 0 / UNKNOWN
{34F8B723-1371-461C-A4C5-A4866323EC44} 'CCMDTS Job' TRANSIENT_ERROR 0 / 57 0 / UNKNOWN

===============

 

If I delete the bits jobs, they just come back again of course. I don't know if it is useful to anyone, but when I run a bitsadmin on the job I get the following info.

=================

bitsadmin /info {5211F5B3-89FF-47AC-9BDC-5C67B990CFA7} /verbose

BITSADMIN version 3.0
BITS administration utility.
(C) Copyright Microsoft Corp.

GUID: {5211F5B3-89FF-47AC-9BDC-5C67B990CFA7} DISPLAY: 'CCM Message Upload {9EF459CF-4EB2-4A75-8FFF-FF400050A3B8}'
TYPE: UPLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\SYSTEM
PRIORITY: NORMAL FILES: 0 / 1 BYTES: 0 / 14138
CREATION TIME: 7/30/2021 5:26:37 PM MODIFICATION TIME: 8/3/2021 7:27:22 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 1209600 ERROR COUNT: 1193
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE: https : //<MP  FQDN>:443/CCM_Incoming/{9EF459CF-4EB2-4A75-8FFF-FF400050A3B8} -> D:\SMS_CCM\ServiceData\LocalPayload\{9EF459CF-4EB2-4A75-8FFF-FF400050A3B8}
ERROR CODE: 0x80072efe - The connection with the server was terminated abnormally
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION:
JOB FILES:
0 / 14138 WORKING https : //<MP  FQDN>:443/CCM_Incoming/{9EF459CF-4EB2-4A75-8FFF-FF400050A3B8} -> D:\SMS_CCM\ServiceData\LocalPayload\{9EF459CF-4EB2-4A75-8FFF-FF400050A3B8}
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ? true

Peercaching flags
Enable download from peers :false
Enable serving to peers :false

CUSTOM HEADERS: NULL
CLIENT CERTIFICATE INFORMATION:
Certificate Store Location : CERT_STORE_LOCATION_LOCAL_MACHINE
Certificate Store Name : MY
Certificate Hash : 41C2067A522B94550F626B1A136015C4C6FE46D9
Certificate Subject Name : NULL

HTTP security flags
Enable CRL Check :true
Ignore invalid common name in server certificate :false
Ignore invalid date in server certificate :false
Ignore invalid certificate authority in server certificate :false
Ignore invalid usage of certificate :false
URL redirection policy :Redirects will be automatically allowed.
Redirection from HTTPS to HTTP allowed :false

=================

The certificate hash in the job is the same one that shows in the ClientIDManagerStartup.log in the client log folder.

======

>>> Client selected the PKI Certificate [Thumbprint 41C2067A522B94550F626B1A136015C4C6FE46D9] issued to '<MP FQDN>' ClientIDManagerStartup 8/3/2021 5:59:50 PM 5304 (0x14B8)

======

 

I've been scouring the web for a few days now and can't seem to find anything to help. I see no other obvious errors in the log files.  Again, no other machines are having this issue.

 

I know I could probably remove the MP role and reinstall or bring up a new MP, but I would rather not as this is my dev server that I was testing the in place upgrade on before I did the same thing in prod and I'm not looking forward to having to make those sorts of changes this close to the start of the semester on the prod side if the same thing happens when I upgrade prod. Anyone have any ideas?

17 Replies
Anyone have any ideas? I am seeing other computers that aren't config manager servers also showing similar problems in the dataTransfer.log file. They aren't sending in hardware inventory to the management point or they are having issues downloading bits jobs from the management point.

This inplace server OS upgrade has not been a smooth process.
I posted to Reddit as well and got some pointers saying you need to remove the MP role if you fully reinstall the client. No links to any specific docs, more just "I've heard" sort of thing.

I removed the MP role, but left the SUP role. This seemed to remove the client at the same time. At least it removed the Control Panel entry.
I then reinstalled the MP role and then installed the client. They both exited setup with error code 0, but the issue still remains.
I dug into the logs a bit more and it seems like it's something to do with the certs maybe.
Keep in mind this is all on the management point itself and we do require HTTPS via an internal ADCS PKI. If I look at one of the errors in the DataTransferService.log and grab the BITS job:

CDTSJob::HandleErrors: DTS Job '{F0AD54F5-7364-49BE-91C4-33BA0DED45DC}' BITS Job '{20FFFB81-7308-4187-832D-500312F8B7D6}' under user 'S-1-5-18' OldErrorCount 1397 NewErrorCount 1398 ErrorCode 0x80072EFE DataTransferService 8/25/2021 9:46:47 PM 1316 (0x0524)

Then checking the bits job, I can get the URL (https://SERVER-FQDN:443/SMS_MP/.sms_pol?%7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.SHA256:52BC11A0A1...)
=====================
bitsadmin /info '{20FFFB81-7308-4187-832D-500312F8B7D6}' /verbose

BITSADMIN version 3.0
BITS administration utility.
(C) Copyright Microsoft Corp.

GUID: {20FFFB81-7308-4187-832D-500312F8B7D6} DISPLAY: 'CCMDTS Job'
TYPE: DOWNLOAD STATE: TRANSIENT_ERROR OWNER: NT AUTHORITY\SYSTEM
PRIORITY: HIGH FILES: 0 / 1 BYTES: 0 / UNKNOWN
CREATION TIME: 8/20/2021 4:11:01 PM MODIFICATION TIME: 8/25/2021 9:30:13 PM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: REGISTERED NOTIFICATION FLAGS: 11
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 28800 ERROR COUNT: 1380
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE: https://SERVER-FQDN:443/SMS_MP/.sms_pol?%7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.SHA256:52BC11A0A1... -> D:\SMS_CCM\Staging\{33B321B6-72BD-4827-95FF-623A04B7CE53}.3.00.tmp
ERROR CODE: 0x80072efe - The connection with the server was terminated abnormally
ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed.
DESCRIPTION:
JOB FILES:
0 / UNKNOWN WORKING https://SERVER-FQDN:443/SMS_MP/.sms_pol?%7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.SHA256:52BC11A0A1... -> D:\SMS_CCM\Staging\{33B321B6-72BD-4827-95FF-623A04B7CE53}.3.00.tmp
NOTIFICATION COMMAND LINE: none
owner MIC integrity level: SYSTEM
owner elevated ? true
This job is read-only to the current CMD window because the job's mandatory
integrity level of SYSTEM is higher than the window's level of HIGH.
Peercaching flags
Enable download from peers :true
Enable serving to peers :true

CUSTOM HEADERS: NULL
CLIENT CERTIFICATE INFORMATION:
Certificate Store Location : CERT_STORE_LOCATION_LOCAL_MACHINE
Certificate Store Name : MY
Certificate Hash : 41C2067A522B94550F626B1A136015C4C6FE46D9
Certificate Subject Name : NULL

HTTP security flags
Enable CRL Check :true
Ignore invalid common name in server certificate :false
Ignore invalid date in server certificate :false
Ignore invalid certificate authority in server certificate :false
Ignore invalid usage of certificate :false
URL redirection policy :Redirects will be automatically allowed.
Redirection from HTTPS to HTTP allowed :false

================
Finally if I look in the IIS Log for that URL I see a 403.7 error which from what I can tell indicates a mutual cert auth error.
============================
2021-08-26 01:46:47 10.10.28.120 HEAD /SMS_MP/.sms_pol %7B33B321B6-72BD-4827-95FF-623A04B7CE53%7D.SHA256:52BC11A0A11362FDE7CF392B055993FE9E2BB81CF5A8BF4F69A19C5CE9D7E2DB 443 - 10.10.28.120 Microsoft+BITS/7.8 - 403 7 64 1

================
In order to rule out every issue with certs, I deleted all the certs except one that is configured for both client and server auth and is the one setup for IIS. I verified in the ClientIDManagerStartup.log that it had selected that cert for the CM client. Going to the IIS server from the client browser shows no issues and of course other machines can talk just fine to the MP.
Anyone have any other ideas or know how to get more detailed logging from BITS on IIS?
I've now removed the CM roles, all pre-requisites and then reinstalled and I am still seeing BITS errors from multiple clients talking to the MP. Some downloads and uploads seem to work fine, but others don't. It seems very similar to the issues described in this blog post, but this is an old issue for Windows Server 2016 and we have upgraded to 2019 with all the latest updates. https://systemcenterdudes.com/sccm-hardware-inventory-problem-windows-10-1607/
So at this point is the MP role still in an errored state? Also based on the logs, seems like you have SSL enabled on the MP?
The MP role itself doesn't show any errors. It thinks it's working fine, but the clients are having issues with some BITS transfers. The clients can talk to the MP and find out what apps and updates are available and download them from the DPs with no issues. Uploading client data like hardware scans or baseline compliance and downloading some config baselines are the main issue.

We are all HTTPS with an internal PKI.
That sounds like a phantom issue. Since CM was originally installed on 2012 R2, the pre-reqs were different., Perhaps go grab the SCCM Preq Tool and re run it for your server.

https://msendpointmgr.com/configmgr-prerequisites-tool/

I would run it Primary Site, DP and MP roles to ensure you're not missing any components. Then see if that fixes your BITS issues,. Keep us posted
Thanks for the suggestion. That tool did find a few things that need to be installed.
For the management point it installed:
NET-Framework-45-Features
BITS-Compact-Server
RSAT-Bits-Server
Web-ASP
For the primary site it installed UpdateServices-RSAT and for the DP role it installed Web-Scripting-Tools. After it was done I removed the MP role and added it back, but the issue is still happening.
I thought that would help for sure! Any reboots after the component updates?
Does other clients connecting to this MP have the same issue? Or is it only the client on the MP itself?
Yes, other clients also have the issue.
Try resetting the BITS queue manually:
net stop bits
Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
net start bits
I have done that. The BITS jobs just get recreated by the CM client.
Hi,
Have you check SSL setting (Enable RequireSSl) for the APIRemoting30, ClientWebService, DSSAuthWebService, ServerSyncWebService, and SimpleAuthWebService virtual directories.
Have you run this commandline for WSUS :
Program Files\Update Services\Tools\WSUSUtil.exe configuressl <SUP.FQDN>

Sources (Read the « Update 2 ») :
https://sccmentor.com/2021/07/27/in-place-upgrade-of-configmgr-site-server-from-windows-2012-r2-to-2...
Thanks for the response Renald. I have done all those steps. But, we don't have any issues with updates or DP communications. It's mainly clients uploading and downloading policy/device data to the management point.
Hi,
Ok, any chance it can be an antivirus, proxy, firewall related issue ?
CRL is enable, have you check clients cert wasn’t revoked ?
Have you try to troubleshoot a client with Microsoft Support Center Client Tools ? (You can do live monitoring and troubleshoot on client policy, cert, apps, updates, etc.)

Thanks for the suggestions.

There are no AV alerts and we only use Windows Defender. The proxy settings and firewall settings have been checked. The servers are talking fine. I see the 403.7 errors in the IIS logs, so the communications are getting there, the mutual cert auth is just failing for some reason.

CRL is enabled and the certs all check out fine from the OS level. I have also tried the support center client tools with no luck.

It's something to do with BITS mutual cert auth, but I couldn't find any root cause beyond that and nothing online was helpful. I ended up just creating a whole new management point on a fresh server 2019 box and switching everyone to that. That resolved the issue. I guess this thread will just be a warning that an inplace upgrade of the server OS isn't always a slam dunk.