Issues with data locations.

I have built a Vista (Business edition) machine as a member of a windows
2003/2003 domain.

This machine is located in an OU which does not have redirect documents set.
On the Vista machine as expected Documents, Pictures and Music pointed to
the local hard drive in subfolders under the location c:\users\administrator

I then changed the paths to Documents, Pictures and Music as follows:

Pictures to d:\data\pictures
Music to d:\data\music
Documents to \\servername\documents\lees work

The serer is structured as follows

d: -
Documents(Shared as Documents)
-User1 Documents
-User2 Documents
-User3 Documents
etc.....

Profiles
- User1 Profile
etc.....

At this point I noticed that "Documents" on the start menu had changed to
the name of the new location for documents on the network called “Lees Work"
I then renamed "Lees Work" on the start menu to "Documents" and I am in now
the following situation.

Looking on the server Vista seems to have taken over!!!!

Rather than taking action only over the "Lees work" sub folder for some
reason Vista has managed to pick up the fact that there is a higher level
folder called "Documents" on the server. Vista has preceded to convert the
top level folder on the server called "Document" to a Windows Vista folder
and then replicated this throughout the tree. e.g. it has enabled sync on
all of folder in the tree to sync to my PC!!!!!!!

What is hell is going on here?

I am not in the mood for performing a restore on a data tree which contains
300+ network users data because I pointed my vista PCs "Documents" to my
networks "My Work" folder located in a server top level folder called
"Documents".

"SuperPlay" <SuperPlay@discussions.microsoft.com> wrote in message
news3DB57AC-C93C-44E2-977E-1B31671638EA@microsoft.com...
>I have built a Vista (Business edition) machine as a member of a windows
> 2003/2003 domain.
>
> This machine is located in an OU which does not have redirect documents
> set.
> On the Vista machine as expected Documents, Pictures and Music pointed to
> the local hard drive in subfolders under the location
> c:\users\administrator
>
> I then changed the paths to Documents, Pictures and Music as follows:
>
> Pictures to d:\data\pictures
> Music to d:\data\music
> Documents to \\servername\documents\lees work
>
> The serer is structured as follows
>
> d: -
> Documents(Shared as Documents)
> -User1 Documents
> -User2 Documents
> -User3 Documents
> etc.....
>
> Profiles
> - User1 Profile
> etc.....
>
> At this point I noticed that "Documents" on the start menu had changed to
> the name of the new location for documents on the network called “Lees
> Work"
> I then renamed "Lees Work" on the start menu to "Documents" and I am in
> now
> the following situation.
>
> Looking on the server Vista seems to have taken over!!!!
>
> Rather than taking action only over the "Lees work" sub folder for some
> reason Vista has managed to pick up the fact that there is a higher level
> folder called "Documents" on the server. Vista has preceded to convert
> the
> top level folder on the server called "Document" to a Windows Vista folder
> and then replicated this throughout the tree. e.g. it has enabled sync on
> all of folder in the tree to sync to my PC!!!!!!!
>
> What is hell is going on here?
>
> I am not in the mood for performing a restore on a data tree which
> contains
> 300+ network users data because I pointed my vista PCs "Documents" to my
> networks "My Work" folder located in a server top level folder called
> "Documents".
>

If you open the Properties dialog for 'Documents ' on the Start Menu and
select the 'Location' tab, does it point to 'Lees Work' or the higher level
Documents? If it's not correct, modify the path.

On a standalone machine, renaming 'Documents' on the Start Menu doesn't
change the name of the actual folder, but modifies the hidden, system file
within the folder named 'desktop.ini'. Here are the contents before a
rename:


[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21770
IconResource=%SystemRoot%\system32\imageres.dll,-112
IconFile=%SystemRoot%\system32\shell32.dll
IconIndex=-235

Here are the contents after I renamed it to 'DocumentsRename':

[.ShellClassInfo]
LocalizedResourceName=DocumentsRename
IconResource=%SystemRoot%\system32\imageres.dll,-112
IconFile=%SystemRoot%\system32\shell32.dll
IconIndex=-235

When you say Vista converted the higher-level Documents to a Vista folder,
did you mean a green icon? that's controlled by desktop.ini as well. Check
the folders on the server for desktop.ini files and modify/delete as
necessary.


--
Good Luck,

Keith
Microsoft MVP [Windows XP Shell/User]