Messages

+1 for the superseded model as we create new SUGs each time the ADR runs and it could be over a month before even hitting some systems. The defer expiration of updates model could work for us, however there'll be some exceptions whereby we'd need the 30 day limit increased to 60 days, say.

Thanks that's much better than I imagined.

Prior to the apps are being published into WSUS. For example a larger enterprise may have different subsidiaries or business units all on the same CM infrastructure and may want to break down the report by servers/OS etc whereby a report on that collection could help with the business case #smallthings

One last thing... We're considering implementing this on a subset of the business to begin with, as such an optional Collection ID field would be useful.

Nifty. Thanks Justin - worked a treat 

Hi there. We're currently on the trial version of the product and we're wondering if it's possible to use the option to "Connect to your CM database to scan installed applications that are also supported in our catalog" but to compare against the full catalog? Management wants to see the value-add of the spend. If not, would purchasing a very small number of licenses be a valid alternative? Thanks in advance.

Hi there, this should be a simple one to add.. I was wanting to add a schedule for the last Sunday but noticed the drop down only covered 1st through 4th. Any chance we could get that added at some point?

Awesome 

I think this is a little different in that the request is to skip the update if the wfica32.exe (user context) is detected. Would the option to "Skip update installation if conflicting processes are running" work in this case?

[Request New Features or Software | Microsoft SCCM (Enterprises/Paid)]

This should probably go into a new/modified category Request New Features or Software | Microsoft SCCM (Enterprises/Paid)...

This is minor but figured it would be useful to have a tab in the GUI with the current product version, last self-update date/time and embed the release notes. The latter could be useful to ensure we're all taking advantage of the latest improvements and aware of any fixes #smallthings

Could this be related to the following Windows 10, version 1809 re-released issue documented below?

Apple has identified an incompatibility with iCloud for Windows (version 7.7.0.27) that may cause users to have issues updating or synching Shared Albums after updating to Windows 10, version 1809. Users who attempt to install iCloud for Windows (version 7.7.0.27) on Windows 10, version 1809 will see a message stating that this version of iCloud for Windows isnÔÇÖt supported, and the installation will fail. To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Window 10, version 1809 until this issue has been resolved.

https://support.microsoft.com/en-us/help/4464619/windows-10-update-history

+1 this request, handy feature for larger enterprises