![]() Require an update for SHA-2 code signing support: Standards, Microsoft now only signs Configuration Manager binaries This issue is caused due to requirement changes for SCCM version 1906 which requires clients with SHA-2 code signing support as per the link What’s new in version 1906 Version 1906 client requires SHA-2 code signing supportīecause of weaknesses in the SHA-1 algorithm and to align to industry ccmsetup 9:41:30 PM 1516 (0x05EC) Enumerated all 1 DP locations but none of them is good. Message with STATEID='316' will not be sent. Pre-req file name: C:\WINDOWS\ccmsetup\ccmsetup.cab' ccmsetup 9:41:30 PM 1516 (0x05EC) A Fallback Status Point has not been specified and no client was installed. ccmsetup 9:41:30 PM 1516 (0x05EC) Failed to get client version for sending state messages. Couldn't verify 'C:\WINDOWS\ccmsetup\ccmsetup.cab' authenticode signature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |