omnbit
asked on
Home Folder Problems
I have a weird issue that's randomly happening to some users.
When I set up the user accounts I set up the the profile and the home folder to map to drive U: and the locations is \\servername\users\theuser
It's been working great but sometimes for some weird reason the user will get a map to the U: at \\servername\users so they can view the whole folder....since these are the private drives I've blocked everyone but domain admins from browsing this directory so they get the access denied error.
Any reason why it's doing this.
Should I start setting the home to \\servername\users\%USERNA
or kill using the home folder and just use my login script to map?
THX
When I set up the user accounts I set up the the profile and the home folder to map to drive U: and the locations is \\servername\users\theuser
It's been working great but sometimes for some weird reason the user will get a map to the U: at \\servername\users so they can view the whole folder....since these are the private drives I've blocked everyone but domain admins from browsing this directory so they get the access denied error.
Any reason why it's doing this.
Should I start setting the home to \\servername\users\%USERNA
or kill using the home folder and just use my login script to map?
THX
ASKER
I've just been doing this.
Profile Tab set to U: drive
Path set to \\servername\users\TheUser
So if my user is Tom
Path set to \\servername\users\Tom
Profile Tab set to U: drive
Path set to \\servername\users\TheUser
So if my user is Tom
Path set to \\servername\users\Tom
Hi omnbit,
This has been an issue for a number of people and the source of many newsgroup disucssions. A solution discussed on MCSE.ms forums looks to be solving the issue for most people - in fact, everyone that has had the issue you described and implemented the GPO setting has reported back that it resloved their problem. Hopefully, you will have the same luck.
Enable "Always wait for the network at computer startup and logon" in your GPO and update DCs and clients. This should make the issue dissappear. FYI - This settings disables Windows XP fast logon optimization...
Cheers!
This has been an issue for a number of people and the source of many newsgroup disucssions. A solution discussed on MCSE.ms forums looks to be solving the issue for most people - in fact, everyone that has had the issue you described and implemented the GPO setting has reported back that it resloved their problem. Hopefully, you will have the same luck.
Enable "Always wait for the network at computer startup and logon" in your GPO and update DCs and clients. This should make the issue dissappear. FYI - This settings disables Windows XP fast logon optimization...
Cheers!
ASKER
Thanks....I'll give that a try.
Yeah, what jss1199 is saying is true...I've seen similar discussions on EE about that setting, and another EE expert linked to this article:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/7d2fc477-5a3a-42b9-94e3-0f0848df2ab9.mspx
That seems to state that it shouldn't even be enabled based on the note at the bottom, but I'm betting that jss1199 is hooking you up right.
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/7d2fc477-5a3a-42b9-94e3-0f0848df2ab9.mspx
That seems to state that it shouldn't even be enabled based on the note at the bottom, but I'm betting that jss1199 is hooking you up right.
Microsoft *says* that Fast Logon optimization is automatically turned off when a user logging in has a home folder defined (as this would obviously cause problems mapping), but the success of this workaround in addressing such issues begs to differ....Who woulda figured? Is it possbile that Microsoft might be wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm giving it a few days to see if it did....It's something that didn't happen all the time so I want to make sure.
Is that how it is?