Home Folder

Our users each have a their own Home folder. When they log into the domain,
it automatically connects them to it based on their user profile
information.

However, sometimes when they log in, it does not connect to their individual
folder but to the parent folder.

For example, a users home folder is set to this:

Z: drive --> \\Fileserver\Users\JohnDoe. The Users folder is the shared
folder in this case.

When they log in, their Z: drive should be linked to that location.

However sometimes it does not map directly to the JohnDoe folder, it maps to
the Users folder where they see all the users folders listed in there.

Why does it do this and how can I prevent it.

Thanks,
Jasper

Jasper Recto <(E-Mail Removed)> wrote:
> Our users each have a their own Home folder. When they log into the
> domain, it automatically connects them to it based on their user
> profile information.
>
> However, sometimes when they log in, it does not connect to their
> individual folder but to the parent folder.
>
> For example, a users home folder is set to this:
>
> Z: drive --> \\Fileserver\Users\JohnDoe. The Users folder is the
> shared folder in this case.
>
> When they log in, their Z: drive should be linked to that location.
>
> However sometimes it does not map directly to the JohnDoe folder, it
> maps to the Users folder where they see all the users folders listed
> in there.
> Why does it do this and how can I prevent it.
>
> Thanks,
> Jasper

This is a common problem if you haven't set "Always wait for network at
computer startup and logon" in group policy. Set up a custom GPO for this
rather than editing one of the defaults, and link it at a level where it
will apply to all your workstartions.

http://technet2.microsoft.com/window....mspx?mfr=true

THANKS!!
"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:%23hk23$(E-Mail Removed)...
> Jasper Recto <(E-Mail Removed)> wrote:
>> Our users each have a their own Home folder. When they log into the
>> domain, it automatically connects them to it based on their user
>> profile information.
>>
>> However, sometimes when they log in, it does not connect to their
>> individual folder but to the parent folder.
>>
>> For example, a users home folder is set to this:
>>
>> Z: drive --> \\Fileserver\Users\JohnDoe. The Users folder is the
>> shared folder in this case.
>>
>> When they log in, their Z: drive should be linked to that location.
>>
>> However sometimes it does not map directly to the JohnDoe folder, it
>> maps to the Users folder where they see all the users folders listed
>> in there.
>> Why does it do this and how can I prevent it.
>>
>> Thanks,
>> Jasper
>
> This is a common problem if you haven't set "Always wait for network at
> computer startup and logon" in group policy. Set up a custom GPO for this
> rather than editing one of the defaults, and link it at a level where it
> will apply to all your workstartions.
>
> http://technet2.microsoft.com/window....mspx?mfr=true
>

I also have started experiencing this problem - it has run for three years
without issues until last week or so. It seems only to affect XP (Sp2).

I have set the GPO, but reading the description it should wait for network
if a roaming or home drives are set anyway.

I have added it to the default domain policy and will see what happens.

"Lanwench [MVP - Exchange]" wrote:

> Jasper Recto <(E-Mail Removed)> wrote:
> > Our users each have a their own Home folder. When they log into the
> > domain, it automatically connects them to it based on their user
> > profile information.
> >
> > However, sometimes when they log in, it does not connect to their
> > individual folder but to the parent folder.
> >
> > For example, a users home folder is set to this:
> >
> > Z: drive --> \\Fileserver\Users\JohnDoe. The Users folder is the
> > shared folder in this case.
> >
> > When they log in, their Z: drive should be linked to that location.
> >
> > However sometimes it does not map directly to the JohnDoe folder, it
> > maps to the Users folder where they see all the users folders listed
> > in there.
> > Why does it do this and how can I prevent it.
> >
> > Thanks,
> > Jasper
>
> This is a common problem if you haven't set "Always wait for network at
> computer startup and logon" in group policy. Set up a custom GPO for this
> rather than editing one of the defaults, and link it at a level where it
> will apply to all your workstartions.
>
> http://technet2.microsoft.com/window....mspx?mfr=true
>
>
>

RobWUK <(E-Mail Removed)> wrote:
> I also have started experiencing this problem - it has run for three
> years without issues until last week or so. It seems only to affect
> XP (Sp2).

Yes (although pre-SP2 as well).
>
> I have set the GPO, but reading the description it should wait for
> network if a roaming or home drives are set anyway.

It doesn't always, though
>
> I have added it to the default domain policy and will see what
> happens.

I'd recommend setting up your own custom GPOs instead of editing the built
in ones - and I'd link this policy at an OU level that affects only your
workstations.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Jasper Recto <(E-Mail Removed)> wrote:
>>> Our users each have a their own Home folder. When they log into the
>>> domain, it automatically connects them to it based on their user
>>> profile information.
>>>
>>> However, sometimes when they log in, it does not connect to their
>>> individual folder but to the parent folder.
>>>
>>> For example, a users home folder is set to this:
>>>
>>> Z: drive --> \\Fileserver\Users\JohnDoe. The Users folder is the
>>> shared folder in this case.
>>>
>>> When they log in, their Z: drive should be linked to that location.
>>>
>>> However sometimes it does not map directly to the JohnDoe folder, it
>>> maps to the Users folder where they see all the users folders listed
>>> in there.
>>> Why does it do this and how can I prevent it.
>>>
>>> Thanks,
>>> Jasper
>>
>> This is a common problem if you haven't set "Always wait for network
>> at computer startup and logon" in group policy. Set up a custom GPO
>> for this rather than editing one of the defaults, and link it at a
>> level where it will apply to all your workstartions.
>>
>> http://technet2.microsoft.com/window....mspx?mfr=true