Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

WinXP My Documents Folder Problem

Original Message
Name: Mathew Fisher
Date: May 13, 2004 at 08:13:29 Pacific
Subject: WinXP My Documents Folder Problem
OS: Windows XP SP1
CPU/Ram: N/A
Comment:
I have Windows NT Server SP4 with WindowsXP machines connecting.

The problem I have is that when a user logs on to the Windows NT Server, the users "My Documents" folder points to a mapped network drive. When I change the target of "My Documents" folder and log out and back in it reverts back to the mapped drive. This happens with everyones login account. I have also created a .reg file to post settings into each persons registry on login (within the logon script) but to no success ....

I have nothing in the logon script and can not see anything in the user profiles or groups to change this option.

ALL I want is for when any user logs in, the My Documents folder within Explorer opens up the Local My Documents folder for that user, not a mapped network drive....

Many Thanks.



Report Offensive Message For Removal


Response Number 1
Name: normajean
Date: May 13, 2004 at 10:46:41 Pacific
Subject: WinXP My Documents Folder Problem
Reply: (edit)
It sounds like roaming profiles are being used. When you go to the XP machine, under control panel, system, advanced, user profiles does it say they are local profiles or roaming profiles? If it says roaming, delete the profile off the server first then delete the local profile for the user. Have them log on again and it will rebuild their profile, hopefully as a local profile. (but of course, save their documents someplace else before you delete all copies of their profile)

Report Offensive Follow Up For Removal

Response Number 2
Name: Jennifer SUMN
Date: May 13, 2004 at 10:57:08 Pacific
Subject: WinXP My Documents Folder Problem
Reply: (edit)
Check the following reg key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Personal

Where is it pointing?


Report Offensive Follow Up For Removal

Response Number 3
Name: Mathew Fisher
Date: May 14, 2004 at 01:37:48 Pacific
Subject: WinXP My Documents Folder Problem
Reply: (edit)
Thanks for replies,

Jennifer : I've already tried changing the registry in that way but it changes everytime I log on , suggesting that it's picking up some profile.

Which leads me to ...

Zachary : The PC's use local profiles, roaming profiles have been disabled.


It appears that windows is looking at this mapped drive (which contains at least 10,000 documents (word & excel etc..), maybe it's something to do with windows finding a normal.dot in there ??

Many Thanks



Report Offensive Follow Up For Removal

Response Number 4
Name: Jennifer SUMN
Date: May 14, 2004 at 09:08:10 Pacific
Subject: WinXP My Documents Folder Problem
Reply: (edit)
Have you checked your Default Profile? Or, have you tried changing permissions on that particular value so it can't be changed?

Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: WinXP My Documents Folder Problem

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




CMOS/GPNV checksum bad

3 Strikes

how to find complete path of a file

Replication of DC with ADC

Deleting a block of text with sed


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC