Troubleshooting Local Users and Groups

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Troubleshooting

What problem are you having?

  • Received the "The local policy of this system does not permit you to logon interactively" error message, or unable to log on locally.

  • Runas command failed.

  • Cannot log on to a network computer running Windows 95 or Windows 98.

  • Cannot access the Computer Management extension snap-ins on a remote computer.

Received the "The local policy of this system does not permit you to logon interactively" error message, or unable to log on locally.

Cause:  The ability to log on locally to a stand-alone server or member server running Windows Server 2003 is controlled by local security policy.

Solution:  Add the user account to the Users local group or use the local security policy to assign the particular user or group the right to Allow log on locally.

See also:  Allow log on locally;Assign user rights for your local computer; Local Security Policy overview

Runas command failed.

Cause:  The Secondary Logon service is not running.

Solution:  Start the Secondary Logon service.

See also:  Start, stop, pause, resume, or restart a service

Cause:  The Secondary Logon service is running; however, you do not have permissions on the shared resource that is running the Secondary Logon service.

Solution:  Verify that your local user account in Computer Management has the permissions needed to access the shared resource on which the Secondary Logon service is installed. To view permissions in Computer Management, in Control Panel, double-click Administrative Tools, and then double-click Computer Management.

See also:  Runas

Cause:  The Secondary Logon service is running; however, you cannot start or install a program from a shared resource using the runas command.

Solution:  Using the runas command, map a network drive to the shared resource using administrative credentials from your local computer, and then start the program again. To do this, open a command prompt by typing the following command in the Run dialog box:

runas /user:administrator cmd

When prompted, type the administrative password and when the command prompt appears, type:

**net use z: \\Server\Share/user:DomainName\**UserName *

This will connect you to the shared resource while still under the security context of the local administrator account.

See also:  Runas

Cannot log on to a network computer running Windows 95 or Windows 98.

Cause:  Your password is longer than 14 characters.

Solution:  Create a new user account or change your password to the 14 character maximum for Windows 95 and Windows 98.

See also:  Reset the password for a local user account

Cannot access the Computer Management extension snap-ins on a remote computer.

Cause:  The Remote Registry service is not running on the remote computer.

Solution:  Ensure that the Remote Registry service is started on the remote computer. You need appropriate permissions on the remote computer to start the service.

See also:  Start, stop, pause, resume, or restart a service

Note

  • You might also receive this error message if the remote computer is running Windows 95. Computer Management does not support remote access to computers that are running Windows 95.