Polski Posted May 30, 2008 Posted May 30, 2008 Windows 2003 Domain with XP-SP3 clients. Before we installed SP3 the "My Documents" folder pointed to seperate network shares for each user. \\servername\homes$\%username% After SP3 was deployed we found they all pointed to one users folder (which they had no access to!) Rolling back SP3 has cured the problem. Thought it worth giving you a "Heads up" on it.
apeo Posted May 30, 2008 Posted May 30, 2008 Thanks for the heads up... odd error tho, so it just picked a random users' folder? You could redirect 'My Documents' to mappeddrive:\My Documents eg "H:\My Documents".
Michael Posted May 30, 2008 Posted May 30, 2008 I've deloyed SP3 to a few systems and haven't experienced the problem you report. In saying that, I use \\SERVERNAME\User$ to map My Documents to each user. Does this make any difference?
JamesC Posted May 30, 2008 Posted May 30, 2008 I've experienced this same issue. I map my home dirs like so: \\servername\homes$\%username% but I have also seen instances, especially on RM networks where each user has their own mapped drive - instead of being mapped to a folder within a mapped drive (as described by \\SERVERNAME\User$). I have found that for some reason users seem to have their home dir mapped to: \\servername\homes$ instead of \\servername\homes$\%username% so they can see every other students homedir! NTFS permissions obviously stop them from browsing another students homedir but it is a real pain. Luckily I haven't rolled out SP3 and happened to notice this whilst testing. Hope this saves a few people problems!!
Michael Posted May 30, 2008 Posted May 30, 2008 It's interesting. I wonder if the %username% variable is causing the problem? Within AD I setup home drives as \\SERVERNAME\USERNAME$ (where USERNAME$ is an actual logon name, not a variable)! I then use Autoshare to automatically share all the home folders. In my initial testing XP SP3 did not break my configuration.
EduTech Posted May 30, 2008 Posted May 30, 2008 It's interesting. I wonder if the %username% variable is causing the problem? Within AD I setup home drives as \\SERVERNAME\USERNAME$ (where USERNAME$ is an actual logon name, not a variable)! I then use Autoshare to automatically share all the home folders. In my initial testing XP SP3 did not break my configuration. that could be right, as i dont use the variable either and i have not had this issue that is reported. james
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now