Replies: 2 comments 4 replies
-
Smart move! 👌 |
Beta Was this translation helpful? Give feedback.
-
That's indeed the reason we're using it this way. A lot of software automatically updates but not everything. We want to have all software up to date even it's not used at the moment. This way we make sure the software is already up to date when it's started again after a long time. Also this way we have a better overview of outdated software in Microsoft Defender. I've tried to disable the Winget-AutoUpdate task and add triggers to the Winget-AutoUpdate-UserContext. Now it runs only in the user context so that would work. Is there any way to set this up through a policy? Right now we're only testing with a small amount of devices but eventually we'd like to deploy it to 700+ devices. |
Beta Was this translation helpful? Give feedback.
-
We've implemented Winget-AutoUpdate through Intune using ADMX-templates.
For applications installed in system context we'll provide updates through Intune. However we would like to update applications installed in the user-context.
Right now we've managed to do so by setting up a whitelist and using the option to ignore the black/whitelist in user context. This way nothing in the system contexts gets updated, but everything in the user context will be updated. However this means we're not able to use the black or whitelist anymore for what they're designed to do. It would therefore be nice to have separate black/whitelist for user and system context or at least an option to not install any updates in the system context.
Beta Was this translation helpful? Give feedback.
All reactions