You have nice user guides for patchmypc application using ConfigMgr, or using Intune, but i would very much like one guide that transitions from ConfigMgr to Intune so you get the best of PatchMyPC while Configmgr is in a co-mgmt state. What requirements must be in place, are there any co-mgmt issues that needs to be adressed. Can one use co-mgmt workload to create transition rings while moving parts the patching of the devices up there. Basically some guides on how to use PatchMyPC to patch 3rd party applications in both worlds when some clients are on ConfigMgr, while others are in Intune.
"Why bother having a "Documentation" category if you guys keep ignoring it.."
We're not ignoring you, we just didn't realise there was a Documentation category :-) I've updated your request to noted and made an internal work item (as promised via Twitter DM) to investigate this.
"Jasons article says SCUP on WSUS, but what does WSUS have to do with 3rd party patching in Intune. Why even bring it up"
Jason's mentioning of SCUP was because he needed to illustrate the creation of an independently published third party update, without referencing any particular vendor e.g. Patch My PC.
You've asked quite extensively for guidance on how to effectively patch devices with third party updates for an environment in a co-managed state between ConfigMgr and Intune. Whether you're going to even need/want WSUS/ConfigMgr depends on your strategy.
Overall I think you ask good questions and I can totally see the confusion here. I'll likely reach out to you at some point for feedback on a draft post when I make progress on it and I'll do my best to bring answers to all your questions.
I'm sorry for the confusion caused, I openly admit I did not read your initial request fully.
In the mean time, you can totally have a call with us to go through these questions 1-on-1 in a review call while looking at your environment and config. Book that here: https://patchmypc.com/review.
Why bother having a "Documentation" category if you guys keep ignoring it.. And keep referring to articles that has nothing to do with my request in general. Jasons article says SCUP on WSUS, but what does WSUS have to do with 3rd party patching in Intune. Why even bring it up.
Let me make it simple.
Show me the guide that explains the best option and how to use PatchMyPC client application to handle 3rd party updates on both ConfigMgr and Intune at the same time for both Intune clients and Configmgr clients. Your Intune guide says i need to install the application in Intune Standalone mode to use with Intune. Are you saying that is correct,? what happens to my Configmgr client if i reinstall with "intune standalone". Whivh workload needs to be moved from ConfigMgr to Intune. Will this change also affect the Software Center that i use to publish 3rd Party Applications from PatchMyPC application.
Are there any other settings or modifications that can break or needs to be changed for this hybrid workload to function properly.
And again. please remove the Documentation category is you guys are not willing to accept requests for it...
This would not be the place to request a guide or video. Our idea portal is for new features and applications.
Regarding third party updates and co-management there is already a great article by Jason Sandy’s that covers this. Please find the link below.
If you have specific questions or run into issues feel free to put in a ticket and we will help however we can.
You are not understanding the idea. Im talking about putting PatchMyPC into Hybrid mode..Using both ConfigMgr, and Intune for patching 3rd party applications when ConfigMgr is in a Co-mgmt mode.
There's lots of community resources out there on how to start co-management, e.g. a blog series here by MVP Ben Whitmore: https://byteben.com/bb/co-management-series-merging-the-perimeter-part-1-what-is-co-management
This platform is primarily setup for handling customer feature and catalogue application requsts so I'll need to close this however we appreciate the feedback and the nice words about our guides.