G
Guest
I have a Windows 2000 AD server. This server is running out of room and we
would like to take one of our Windows 2003 file servers and use this as the
repository for any new home folders that are created on the Windows 2000 AD
server. I have the script correct where the folder will be created on the
remote server and the proper permissions are added for the user that "owns"
that home folder. Under the profile tab, the "connect" radio button is
clicked the drive letter is "H" and the To: is \\remoteserver\home
folder\%username%. What I seem to be having an issue with is this.
The drive letter "H" will not map for the user when he/she loggs in.
Everything works great except the "H" drive being mapped. Is there a way to
get this to work? Will upgrading the 2003 file server to an AD server allow
us to get the mapping to work or is this a limitation by design?
Thank you in advance,
Rick
would like to take one of our Windows 2003 file servers and use this as the
repository for any new home folders that are created on the Windows 2000 AD
server. I have the script correct where the folder will be created on the
remote server and the proper permissions are added for the user that "owns"
that home folder. Under the profile tab, the "connect" radio button is
clicked the drive letter is "H" and the To: is \\remoteserver\home
folder\%username%. What I seem to be having an issue with is this.
The drive letter "H" will not map for the user when he/she loggs in.
Everything works great except the "H" drive being mapped. Is there a way to
get this to work? Will upgrading the 2003 file server to an AD server allow
us to get the mapping to work or is this a limitation by design?
Thank you in advance,
Rick