If you try to connect to the computer using Remote Desktop and login to the user account that has no password set, you will get the error “Login failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced”.
Clicking the OK button will instantly boot you off the remote desktop connection.The error happens because in Windows operating system such as Windows XP, Windows Vista, Windows 7, Windows Server 2003 and Windows Server 2008 (or their R2 versions) does not allow local user to log on remotely via network logon if the user account does not have a password set.Setting a password for the user account that you want to login solves the problem but that would also mean you would have to type in the password every time you start the computer. You can also however disable the blank password check to allow Remote Desktop connection to login to account without password.1. Click the Start button and type gpedit.msc in the Search programs and files bar and hit enter.2.
At the left pane, go to Local Computer Policy Computer Configuration Windows Settings Security Settings Local Policies Security Options3. Look for “Accounts: Limit local account use of blank passwords to console logon only” and double click on it.4.
Hp officejet 100 mobile printer driver windows 7 64 bit. By default the Enable option is selected and all you need to do is select “ Disable” and click OK.Now you can connect to the computer using Remote Desktop and login to the user account that don’t have a password. Some Windows such as the XP home doesn’t have gpedit.msc and you will have to make the changes from registry.1.
Type regedit at the Search programs and files bar and hit enter.2. Navigate to HKEYLOCALMACHINESYSTEMCurrentControlSetControlLsa3. Look for LimitBlankPasswordUse name on the right pane, double click on it and set the value data to 0.
With Windows Server 2012 R2 and Windows 8.1, Microsoft called the Protected Users group. You can use it to limit the availability of outdated authentication protocols, weak encryption algorithms and delegation to sensitive user accounts.Interesting stuff, but I feel there’s some things you should know about this featureWhen you want to go and put the Protected Users group to good use in your environment, I feel you should be aware of these things:1. Take care of client-side requirementsNo matter how you look at this wonderful feature, you won’t escape the fact that to get the protection, your users need to log on to Windows 8.1 (or up) devices or Windows Server 2012 R2 (or up) hosts.
Even if you’ve upgraded all the Domain Controllers to Windows Server 2012 R2 and upgraded the Domain Functional Level to Windows Server 2012 R2, when your colleagues use Windows 7 as their client Operating System (OS) or Windows Server 2008 R2 as their Terminal Servers, they won’t benefit from the protections offered by membership of the Protected Users group.2. Take care of server-side requirements (sorta)According to the official documentation, the Protected Users group requires the Windows Server 2012 R2 Domain Functional Level (DFL). However, the Protected Users group can be applied to Active Directory domains that are set to a Domain Functional Level (DFL) for an operating system earlier than Windows Server 2012 R2.This allows the added security that is achieved by using the Protected Users group to be applied throughout the domain. To do this, promote the Domain Controller holding the Primary Domain Controller emulator (PDCe) Flexible Single Master Operations (FSMO) role to Windows Server 2012 R2, and then allow the upgraded PDC to replicate the Protected Users group to other Domain Controllers. When the replication completes, the PDC can be set back to any available Domain Functional Level (if desired), and the Domain Controller-based protections are automatically applied. Protect users onlyAccounts for services and computers should not be members of the Protected Users group. This group provides no local protection to these types of accounts because the password or certificate is always available on the host.
Also, since Managed Service Accounts (MSAs) and group Managed Service Accounts (gMSAs) use Kerberos Constrained Delegation (KCD), do not add these accounts to the Protected Users group, since their functionality will break. Make Protected Users change their passwords on Windows Server 2008 Domain Controllers (or up) firstMembers of the Protected Users group must be able to authenticate by using Kerberos with Advanced Encryption Standards (AES).
Runas Account Restrictions Are Preventing This User From Signing In
This method requires AES keys for the account object in Active Directory. The built-in Administrator does not have an AES key unless the password was changed on an Active Directory Domain Controller that runs Windows Server 2008 or later. Additionally, any account object, which has a password that was changed at an Active Directory Domain Controller that runs an earlier version of Windows Server, is locked out. You may lock yourself outThe authentication restrictions have no workarounds, which means that members of highly privileged groups such as the Enterprise Admins group or the Domain Admins group are subject to the same restrictions as other members of the Protected Users group. If all members of such groups are added to the Protected Users group, it is possible for all of those accounts to be locked out.
My advice is to never add all highly privileged accounts to the Protected Users group, until you have thoroughly tested the potential impact. ©.All rights reserved.The information on this website is provided for informational purposes only and the authors make no warranties, either express or implied. Information in these documents, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user.Active Directory, Microsoft, MS-DOS, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.Metro Theme created. Proudly powered.