T
TSAM
Guest
Hello,
I have Windows 2003 domain with mixed clients like Windows 2000, Windows XP
and Windows Vista.
We use roaming profiles and this network share is configured on a Windows
2003 Server. For example, when we create a user account in the profiles tab
we specify [ \\FileServer\profiles\user] as the path. It works as expected
with Windows 2000 and Windows XP clients. With Vista, it appears to be
working but we have seen cases where Vista clients cannot load profiles from
this network share.
Please find my queries:
1. It appears Vista creates a profile automatically with .V2 extention. Is
it recommended or required to manually create this folder under the network
share where profiles are stored?
2. What permissions should I see for this user from the network share? When
I browse the user profile folder from the network share Server, I cannot see
any permissions and to me this strange. Is this the default behaviour for
automatically created Vista profile folders?
I have Windows 2003 domain with mixed clients like Windows 2000, Windows XP
and Windows Vista.
We use roaming profiles and this network share is configured on a Windows
2003 Server. For example, when we create a user account in the profiles tab
we specify [ \\FileServer\profiles\user] as the path. It works as expected
with Windows 2000 and Windows XP clients. With Vista, it appears to be
working but we have seen cases where Vista clients cannot load profiles from
this network share.
Please find my queries:
1. It appears Vista creates a profile automatically with .V2 extention. Is
it recommended or required to manually create this folder under the network
share where profiles are stored?
2. What permissions should I see for this user from the network share? When
I browse the user profile folder from the network share Server, I cannot see
any permissions and to me this strange. Is this the default behaviour for
automatically created Vista profile folders?