Mapping of home folders for users

[Guest acoustix]

I've been having an issue with home folders being misdirected when a user

logs into their desktop. I'm not sure if this is a server config issue or a

desktop OS issue.

 

All clients are running WinXP Pro SP2. All domain controllers are Win 2003

SP1. Home folders are cofigured on users profiles in AD. I have selected

"connect H: to: \\servername\home\username". The "home" folder group is

shared on the server to domain users. The home folders are also hosted on a

DC.

 

When a user logs in the H: drive normally points to the correct location.

But I'm seeing more and more of the workstations mapping the H: drive to

\\server\home and then the user sees all home folders (even though they

cannot access them). They have to disconnect the drive, log out, log in

again and most of the time that fixes the issue.

 

What is going on? Is it a configuration issue? It is very annoying and I

cannot seem to figure this one out.

 

Thanks,

Nick

[Guest Danny Sanders]

Re: Mapping of home folders for users

 

I would suggest sharing the home folder as a hidden share, Then map to that

hidden share.

When you share the username folder put the "$" behind the sharename.

Using your example connect H: to \\servername\home\username$.

 

hth

DDS

 

 

 

"acoustix" <acoustix@discussions.microsoft.com> wrote in message

news:9AA905A2-0BB4-4278-BA9B-93B12B324C4C@microsoft.com...

> I've been having an issue with home folders being misdirected when a user

> logs into their desktop. I'm not sure if this is a server config issue or

> a

> desktop OS issue.

>

> All clients are running WinXP Pro SP2. All domain controllers are Win

> 2003

> SP1. Home folders are cofigured on users profiles in AD. I have selected

> "connect H: to: \\servername\home\username". The "home" folder group is

> shared on the server to domain users. The home folders are also hosted on

> a

> DC.

>

> When a user logs in the H: drive normally points to the correct location.

> But I'm seeing more and more of the workstations mapping the H: drive to

> \\server\home and then the user sees all home folders (even though they

> cannot access them). They have to disconnect the drive, log out, log in

> again and most of the time that fixes the issue.

>

> What is going on? Is it a configuration issue? It is very annoying and I

> cannot seem to figure this one out.

>

> Thanks,

> Nick

[Guest acoustix]

Re: Mapping of home folders for users

 

Ok. Do I still need to have the home folder shared then? Or would the path

look like "\\server\username$" instead of "\\server\home\username$" ?

 

Thanks for your help!

Nick

 

"Danny Sanders" wrote:

> I would suggest sharing the home folder as a hidden share, Then map to that

> hidden share.

> When you share the username folder put the "$" behind the sharename.

> Using your example connect H: to \\servername\home\username$.

>

> hth

> DDS

>

>

>

> "acoustix" <acoustix@discussions.microsoft.com> wrote in message

> news:9AA905A2-0BB4-4278-BA9B-93B12B324C4C@microsoft.com...

> > I've been having an issue with home folders being misdirected when a user

> > logs into their desktop. I'm not sure if this is a server config issue or

> > a

> > desktop OS issue.

> >

> > All clients are running WinXP Pro SP2. All domain controllers are Win

> > 2003

> > SP1. Home folders are cofigured on users profiles in AD. I have selected

> > "connect H: to: \\servername\home\username". The "home" folder group is

> > shared on the server to domain users. The home folders are also hosted on

> > a

> > DC.

> >

> > When a user logs in the H: drive normally points to the correct location.

> > But I'm seeing more and more of the workstations mapping the H: drive to

> > \\server\home and then the user sees all home folders (even though they

> > cannot access them). They have to disconnect the drive, log out, log in

> > again and most of the time that fixes the issue.

> >

> > What is going on? Is it a configuration issue? It is very annoying and I

> > cannot seem to figure this one out.

> >

> > Thanks,

> > Nick

>

>

>

[Guest Danny Sanders]

Re: Mapping of home folders for users

 

I *think* they will need list folder contents on the home folder and the

path would be \\server\username$.

It's been a while since I set this up at my last job.

 

hth

DDS

 

"acoustix" <acoustix@discussions.microsoft.com> wrote in message

news:6A2CDAC3-83FC-406C-985A-ECB646964F3F@microsoft.com...

> Ok. Do I still need to have the home folder shared then? Or would the

> path

> look like "\\server\username$" instead of "\\server\home\username$" ?

>

> Thanks for your help!

> Nick

>

> "Danny Sanders" wrote:

>

>> I would suggest sharing the home folder as a hidden share, Then map to

>> that

>> hidden share.

>> When you share the username folder put the "$" behind the sharename.

>> Using your example connect H: to \\servername\home\username$.

>>

>> hth

>> DDS

>>

>>

>>

>> "acoustix" <acoustix@discussions.microsoft.com> wrote in message

>> news:9AA905A2-0BB4-4278-BA9B-93B12B324C4C@microsoft.com...

>> > I've been having an issue with home folders being misdirected when a

>> > user

>> > logs into their desktop. I'm not sure if this is a server config issue

>> > or

>> > a

>> > desktop OS issue.

>> >

>> > All clients are running WinXP Pro SP2. All domain controllers are Win

>> > 2003

>> > SP1. Home folders are cofigured on users profiles in AD. I have

>> > selected

>> > "connect H: to: \\servername\home\username". The "home" folder group

>> > is

>> > shared on the server to domain users. The home folders are also hosted

>> > on

>> > a

>> > DC.

>> >

>> > When a user logs in the H: drive normally points to the correct

>> > location.

>> > But I'm seeing more and more of the workstations mapping the H: drive

>> > to

>> > \\server\home and then the user sees all home folders (even though they

>> > cannot access them). They have to disconnect the drive, log out, log

>> > in

>> > again and most of the time that fixes the issue.

>> >

>> > What is going on? Is it a configuration issue? It is very annoying

>> > and I

>> > cannot seem to figure this one out.

>> >

>> > Thanks,

>> > Nick

>>

>>

>>