Local user management password policy inconsistent behaviour
Hi all, Maybe some of you can enlighten me regarding the windows 10 + 11 local user password policy. The part that I want to question is "not contain parts of the user's full name". Then, let's say I want to create a new user with the following detail: Fullname: Max Mustermann Username: TESTUSER1 Pass: MaxPassword12345678 When I try to create that user via cmd or powershell, either using "net" or "New-LocalUser", it will not succeed and it will show the error "the password does not meet complexity....", which is expected. However, if I try to create the same user with the same credential via lusrmgr, it will be created without any error. So, why there is a different behaviour between lusrmgr and CLI? Then, if we have the existing user, and try to change the password of that user via lusrmgr, and the password contains the part of the user's full name, then the error will be thrown as expected. So, why is it only affect the lusrmgr and only when we create a new user? Is this a bug? Thanks!
Authorise standard user for certain app
Hi guys, I want allow the standard users to run games on their account (specifically garena and league of legends) however as I click play, garena then opens an app call gxxhelper (garena platform service) and this requires admin password. I've tried the create shortcut with saved credentials but this wouldn't work as garena opens another app. It's pretty stupid if I just give the other users admin rights, I could be locked out of my own computer. I have also tried task scheduler and the admin compatibility tool but they didn't work either. I have also tried to make the program to always run as admin (under properties) but this option makes the app unusable, the game probably not allow modification of client's files. Is there another option to make this works? Cheers,Can't add local user "Guest" account to login screen
I must be losing my mind. I have Azure AD joined Windows 10 machines (corporate ownership model), but I would like to add a persistent local guest user login to the login screen, and I can't seem to do it. I can add the user, but it doesn't appear as a choice on the login screen. Only "Other user..." appears (along with whoever last logged on). First I tried what I have done historically - via "lusrmgr.msc" and enabled the built-in Guest account. No password, can't change password, etc...AFAIK doing this would result in a new "Guest" login appearing on the login screen, but alas it does not. FWIW it doesn't work for the built-in administrator account either. I also tried another approach - using Windows 10 "Settings-->Accounts-->Other Users-->Add someone else to this PC" and added a local standard user without a MS Account or password, and while that adds the account (I see the profile created under the user folder, and the user has been added to the local users' group according to "lusrmgr.msc", and I then added this new user to the "guests" group and removed from "users", but it doesn't actually appear on the login screen like I thought it used to. I then tried using the Windows Config Designer app to create a "Shared Computer" provisioning package - and while this sort of worked (a new Guest account was added to the login screen) it seemed to wipe out other critical settings on the computer, like, for example, Windows Hello sign-in settings got wiped out for the computer owner. What am I missing? At first I thought it was perhaps a Windows version issue (Insider vs. release) or Intune policy conflict, but I have tried this now on other tenants with and without Intune that are cloud-only Azure AD joined devices and I can't get it to work anywhere. This used to be so simple. Anyone else able to do this? Thanks, Bob
