Here's some background on why I'm asking this question:
I'm renaming the administrator account and changing it's password on over 4000 pc's via a "package" I'm making and will "push" out to all the PC's. That's not a problem, I got that right here and it works.
I'm torn though because when I do that their profiles under c:\documents and settings will still be listed under the old ID name.
So I played with renaming the folder but the next time the the local admin logs into the account it creates a userID.Computername folder instead of using the clean foldername I want it to.
One way around it as mentioned here (if you want the scoop on how I'm doing this) is to just delete the local admin profiles after I rename the account and it's password.
Finally my question:
What do you think about doing that in an enterprise environment?
As far as data loss goes I'm nervous just typing this thread because it might end up causing a HUGE problem onlike 5 out of 4000 pc's... I hate deleting anything...
I might just suck it up and go the sloppy route... Any of you IT folks have an idea?
I'm renaming the administrator account and changing it's password on over 4000 pc's via a "package" I'm making and will "push" out to all the PC's. That's not a problem, I got that right here and it works.
I'm torn though because when I do that their profiles under c:\documents and settings will still be listed under the old ID name.
So I played with renaming the folder but the next time the the local admin logs into the account it creates a userID.Computername folder instead of using the clean foldername I want it to.
One way around it as mentioned here (if you want the scoop on how I'm doing this) is to just delete the local admin profiles after I rename the account and it's password.
Finally my question:
What do you think about doing that in an enterprise environment?
As far as data loss goes I'm nervous just typing this thread because it might end up causing a HUGE problem onlike 5 out of 4000 pc's... I hate deleting anything...
I might just suck it up and go the sloppy route... Any of you IT folks have an idea?