There are two active user accounts on the Windows 7 Professional server, Owner, and Guest.
Owneris an Administrator with a password.Guestis the default Guest account with no password, but has been added toRemote Desktop Users.
When attempting to connect to the server via a Windows 7 Professional client, Guest accepts RD connections fine, however, Owner throws an error "Unable to connect to Local Security Authority."
I created a new Administrator account, named Remote, with the same password as Owner. Remote Desktop worked perfectly. I then deleted Owner, and renamed Remote to Owner.
Now, Remote Desktop gives the same error ("Unable to connect to Local Security Authority") when attempting to log into the new Owner. However, attempting to log into Remote (even though it was renamed to Owner), works.
Completely at a loss here, what is going on? Why won't Owner work, and why does Remote Desktop still use the old name on the renamed account?
+ R). Then, uncheck the box for "users must enter a username and password to use this computer." When you click OK, it will prompt you for the username and password to login to by default. Now when you start up your computer, it will automatically login to that account, but when you access the system remotely it will always prompt for your password.
Best Answer
Do not rename the user account. Create the user "Owner" directly.
Renaming a user causes problems. If you look in the folder c:/users/ you will still see the old user name instead of the new username.
Renaming a User Account Does Not Automatically Change the Profile Path
There is a fix in the link above, but it's always better to create than rename user accounts...