Allow logon locally on server group policy

It depends,

Are you cahnging it from the Local Security Policy console (secpol.msc) or from the AD Group Policy management console (gpmc.msc) ?

if it is the first one, Local, then it only applicalbe for the Local server itself, which is impacting how can they logon to the OS via console.

Please note that this is different with the RDP permission.

usually the "Allow Logon Locally" is for granting AD service account to run the service or tasks in the server.

usually the "Allow Logon Locally" is for granting AD service account to run the service or tasks in the server.

I really hope people do not do this...

Permissions for a service account on a server are:

Deny logon locally (prevent the service account logging on locally)
AND
Allow logon as a service (if running as a service)
OR
Allow logon as a batch job (if running as a scheduled task)

does this policy also affect  who can logon locally to computers that are joined to the domain or just who can logon locally to the server?

Allow logon locally will default to users and administrators (that is the local users and administrators groups on the server) if you have never defined this policy...if I recall correctly. How it applies depends on where you have linked your policies (which OU's) and which OU the various computers are in.

I am going into through gpmc.msc.  For some reason I was thinking that this would  also affect the policy on user computers connected to the domain.   I am having trouble with having two domain users logging into the same computer.  One can login but the other one can't.  I get an error .  

Sign in method you are using is not allowed.  Contact  Network Administrator.

Check that they have the local on locally user right if they are logging on locally. If they're logging on remotely, check that they have the Allow log on through terminal services right. By default on a member server this would be members of: Administrators and Remote Desktop Users (these are the server local groups).

It is just a workstation with users accessing network folders.  So you are saying I need to login with the account that is allowing me in and check the local policy?

Yes, check the rights assignments. Check the local group memberships. Make sure the user is not denied logon locally.

Ok, here is another question.  What if for some reason I am not allowed to access the policy on the computer?   I had tried accessing it before and it seem to give me an error.

I'm not sure. In theory, if GPO's are applying correctly to the device then you could just generate RSOP from a DC. Or check the GPO's applying to the machine's OU. It could be there's a problem with the machine and the OS is stuffed. You would need to check the event logs.

do you use gpresult /r?

You can but I tend to use the one built into GPMC, particularly if I don't trust what I might get back from the endpoint.

If you open gpmc.msc, down the bottom on the left pane you should see Group Policy Modelling and Group Policy Results. Group Policy Modelling will create a model of what policies and their settings should apply to a device. You can do things like change group membership, etc. to test effects. Group Policy Results is just RSOP via GPMC and will pull the results of what is applying from the remote machine.

OK  Will try it out.

Ok was able to view the local policy on the users computer.  However i could not change allow login locally .  It is grayed out. What can i do to allow changes. Other policies allow me to change them but not allow login locally

Found the group policy on the server.    Apparently it is the setting on the server that has a group policy  allow locally -  It has specific users listed - one is the Administrator and other  ad users that don't have admin rights.  This is causing my local workstations on the network who are joined to the l domain to only be able to logon  to that workstation if  they are on the list set by the group policy.  The only other way I can have other users login to that workstation is if i  add a ad user to the admin group for the local computer.  

Any idea why someone would said this up like this?  I  normally let any user login to any computer with their ad user account.

I don't know why anyone would add specific users to a policy like that. It is unusual. Yes, typically all domain users would be able to log on to all workstations. If you were to restrict a particular workstation then you would do it with a group rather than individual users. The only reason to restrict a device is to really lock it down and if you wanted to do that you would need to go beyond just changing who can log on locally. You need it physically secured, secured on the network, the works.

Thanks for everyone's input.

Thank you

No problem.
Glad to help you as well Mom.