Hexnode’s password policy fails due to conflicts with existing Microsoft accountSolved

Thank you all for your valuable input. 

To begin with, you need to identify the restricted user from the local accounts. This can be done by navigating to the Manage tab > Device > select device > Local accounts. Once there, click on each of the local accounts and check which one has the setting “User can change password” set to No. After identifying the restricted user, the next step is to enable them to change their password. 

The first method to remove this restriction is by using a script. Go to the Manage tab > Device > Action > Execute custom script. From there, open the Hexnode repository and generate a script using Hexnode genie. Paste the following command into the script editor: 

powershell 

Set-LocalUser -Name “User_Account_Name” -UserMayChangePassword $true 
 

Replace “User_Account_Name” with the actual name of the restricted account. Save the script with a .ps1 extension and run it. Once executed, check again to confirm that the “User can change password” option is now set to Yes. 

The second method is to perform the change manually from the device. You can open PowerShell as an administrator and run the same command directly. Alternatively, press Win+R, type lusrmgr.msc, and press Enter. Double-click on Users, select the restricted account, right-click and choose Properties. In the properties window, uncheck the option “User cannot change password” and click OK. After this, perform a Scan Local Accounts action from the Hexnode portal and resave the policy. 

Finally, ensure that the password policy is updated. Enable Allow Simple value, set the minimum length to less than or equal to 8, and configure Password Complexity so that it does not require uppercase characters. You can choose digits only, or a combination of digits and lowercase letters. Beyond this, you may apply additional complexity rules as needed. This ensures that the user can change their password while still maintaining the required security standards.

Regards,
Mary Romero