G
Guest
Hi All,
I am currently experiencing issues with the HOMEPATH Volatile Environment
variable within our Win2k domain - primarily from the Laptop users. From the
command prompt, using the set command I get:
HOMEDRIVE=H:
HOMEPATH=\
HOMESHARE=\\arinto\mapeacock$
Which would appear to be correct. But when I look at the Volatile
Environment settings within the registry in both the HKCU\Volatile
Environment and equivalent HKU settings, I get:
HOMEDRIVE:REG_SZ:H:
HOMEPATH:REG_SZ:\\arinto\mapeacock$
HOMESHARE:REG_SZ:\\arinto\mapeacock$
H: is the home folder connected to the \\arinto\mapeacock$ network share via
Active Directory. This is where the roaming user profile is located.
The problem is that if I connect via a Citrix session and run an command
prompt, I get the following message:
CMD.EXE was stated with '\\arinto\mapeacock$' as the current path. UNC paths
are not supported. Defaulting to Windows directory.
A set command displays:
HOMEDRIVE=H:
HOMEPATH=\\arinto\mapeacock$
HOMESHARE=\\arinto\mapeacock$
If, before exiting the normal windows session I delete the Registry settings
referring to Homepath, and log off and back on, open Citrix again, the
command prompt session is then ok. But if I look at the Volatile Environment
setting within Windows( not Citrix) it has changed to the incorrect setting
again. Having run Regmon over the bootup process I can see where the Homepath
initially gets set to the '\', but a bit further down the log it gets set to
the '\\arinto\mapeacock$' value. I cannot discern where the value is getting
populated from, the only two processes logged within Regmon are Winlogon.exe
and LSASS.exe. This value also gets set if I am unplugged from the network
and log on.
Does anyone have any ideas at all? The issue is causing other problems
within Citrix, with apps that refer to the Homepath setting not finding the
correct location because it is looking for the incorrect location
H:\\arinto\mapeacock$
Regards,
Mark
I am currently experiencing issues with the HOMEPATH Volatile Environment
variable within our Win2k domain - primarily from the Laptop users. From the
command prompt, using the set command I get:
HOMEDRIVE=H:
HOMEPATH=\
HOMESHARE=\\arinto\mapeacock$
Which would appear to be correct. But when I look at the Volatile
Environment settings within the registry in both the HKCU\Volatile
Environment and equivalent HKU settings, I get:
HOMEDRIVE:REG_SZ:H:
HOMEPATH:REG_SZ:\\arinto\mapeacock$
HOMESHARE:REG_SZ:\\arinto\mapeacock$
H: is the home folder connected to the \\arinto\mapeacock$ network share via
Active Directory. This is where the roaming user profile is located.
The problem is that if I connect via a Citrix session and run an command
prompt, I get the following message:
CMD.EXE was stated with '\\arinto\mapeacock$' as the current path. UNC paths
are not supported. Defaulting to Windows directory.
A set command displays:
HOMEDRIVE=H:
HOMEPATH=\\arinto\mapeacock$
HOMESHARE=\\arinto\mapeacock$
If, before exiting the normal windows session I delete the Registry settings
referring to Homepath, and log off and back on, open Citrix again, the
command prompt session is then ok. But if I look at the Volatile Environment
setting within Windows( not Citrix) it has changed to the incorrect setting
again. Having run Regmon over the bootup process I can see where the Homepath
initially gets set to the '\', but a bit further down the log it gets set to
the '\\arinto\mapeacock$' value. I cannot discern where the value is getting
populated from, the only two processes logged within Regmon are Winlogon.exe
and LSASS.exe. This value also gets set if I am unplugged from the network
and log on.
Does anyone have any ideas at all? The issue is causing other problems
within Citrix, with apps that refer to the Homepath setting not finding the
correct location because it is looking for the incorrect location
H:\\arinto\mapeacock$
Regards,
Mark