Windows Server 2022 - Problema com a conta de domínio administrador no Microsoft Edge
Windows Server 2022 - Problema com a conta de domínio administrador no Microsoft Edge
I have tried everything possible but Edge remains blocked. It repeatedly displays "This app has been blocked by your system administrator."
Actions taken:
- Installed all GPOs from Administrative Templates in Microsoft.
- Enabled "Allow Microsoft accounts to be optional."
- Turned on "UAC: Admin approval mode for built-in admin accounts."
- Enabled "UAC: Run all admin accounts in Admin approval mode."
- Allowed elevation without prompting "UAC: Behavior of the elevation for admins in admin approval mode."
- Adjusted Security Settings in Control Panel to "Never Notify."
Still facing issues with Edge being blocked by my admin account! Any suggestions?
I’m using Windows Server 2022 - 21H2.
Does Edge work properly from a non-admin account? Or, have you installed and tried an alternate browser?
This is a security feature and not something you should bypass (running via the admin account).
Well, for your information and you may already know this, Microsoft Edge is available to be used by the admin account from scratch and even after promoting the server to a domain controller so whether it's a good idea to or not to use the web on an admin account isn't really a security issue considering there is always access to the server from some standpoint at all times, even when using active directory for remote computers that still need to access business information and if properly setup, there is minimal security issues to deal with.
With that, it is possible to use Edge, why am I having the issue now is what this discussion is about. If you don't have any input on that, then try and get your tommy points somewhere else. I did run a power shell script that installed baseline GPOs from Microsoft's Security Compliance Toolkit (another reason to have the need to access the web) and I think the problem lies in there. I have blown the whole server away and started fresh so I'll try and figure it out eventually. Any idea if regedit might something I have to change deep down in there. If I post the powershell script, would that help identify the problem for us?
Thank you!