I had done this in the past as well. From my perspective, this helps with security as far as network file servers and shares. But the local profile actually uses the SID to determine the profile path. While I cant say that I have tested any VB scripts, my solution was to just create a new Local profile after renaming the account. It was much cleaner that way.
If you have a particular user account that is part of multiple security groups it does help to be able to just rename the account, but from most of my experience it is far easier to just create a new account and add it to the appropriate security groups. Dave Doeppel MCSE 2003 + Messaging -----Original Message----- From: Murda Mcloud [mailto:[EMAIL PROTECTED] Sent: Monday, July 31, 2006 8:59 PM To: [email protected] Subject: username change best practices... Hi all, I seem to remember being given the advice on an MS course for giving a new user same privileges/access etc as the old user they were replacing by just renaming the current account in AD User+Comps. How does this affect things like profile paths on a workstation? It seems that when I do this for instance, profile path stays as 'c:\docs and settings\usernameold' etc but the new user, ie usernamenew, sees that 'old' profile when logging into the machine. What are the security implications of this if any? We don't use roaming profiles as no-one roams. And how does this affect security issues for VB scripts that run using parameters like SPECIAL FOLDERS (eg My Documents/desktop) etc? Is there some accepted practice for renaming the local profile path-vis a vis security standpoint? ------------------------------------------------------------------------ --- ------------------------------------------------------------------------ --- --------------------------------------------------------------------------- ---------------------------------------------------------------------------
