• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 493
  • Last Modified:

After renaming an ActiveDirectory user, the old username appears in eventlog

Hi,
In a Microsoft Windows 2000 pur Domain, I had to rename all Active Directory user accounts from Userxx to his initials. For example User32 was renamed to ABC. I changed in "Active Directory Users and Computers" everything from user32 to ABC.
Now for example, when User ABC reboots his PC in his Windows Event-log "User32" did that reboot and not "ABC".

Is there somewhere else where I have to change the username?

Thanks for any help
Joerg
User32.JPG
0
rolandmueller
Asked:
rolandmueller
  • 5
  • 3
1 Solution
 
PakaCommented:
On each user object, did you change the "User logon name pre-Windows 2000)" name too?
0
 
rolandmuellerAuthor Commented:
yes, I changed the username on each object I could find, when I open tha user in AD
0
 
PakaCommented:
Did you change it in these two places?
namechange.png
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
rolandmuellerAuthor Commented:
Yep, I did that
0
 
PakaCommented:
Is this user logging in locally or are they logging into the domain.?  If they are logging in locally, then they will be using a local account and you'll need to change the user attributes on the local machine too.  If they're logging into the domain, the event should log with that info.
0
 
rolandmuellerAuthor Commented:
The user is logging into the domain, they don't have local accounts.
0
 
PakaCommented:
USER32 is the process that actually performs the shutdown on behalf of the user.
0
 
ChiefITCommented:
sounds like saved passwords for maybe a mapped network drive or something Paka.
0
 
PakaCommented:
I tried it on a vanilla test environment and USER32 will show up as the source of the shutdown event.  I suspect that MSGINA is calling USER32 to do the actual work or logging and that's why USER32 is showing up in the event log.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now