G
Givdesh Dusanda
Problem:
The Active Directory Users and Computers (ADUC) snap-in
keeps expanding environmental variables in profile and/or
home-directory paths every time Apply or OK buttons are
clicked.
System: Windows 2000 SP4 AD mixed-mode network.
As many admins know environmental variables can be used in
user settings to simplify the creation of new accounts.
The theory goes that if you create a template account with
a profile path of \\server\share$\%user% then you can
generate new accounts by copying the template and the path
will be filled in at runtime with correct value for each
user.
Microsoft also say that you can also make the server name
into an environmental variable in the path for profile
path and in logon scripts. In this way a client PC at a
branch office can b directed to the closest domain
controller, rather than trying to download across a WAN to
a distant DC at HQ.
Here's the relevant URL:
http://www.microsoft.com/windows2000/en/server/help/default
..asp?url=/windows2000/en/server/help/sag_lsconcepts_3.htm
Nice idea but Windows 2000 ADUC on my system keeps
expanding the evironmental variables so that the
user/server name is filled in before the console closes.
This means template accounts loose most of their advantage
and it is only possible to download profiles from a
predetermined server, set at the DC.
I thought the upgrade to SP4 might fix this problem but no
joy there. ADUC remains stubbornly resistant to my efforts
to make it keep environmental variable names in the path
definitions.
Is there something I'm not doing? Is some special reg hack
needed to make this stuff work?
GD
The Active Directory Users and Computers (ADUC) snap-in
keeps expanding environmental variables in profile and/or
home-directory paths every time Apply or OK buttons are
clicked.
System: Windows 2000 SP4 AD mixed-mode network.
As many admins know environmental variables can be used in
user settings to simplify the creation of new accounts.
The theory goes that if you create a template account with
a profile path of \\server\share$\%user% then you can
generate new accounts by copying the template and the path
will be filled in at runtime with correct value for each
user.
Microsoft also say that you can also make the server name
into an environmental variable in the path for profile
path and in logon scripts. In this way a client PC at a
branch office can b directed to the closest domain
controller, rather than trying to download across a WAN to
a distant DC at HQ.
Here's the relevant URL:
http://www.microsoft.com/windows2000/en/server/help/default
..asp?url=/windows2000/en/server/help/sag_lsconcepts_3.htm
Nice idea but Windows 2000 ADUC on my system keeps
expanding the evironmental variables so that the
user/server name is filled in before the console closes.
This means template accounts loose most of their advantage
and it is only possible to download profiles from a
predetermined server, set at the DC.
I thought the upgrade to SP4 might fix this problem but no
joy there. ADUC remains stubbornly resistant to my efforts
to make it keep environmental variable names in the path
definitions.
Is there something I'm not doing? Is some special reg hack
needed to make this stuff work?
GD