This behavior results from a change to Windows. In particular, applications that access the user's profile information in Active Directory will be denied access. This behavior is most likely to occur if your domain controllers are running Windows Server 2016 or later, and users attempt to connect by using a customized connection app. If your deployment uses a group policy object to remove Everyone, you may need to restore access by updating the group policy object to add Remote Desktop Users.Īccess denied, A remote call to the SAM database has been denied If you have more than one computer in your deployment, use a group policy object.įor example, the default membership for Access this computer from the network includes Everyone.
If the list doesn't include either Remote Desktop Users or a parent group like Everyone, you must add it to the list.Check the list of users and groups for Remote Desktop Users (or a parent group).Navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment, right-click Access this computer from the network, and then select Properties.Open Group Policy Object Editor (GPE) and connect to the local policy of the remote computer.If the user is already a member of this group (or if multiple group members have the same problem), check the user rights configuration on the remote Windows 10 or Windows Server 2016 computer. If this issue affects a single user, the most straightforward solution to this issue is to add the user to the Remote Desktop Users group. Modify the user's group membership or user rights assignment For example, Windows 7 clients do not have this issue.
The system administrator has restricted the type of logon (network or interactive) that you may use. In this situation, a Windows 10 user attempting to connect to Windows 10 or Windows Server 2016 computers is denied access with the following message: This article addresses several issues that can cause problems that affect user authentication.
0 kommentar(er)
