Currently, if any application is deployed as available the user will get a 'New Software is Available' notification every single time the client starts. Forever. In 1610 a 'new' banner was added to the icons which goes away after 7 days. That's great but then so should the notification. To not tie these together greatly reduces the value of both of them since user are now expecting to see 'new' icons in the Software Center when they get notified that new software is available. After a few weeks of that they just stop paying attention to the notification.
In addition, as of 1610 new deployments will have a 'new' banner of them for 7 days.
Although making it more prominent like you describe users can already do this via the Software Center by navigating to Options > Computer Maintenance and clicking Sync Policy. I know ... that's buried but it is there.
The trick would be to secure the account used to access the LAPs password from AD. If in implementing this solution they made those account vulnerable in any way, shape, or form then the attacker now has access to every admin password stored plain-text in a well documented AD attribute.
To add on to this; in my experience this notification is **** near permanent. While the 'new' banners disappear after 7 days the notification seemingly never does. Everytime users log in after a reboot they get that prompt.
Martin, I agree wholeheartedly and would add Windows 19 to this as well. I've discussed this with the product team a bit and commenting to this effect over on the Patch Tuesday item: https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8819518-software-update-patch-tuesday-scheduling
Updating status to Noted.
We have a couple of similar items for a ‘connected’ stand-alone media. I’ll most likely merge with those, the idea being to remove the restrictions for SMP, Dynamic App etc. from Stand-alone.
See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/ for details on what the status values mean.
A slight revision to this that also might be useful: Offline while in WinPE only. Imaging over wireless isn't supported and even if it was I'm not sure we would want to do so for congestion purposes. So having an option where everything occurs offline while in WinPE (where we won't have wireless connection) and then flipping to online once in the full OS (where we now have wireless) would be pretty shiny.