Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

There are two active user accounts on the Windows 7 Professional server, Owner, and Guest.

  • Owner is an Administrator with a password.
  • Guest is the default Guest account with no password, but has been added to Remote 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?

share|improve this question
add comment

1 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.

When you rename a user account in on a computer that is running Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2, the user profile path is not changed automatically. It may cause some confusion when the %SystemDrive%\users folder is viewed

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...

share|improve this answer
    
The profile path should have no effect on the userNAME, however, no? Profile paths may be entirely arbitrary, or even located on a network drive (not the local machine). Which is why software should never assume profile paths, but use the proper API calls. I do not think the profile path is the issue here, as I have renamed accounts in the past and used them just fine. –  Unsigned Sep 6 '12 at 0:03
    
I had the same rdp problem you had, and it was solved by deleting the old renamed account and creating a new clean account. I can not be sure the cause, but maybe someone here can add to the discussion. –  Logman Sep 6 '12 at 0:13
    
try the reg fix from the link, probably only way to rule it out –  Logman Sep 6 '12 at 2:44
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.