For as long as I remember, I have populated the drive letter and network path for the Home Folder attribute in AD. We also perform this mapping in the logon script, which is at least partially redundant. We have been having a problem with this drive letter mapping to the top level of the share, instead of all the way to the user's folder. In researching the issue, I have found reports of this being a bug (e.g. http://www.techsupportforum.com/microsoft-support/windows-nt-2000-2003-server/145050-home-folder-active-directory.html).
Since we are already setup to do this in the logon script, I would like to remove the attribute from AD. To make sure that there are no unintended consequences, I tried to research whether this attribute might control/do something other than just the drive letter. I found something indicating it affected an environment variable, but it didn't sound like anything that would cause a problem. Unfortunately, my google-fu is weak and I haven't been able to find enough info to discount the possibility that it will create a (new/different) problem. Can anyone confirm if this attribute does anything other than a drive letter mapping? Any other impact from changing the selection to "local path" and leaving that blank? Bill Mayo Pitt County MIS ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
