| Author |
Message |
Davidoj
Guest
|
 Posted:
Wed Apr 20, 2005 2:28 pm Post subject:
users home folder maping |
|
|
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until next
boot
Has anyone had similar issues? |
|
| Back to top |
|
 |
Todd J Heron
Guest
|
| Posted:
Wed Apr 20, 2005 3:54 pm Post subject:
Re: users home folder maping |
|
|
Hi,
If you are using the AD "Connect" feature to map the home directory then do
not use a loginscript to map the home directory. If you are using a
loginscript to map home directory then do not use the "Connect" feature.
Use one or the other but not both as this will cause problems. Are you or
are you not using a loginscript in any way? And what OS is the client
running?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
davidoj
Guest
|
| Posted:
Wed Apr 20, 2005 4:06 pm Post subject:
Re: users home folder maping |
|
|
I'm not useing a logonscript to map the home folder also just the "Connect"
feature but I use logon scripts to map other drives like department drives
and program shares and they should not conflict with the mapping of the home
folder. All clients are XP sp2
"Todd J Heron" wrote:
| Quote: | Hi,
If you are using the AD "Connect" feature to map the home directory then do
not use a loginscript to map the home directory. If you are using a
loginscript to map home directory then do not use the "Connect" feature.
Use one or the other but not both as this will cause problems. Are you or
are you not using a loginscript in any way? And what OS is the client
running?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
|
|
|
| Back to top |
|
|
Todd J Heron
Guest
|
| Posted:
Wed Apr 20, 2005 4:56 pm Post subject:
Re: users home folder maping |
|
|
Ok, that is correct. It was only the home dir mapping that could
potentially conflict here. For a user who cannot map correctly one a
certain machine, does this behavior follow them around to other machines?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights |
|
| Back to top |
|
|
Davidoj
Guest
|
| Posted:
Wed Apr 20, 2005 6:57 pm Post subject:
Re: users home folder maping |
|
|
My latest testing indicates it is bound to computers only. currently I'm
putting a new image on one of the computers to se if it solves the problem
"Todd J Heron" wrote:
| Quote: | Ok, that is correct. It was only the home dir mapping that could
potentially conflict here. For a user who cannot map correctly one a
certain machine, does this behavior follow them around to other machines?
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
|
|
|
| Back to top |
|
|
Steve B
Guest
|
| Posted:
Tue Jun 28, 2005 2:26 pm Post subject:
RE: users home folder maping |
|
|
I am having exactly the same problem, but havent got to the bottom of it. Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large directory
over a slow link. The mapping occasionally works to the correct sub folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
| Quote: | I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until next
boot
Has anyone had similar issues? |
|
|
| Back to top |
|
|
Steve B
Guest
|
| Posted:
Wed Jun 29, 2005 8:51 am Post subject:
Re: users home folder maping |
|
|
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do connect to
the server by name, but do not traverse the file system to the target folder.
Server is operating fine and there are no errors in the event logs on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
| Quote: | Hi Steve,
Not sure if this helps, but have you made sure you have the correct DNS
setup? That is, all clients/servers point to internal DNS only and DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large
directory
over a slow link. The mapping occasionally works to the correct sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
Denis Wong @ Hong Kong
Guest
|
| Posted:
Wed Jun 29, 2005 8:52 am Post subject:
Re: users home folder maping |
|
|
Hi Steve,
Not sure if this helps, but have you made sure you have the correct DNS
setup? That is, all clients/servers point to internal DNS only and DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
| Quote: | I am having exactly the same problem, but havent got to the bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large
directory
over a slow link. The mapping occasionally works to the correct sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until
next
boot
Has anyone had similar issues? |
|
|
| Back to top |
|
|
Steve B
Guest
|
| Posted:
Wed Jul 06, 2005 12:51 pm Post subject:
Re: users home folder maping |
|
|
Anyone have any ideas? If not, is there a good place I can be pointed to try
and follow this up (maybe MS tech support?). Any help would be useful as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
| Quote: | Thanks for the reply
All clients are pointing to internal AD integrated DNS and the servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do connect to
the server by name, but do not traverse the file system to the target folder.
Server is operating fine and there are no errors in the event logs on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the correct DNS
setup? That is, all clients/servers point to internal DNS only and DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large
directory
over a slow link. The mapping occasionally works to the correct sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
KJ
Guest
|
| Posted:
Wed Jul 13, 2005 4:52 pm Post subject:
Re: users home folder maping |
|
|
We are having the same issue. It is happening on laptops with wireless cards
also attached. I have set the local connection as top billed, then wireless,
then firewire. It is to no avail. A fresh reboot in morning and I might be at
Home folder on P drive or I might be at my username on P drive. 2000 domain
using Xp Pro laptop. Policy is not set but on local PC I am redirecting my
docs to "pipes" of my Home folder locally not using Group Policy. We have
WINS settings, DNS internal and gateway settings on DHCP server. I also get
duplicate domain.com.domain.com when doiing Nslookups at times, never had
this occur before either.
"Steve B" wrote:
| Quote: | Anyone have any ideas? If not, is there a good place I can be pointed to try
and follow this up (maybe MS tech support?). Any help would be useful as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do connect to
the server by name, but do not traverse the file system to the target folder.
Server is operating fine and there are no errors in the event logs on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the correct DNS
setup? That is, all clients/servers point to internal DNS only and DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large
directory
over a slow link. The mapping occasionally works to the correct sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
Steve B
Guest
|
| Posted:
Thu Jul 14, 2005 4:52 pm Post subject:
Re: users home folder maping |
|
|
Ive looked some more and Ive got a hunch its to do with Deep Folder
implementation. If you check this out there is a microsoft page which
describes the kind of behaviour we are seeing.
We are also using home folder redirection and I wonder if it is this problem
with the %homeshare%%homepath% variables that get interpretted. (check your
XP redirected folder policy on a 2000 machine to see what I mean)
Can anyone further this?
You can disable the behaviour in group policy, but Im loathe to yet as the
would have to be done locally on the 2000 server (XP policy templates dont
have the option???) and the server is huge with a lot of data. I dont want
users to lose access just to test my theory (BTW it would be a 1000+ users)
"KJ" wrote:
| Quote: | We are having the same issue. It is happening on laptops with wireless cards
also attached. I have set the local connection as top billed, then wireless,
then firewire. It is to no avail. A fresh reboot in morning and I might be at
Home folder on P drive or I might be at my username on P drive. 2000 domain
using Xp Pro laptop. Policy is not set but on local PC I am redirecting my
docs to "pipes" of my Home folder locally not using Group Policy. We have
WINS settings, DNS internal and gateway settings on DHCP server. I also get
duplicate domain.com.domain.com when doiing Nslookups at times, never had
this occur before either.
"Steve B" wrote:
Anyone have any ideas? If not, is there a good place I can be pointed to try
and follow this up (maybe MS tech support?). Any help would be useful as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do connect to
the server by name, but do not traverse the file system to the target folder.
Server is operating fine and there are no errors in the event logs on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the correct DNS
setup? That is, all clients/servers point to internal DNS only and DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very large
directory
over a slow link. The mapping occasionally works to the correct sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
Travis Duffy
Guest
|
| Posted:
Fri Jul 22, 2005 4:51 pm Post subject:
Re: users home folder maping |
|
|
I am also having this same issue. It affects our users with windows xp but
not windows 2000. Does anyone have any solutions or work arounds for this
issue yet? FYI, I am not implimenting any folder redirection, just
specifying the home directory path within the user account properties and
mapping the drive to H:
"Steve B" <SteveB@discussions.microsoft.com> wrote in message
news:96562CC6-90B4-4FCD-94BA-E62602675279@microsoft.com...
| Quote: | Ive looked some more and Ive got a hunch its to do with Deep Folder
implementation. If you check this out there is a microsoft page which
describes the kind of behaviour we are seeing.
We are also using home folder redirection and I wonder if it is this
problem
with the %homeshare%%homepath% variables that get interpretted. (check
your
XP redirected folder policy on a 2000 machine to see what I mean)
Can anyone further this?
You can disable the behaviour in group policy, but Im loathe to yet as the
would have to be done locally on the 2000 server (XP policy templates dont
have the option???) and the server is huge with a lot of data. I dont want
users to lose access just to test my theory (BTW it would be a 1000+
users)
"KJ" wrote:
We are having the same issue. It is happening on laptops with wireless
cards
also attached. I have set the local connection as top billed, then
wireless,
then firewire. It is to no avail. A fresh reboot in morning and I might
be at
Home folder on P drive or I might be at my username on P drive. 2000
domain
using Xp Pro laptop. Policy is not set but on local PC I am redirecting
my
docs to "pipes" of my Home folder locally not using Group Policy. We
have
WINS settings, DNS internal and gateway settings on DHCP server. I also
get
duplicate domain.com.domain.com when doiing Nslookups at times, never
had
this occur before either.
"Steve B" wrote:
Anyone have any ideas? If not, is there a good place I can be pointed
to try
and follow this up (maybe MS tech support?). Any help would be useful
as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the
servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering
correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do
connect to
the server by name, but do not traverse the file system to the
target folder.
Server is operating fine and there are no errors in the event logs
on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the
correct DNS
setup? That is, all clients/servers point to internal DNS only and
DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the
bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very
large
directory
over a slow link. The mapping occasionally works to the correct
sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they
map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back
on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry
key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home
folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
Mark Clark
Guest
|
| Posted:
Wed Oct 05, 2005 8:50 pm Post subject:
Re: users home folder maping |
|
|
We have the same problem with Windows XP and AD2000. Mapping folder to root
or \\server\users$ instead of \\server\users$\staff\maclark. This is
intermittent.
"Travis Duffy" wrote:
| Quote: | I am also having this same issue. It affects our users with windows xp but
not windows 2000. Does anyone have any solutions or work arounds for this
issue yet? FYI, I am not implimenting any folder redirection, just
specifying the home directory path within the user account properties and
mapping the drive to H:
"Steve B" <SteveB@discussions.microsoft.com> wrote in message
news:96562CC6-90B4-4FCD-94BA-E62602675279@microsoft.com...
Ive looked some more and Ive got a hunch its to do with Deep Folder
implementation. If you check this out there is a microsoft page which
describes the kind of behaviour we are seeing.
We are also using home folder redirection and I wonder if it is this
problem
with the %homeshare%%homepath% variables that get interpretted. (check
your
XP redirected folder policy on a 2000 machine to see what I mean)
Can anyone further this?
You can disable the behaviour in group policy, but Im loathe to yet as the
would have to be done locally on the 2000 server (XP policy templates dont
have the option???) and the server is huge with a lot of data. I dont want
users to lose access just to test my theory (BTW it would be a 1000+
users)
"KJ" wrote:
We are having the same issue. It is happening on laptops with wireless
cards
also attached. I have set the local connection as top billed, then
wireless,
then firewire. It is to no avail. A fresh reboot in morning and I might
be at
Home folder on P drive or I might be at my username on P drive. 2000
domain
using Xp Pro laptop. Policy is not set but on local PC I am redirecting
my
docs to "pipes" of my Home folder locally not using Group Policy. We
have
WINS settings, DNS internal and gateway settings on DHCP server. I also
get
duplicate domain.com.domain.com when doiing Nslookups at times, never
had
this occur before either.
"Steve B" wrote:
Anyone have any ideas? If not, is there a good place I can be pointed
to try
and follow this up (maybe MS tech support?). Any help would be useful
as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the
servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering
correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do
connect to
the server by name, but do not traverse the file system to the
target folder.
Server is operating fine and there are no errors in the event logs
on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the
correct DNS
setup? That is, all clients/servers point to internal DNS only and
DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the
bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very
large
directory
over a slow link. The mapping occasionally works to the correct
sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they
map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back
on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry
key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home
folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
Rob
Guest
|
| Posted:
Fri Nov 04, 2005 5:50 pm Post subject:
Re: users home folder maping |
|
|
I of course am having the same issue with this, Does anyone have any
clue??
Mark Clark wrote:
| Quote: | We have the same problem with Windows XP and AD2000. Mapping folder to root
or \\server\users$ instead of \\server\users$\staff\maclark. This is
intermittent.
"Travis Duffy" wrote:
I am also having this same issue. It affects our users with windows xp but
not windows 2000. Does anyone have any solutions or work arounds for this
issue yet? FYI, I am not implimenting any folder redirection, just
specifying the home directory path within the user account properties and
mapping the drive to H:
"Steve B" <SteveB@discussions.microsoft.com> wrote in message
news:96562CC6-90B4-4FCD-94BA-E62602675279@microsoft.com...
Ive looked some more and Ive got a hunch its to do with Deep Folder
implementation. If you check this out there is a microsoft page which
describes the kind of behaviour we are seeing.
We are also using home folder redirection and I wonder if it is this
problem
with the %homeshare%%homepath% variables that get interpretted. (check
your
XP redirected folder policy on a 2000 machine to see what I mean)
Can anyone further this?
You can disable the behaviour in group policy, but Im loathe to yet as the
would have to be done locally on the 2000 server (XP policy templates dont
have the option???) and the server is huge with a lot of data. I dont want
users to lose access just to test my theory (BTW it would be a 1000+
users)
"KJ" wrote:
We are having the same issue. It is happening on laptops with wireless
cards
also attached. I have set the local connection as top billed, then
wireless,
then firewire. It is to no avail. A fresh reboot in morning and I might
be at
Home folder on P drive or I might be at my username on P drive. 2000
domain
using Xp Pro laptop. Policy is not set but on local PC I am redirecting
my
docs to "pipes" of my Home folder locally not using Group Policy. We
have
WINS settings, DNS internal and gateway settings on DHCP server. I also
get
duplicate domain.com.domain.com when doiing Nslookups at times, never
had
this occur before either.
"Steve B" wrote:
Anyone have any ideas? If not, is there a good place I can be pointed
to try
and follow this up (maybe MS tech support?). Any help would be useful
as Ive
seen Im not the only one who's having this problem
Maybe a bug??
"Steve B" wrote:
Thanks for the reply
All clients are pointing to internal AD integrated DNS and the
servers also
are running WINS. DNS is running WINS lookup. All member servers are
configured with the correct zone suffix and are registering
correctly. The
problem is on a member server
Cant see this is a name resolution issue though as the clients do
connect to
the server by name, but do not traverse the file system to the
target folder.
Server is operating fine and there are no errors in the event logs
on it or
the clients.
Anyone seen this or found a workaround?
"Denis Wong @ Hong Kong" wrote:
Hi Steve,
Not sure if this helps, but have you made sure you have the
correct DNS
setup? That is, all clients/servers point to internal DNS only and
DNS
server forwards to ISP?
Also try to post any relevant event log details here.
br,
Denis
"Steve B" <Steve B@discussions.microsoft.com> wrote in message
news:4E36169B-202D-48EE-87F4-7D653C4AD043@microsoft.com...
I am having exactly the same problem, but havent got to the
bottom of it.
Im
hoping someone has found a cure?
The only thing in common is that they are mapping to a very
large
directory
over a slow link. The mapping occasionally works to the correct
sub
folder,
but is not consistent
Anyone?
Thanks
"Davidoj" wrote:
I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they
map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back
on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry
key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home
folder until
next
boot
Has anyone had similar issues?
|
|
|
| Back to top |
|
|
mlrowan
Guest
|
| Posted:
Fri Nov 11, 2005 5:50 pm Post subject:
RE: users home folder maping |
|
|
We are having exactly the same issue...users are mapping to the USERS share
point rather than deep mapping to home folders inside the share. Problem
arose after a script was run to move 200 users to a new server. This process
seems to have 'broken' profile based deep mapping. Manual deep mapping still
works. We also run scripts to map other drives and used the net use g: /HOME
variable when we had WIN9X devices.Unfortunately, the next step seems to be
MS support. Any other suggestions would be greatly appreciated...
"Davidoj" wrote:
| Quote: | I'm having trouble with users home folder mapings
users profile tab is configured like this
profile path:
Logon script:
home folder: h: to \\servercluster\share\username
it seems as some users are not able to map it correctly, they map it as
\\servercluster\share
if I run gpupdate \force and log off the user and log it back on it maps
correctly until the next reboot.
I found out that those settings are stored in this registry key:
HK_Users\S-1-5-21-...\Volatile Enviroment
Users that map the home folder right have those settings
Homedrive: h:
Homepath: \
Homeshare: \\servercluster\share\username
But those that don't map the folder right hafe those settings
Homedrive: h:
Homepath: \username
Homeshare: \\servercluster\share\
If I change the registry settings the user maps the home folder until next
boot
Has anyone had similar issues? |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in