Cannot move the My Documents Folder

I'm using Windows XP in a domain (Windows 2003 server)
and have found that I cannot move the My Documents folder
on the Windows XP workstations. The "restore default,
move, and find target" buttons do not show up on the
user's My Documents property tab. The only thing that
shows up is the target field, which does not allow me to
type in the new target.

Right now the My Documents folder is pointed to the
user's profile directory on the server
\\server\users\username\My Documents

I want to move the My Documents folder to another network
drive so that the documents in My Documents don't get
copied to the workstations each time the user logs in (as
part of their roaming profile). Any help would be
appreciated.

Thanks,
Sal.

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in
the following Registry path:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Explorer]

Delete the DisablePersonalDirChange value. And access the My
Documents propertysheet from Start Menu.

That key does control permission to change My Documents, but since s/he
is in a domain, the group policy will reset that key each time he logs
on. The domain administrator is in control.

--
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security

True. Thanks for the tip, Kent.

--=20
Ramesh - Microsoft MVP
Windows XP Shell
http://www.mvps.org/sramesh2k

What You Should Know About the Sasser Worm and It Variants:=20
http://www.microsoft.com/security/incident/sasser.asp


"Kent W. England [MVP]" wrote in message =
...
Ramesh [MVP] wrote:

This is due to the presence of "DisablePersonalDirChange" value in=20
the following Registry path:=20
=
[HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Policies\Exp=
lorer]
=20
Delete the DisablePersonalDirChange value. And access the My=20
Documents propertysheet from Start Menu.
=20
That key does control permission to change My Documents, but since s/he=20
is in a domain, the group policy will reset that key each time he logs=20
on. The domain administrator is in control.

--=20
Kent W. England, Microsoft MVP for Windows Security