We are happy to have introduced the long-awaited capability of supporting the publishing of patches via Intune. We were repeatedly delayed as the necessary APIs remained in beta with Microsoft longer than anticipated. But they were finally released for general availability and we’ve leveraged them to provide our initial integration. In the spirit of agile, we were anxious to get the capability in your hands for real-world use outside our labs to accept your feedback. Below is a list of known issues and upcoming enhancements as of March 19th, 2021. Fixes for the bulk of the known issues below are being worked on now, with many scheduled to be addressed in our February update.
Known Issues
- If multiple paths are passed as detection rules, it will fail, if not all paths are available in the system. (Q1)
- Workaround: Pass path that is relevant to the deployment machine. You can choose specific paths from Step 3 of the patch wizard.
- For sps.exe, uninstall string may not be properly set right now, but such does not impact the installation of package. (Q1)
- Today the install and uninstall string for SPS packages is set to the same value in Intune when a publish is made. A dummy uninstall string will be set in Intune for SPS packages. This does not impact the installation.
- For some patches, a simple return code may not good enough to confirm a successful installation. It is possible a device may have got new software, but Intune interface could show a return code that suggests failure. (H1)
Planned Enhancements
- The ability to pass deployment assignments from SVM (H1)
- Certificate support for authentication (H1)
- The ability to manage multiple detection rules and requirements (H1)
- Ability to publish to multiple distribution system via single patch daemon (H2)
- Automated Timestamp signing (H2)
- The ability to leverage Intune for deployment of the SVM scan agent (Q1)
Is there more you'd like to see? Please leverage our Ideas portal to share and vote on the ideas of others!
