Windows 10: Protected users - Ntlm fallback

Hi, I'm testing the protected users group in Active directory, and I'm testing this with a highly privileged user which is not able to access a remote machine using RDP, and by the logs it looks like the user falls on Ntlm, which receives an error message since Ntlm is not allowed for members of the protected users group. The user is trying to login to a remote machine by Fqdn and not an IP address. In the event logs I couldn't find any event log, such as event log 4771 which will shed some light over the reason for the kerberos ticket to be denied, kerberos audit logs were enabled in the gro

:)

 

Current active users that are friends

The other reason I suggested this is that users can add characters to their username that are not alphanumeric (e.g. user*). This confuses things somewhat when looking at the list.

 

Clear Windows Security Center (Defender) Protection History

Did not work for me. After going through all steps I still have protection history full

 

Edge Search Does Not Permit Change of Region


I got these suggestions from the Microsoft Community forum.No. 1 worked for me:

Thank you for posting the query on Microsoft Community. I am glad to assist you on this.
We have reproduce the issue here and we are able to access non-regional search for google using Microsoft Edge.
I would suggest you to try the below steps and check if it helps.
Step 1:
Clear browsing data option of Microsoft Edge and check if you face the issue. To do so perform the steps below.

1. Click on the More actions icon next to the feedback icon present on top right corner of the Project Spartan homepage.
2. Select Settings and click on Choose what to clear.
3. Check the boxes Browsing history, Cookies and saved website data and Cached data and files and click on Clear.

Step 2:
I suggest you to create a new user account and check if the issue occurs.

1. Go to Settings.
2. Choose Accounts and then select Family and other users.
3. Select add someone else on this PC.
4. Enter a user name and hit next.
5. Click on Finish.
6. Sign out from the current Account and Log into the new account.

Step 3:
It could also happen because of network issue. I suggest you to try with different network connection and check if it helps.