![]() Your users will retain the ability to disable notifications for all other apps on a per-app basis. With this approach, you need to control 2 settings:Įnsuring the master notifications switch stays enabledĮnsuring that notifications for your custom AppID stay enabled Here's a blog that will show you how to create your own custom AppID: This is significant because it allows me to limit my policies only to my custom toasts. In my org, I created a custom/branded AppID with corporate logos specifically for this purpose. ![]() So I think one of the best things you can do for these custom notifications is to NOT associate them with the Software Center AppID. There are improvements to this in 1906, but still. Users are not wrong for wanting to disable them entirely. ![]() I'm doing the same types of custom toast notifications in my environment, so I'm happy to share how I'm managing this.įirst thing to acknowledge on this topic is that Software Center has a history of being really spammy when it comes toast notifications. The "right" answer will depend on your environment, but it's almost always somewhere in the middle. You've clearly hit on a controversial topic here. Get your CISO to sign something that says all Windows domain-joined PCs need to see notifications, and force that reg setting. So that is an option, if you believe notifications are an important part of your coordination with your users. We've had one complaint so far, and she's the old hag who insists on using Thunderbird. We use the same argument to push out desktop icons. We have political precedence in that we have an agent running on all machines that points people to our intranet, our internal shopping app, documentation etc., and people complain about it, but it's written down on a paper somewhere that ALL employees must have equal and direct access to all of our central services. We started using Group Policy Preferences to push out new desktop shortcuts and delete the old ones. Some icons were in the Default Desktop and were not functioning because the apps didn't exist anymore. Some icons were in the Public Desktop, where people couldn't delete them. If users think IT just exists to fix things when they break, then you can't proactively manage anything - you don't have the authority to do so.Įxample: We didn't centrally manage desktop icons until a few weeks ago. But IT is also sometimes a closed loop system, where the users need to work with us to make things go around. I totally agree that controlling users will become a pain in the butt, because it means more work for you. On the other hand, just get it written down by someone on a higher payroll than you. If you utilize it, be prepared for some backlash from the users that choose to disable it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |