Security policies on this PC are preventing you from changing this setting


Recommended Posts

Fixed this already, but just a FYI as Google doesn't have this listed:

This appears in the Metro Control Panel under Users after I tried adding an Exchange account to the Mail app, and acknowledged the following security-related dialog without thinking.

With that setting enabled, your PC will lock itself after dimming the screen or after waking it from sleep - your Power Options settings have no effect here. Having your PC prompt you for your password after waking up or idling isn't particularly helpful if you're on a single user desktop at home.

Disabling it is simple but not particularly straight forward at first: go to the desktop Control Panel, User Accounts, and click "Reset Security Policies" on the left. That should do the trick.

  • Like 2

That's a security policy set in place because you've connected to an Exchange account that requires that policy be in place in order to use it. That's not something to fix...that's intended behavior.

Unless I'm not understanding something that you've said.

Is that policy set server-side?

In addition the policy remains even if you remove the Exchange accounts in question from the Mail app, or uninstall the Mail/Calendar/People/Messenger apps.

My point was, this policy seems a bit unnecessary for a non-portable single user desktop that rests at home, especially since the Mail app is the first non-web client to ask about this policy.

Yes, that policy is set server side. The same thing happens with all of my phones when I connect them to my work e-mail via Exchange. It's a way to prevent your work e-mails (and other items) from being read/used by anyone who walks up and tries to use the machine. It's fairly standard practice.

The policy will remain in effect after removal until you tell it to disable the setting. That's a trivial matter to take care of usually. :)

  • 2 months later...

Interesting... so it does continue to work after disabling the security policy.

Perhaps it'll bug you later to enforce it, else it stops syncing.

  • sc302 locked this topic
This topic is now closed to further replies.
  • Posts

    • According to Microsoft, Cause: One of the drivers controlling the device notified the operating system that the device failed in some manner.   https://support.microsoft.com/en-us/topic/error-codes-in-device-manager-in-windows-524e9e89-4dee-8883-0afa-6bca0456324e
    • This looks awesome, I will request access via Steam later this afternoon!
    • Personally, I’ve found that it’s usually worth investing in the infrastructure you don’t want to replace later, especially cabling. Running Cat6A (or better, depending on your needs) during an upgrade is relatively inexpensive compared to having to re-cable a few years down the road. For switches I try to balance current specs with realistic growth. If my budget allows it Ill choose switches with higher uplink speeds which leaves room for expanding later on, but I don’t necessarily overspend on access ports if the endpoints won’t benefit from them anytime soon. One lesson I’ve learned is that planning for scalability pays off. It’s much easier to add devices, VLANs, or higher-bandwidth workloads when your network infrastructure already supports it than to replace hardware later.  What is your budget like?
    • I hate the term, "future-proof." We saw it back in the 90's / 2000's, if not before. You cannot future-proof anything, since there is no definition of how far into the future you plan on prepping for. Best idea is to tell us what you currently have and what its use is at the moment, and we can then offer ideas about some areas that might need an upgrade and other areas that can be left alone.
    • I can agree that it is being used in a small capacity. I worked for a company where their engineers still used XP, and when asked why it was because their sensor software wasn't compatible with newer operating systems and the software was discontinued so they couldn't upgrade the software. Given that the sensors were still in use by companies, they had to continue using XP to support the sensor, otherwise the price to the company would have gone into the millions or billions. Our response was simple: Ok, you can keep the XP machine. But we're removing it from the network. "But then it can't access the Internet or folder shares!" Yup, kinda the point. If someone wants to continue using an unsecure OS they can do, I have no problem with that. But it should be isolated. Simple. I had a fight with a guy in the engineering department for weeks before he finally relented. But we digress.   What do I plan on doing to commemorate the anniversary? Nothing. I have fond memories of the OS, but at the end of the day it's just an OS. If I had some time I might see if I could install it on my Raspberry Pi for a laugh. But my reflex memory with today's OS ideas would probably get me frustrated and I'd uninstall it after 5 mins.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      539
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      154
    4. 4
      Steven P.
      99
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!