Heck, I'd go one further and say you should be able to embed a PowerShell script in the Deployment Type configuration. ConfigMgr already supports embedding PS scripts in many other components, not having it in Deployment Types seems like an omission.
1,403 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Saw a working demo of this recently so updating to planned.
Agreed this would be a brilliant feature, but I'm assuming it's a little harder to implement in SCCM as unlike, for example, the Exchange Management Console, the ConfigMgr Console is not actually using PowerShell and WinRM in the background - it still relies on WMI to the SMS Provider.
@Andrew M - The downside there would be that Configuration & Compliance would become dependant on WMF 4. That said, it does feel like there's a lot of overlap between the two functionalities that could do with some rationalisation.
Phase 1 of these feature is in 1602 production
Regarding the talk of using PS remoting, I think I'd rather see this kind of functionality, if built into the console, use the existing communication channels (Fast Channel notification and standard policy items). I do see the value of PowerShell based commands (we use Ryan's tools), but it introduces yet another dependency. If you've got working communication between client and server, that should be enough.
It's actually a feature I really miss from LANDesk. There could be a firewall blocking all communication between server and client except the LANDesk channel, and even if I had no administrative rights on the client, I could still kick off a hardware inventory or a variety of other commands, and get real-time feedback on the results.
Posted this again https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8803711-3rd-party-patching-scup-integration-with-sccm-co originally, but this is probably the correct "idea" for it.
Ideally, I'd like to see functionality that allows to you add 3rd-party catalogue URLs in the ConfigMgr console and then, before it triggers the usual scheduled WSUS sync with MS Update, it first syncs any third party catalogues and pushes the data into WSUS.
You can then use ADRs to create deployments of 3rd-party software exactly as you do with MS software.