J
JoS
I have noticed an anomaly in the functionality of the Adminpak for XP/2003
and the Adminpak for win2k - specifically the AD U&C snap-in.
When creating a user using the Win2k AD U&C snap-in and defining their home
dir location as \\FQDN\share\%username% the correct permissions will be set
on that home dir (ie. username and local (to the server hosting the share)
admins Full Control). This is correct by design. But using the win2k3 AD
U&C snap-in and defining the home dir location using the same syntax results
with incorrect permissions on the newly created home directory (in my
situation it appears as if it is inheriting the perms from parent dir and
then adding the specific user with Full Control). The fileserver that hosts
the home dirs is a Win2k Server. Has anyone else seen this?
I can't imagine this is by design.
Google, groups.google, and the MSKB have nothing on this.
TIA,
JoS
and the Adminpak for win2k - specifically the AD U&C snap-in.
When creating a user using the Win2k AD U&C snap-in and defining their home
dir location as \\FQDN\share\%username% the correct permissions will be set
on that home dir (ie. username and local (to the server hosting the share)
admins Full Control). This is correct by design. But using the win2k3 AD
U&C snap-in and defining the home dir location using the same syntax results
with incorrect permissions on the newly created home directory (in my
situation it appears as if it is inheriting the perms from parent dir and
then adding the specific user with Full Control). The fileserver that hosts
the home dirs is a Win2k Server. Has anyone else seen this?
I can't imagine this is by design.
Google, groups.google, and the MSKB have nothing on this.
TIA,
JoS