A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
This doesn't have to be a feature; but a how-to guide would be sweet. Key points are to cover the usage of a self-signed cert or usage of PKI and where and how it needs to be configured in the OSD Task Sequence and also how to setup the collections for the deployments
Hey Steven, here's the OSD guide :) https://patchmypc.com/applications-fail-to-install-during-osd-in-sccm-with-error-authorizationmanager-check-failed-0x87d00327
Actually check this one out: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/36516268-install-third-party-software-updates-during-ts-ins
It may not, I haven't tested it. I know not all client settings apply during OSD. If it doesn't, this would be a good feature request for the SCCM UserVoice at https://configurationmanager.uservoice.com/forums/300492-ideas
Simply overlooked it, some reason I thought during OSD we don’t have client policy for this. 🥺
Here's a guide that covers PKI: https://www.youtube.com/watch?v=lqapp8j7CHk
As for PKI vs. Self-signed it really will depend on the organization. I'm not sure there's really much to talk about with configuring the signing certificate with clients especially since it's pretty easy if you enabled the new option and client settings in SCCM https://docs.microsoft.com/en-us/sccm/sum/deploy-use/third-party-software-updates#enable-third-party-updates-on-the-sup?