Windows Server TechCenter > Windows Server Forums > General > Can a domain user prepend to %PATH%
Ask a questionAsk a question
 

AnswerCan a domain user prepend to %PATH%

  • Saturday, November 07, 2009 6:06 PMBrian Granger Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    I am running Windows Server HPC 2008.  Some of my domain users need to be able to *prepend* things to their %PATH% variable. 

    They need to do this because certain users need to install their own version of executables that *override* the system wide ones.

    When they set the user environment variable %path%, that get post-pended to the system %path%, so the system wide executables
    are still used.

    How can my users do this (I don't want to have to manage these things as an admin). 

    Cheers,

    Brian

Answers

  • Monday, November 09, 2009 12:14 AMMeinolf Weber [MVP-DS]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hello,

    as far as i know they must be local admin to achive that. Another option is that you configure them(even it is more work) according to:
    http://technet.microsoft.com/en-us/library/cc772047(WS.10).aspx
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
  • Monday, November 09, 2009 2:32 AMGunner999 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    There are several variations of the same basic principal you can use to do this.

    Basic Principal
    Any manually started command prompt allows manipulation of the SYSTEM PATH variable in only that isolated instance.  For example open two command prompts.  In the first one type "SET Path=" to clear the path, in the other "Set Path=D:\;%path%".  In both type "Set Path" to view the results.  They are both different....but how can this be?  By default, each time a process is started it receives a copy of the current system state, each can then modify that state independently of each other.  Also, all processes launched from that parent CMD.exe is part of a Process Tree, and should inherit the PATH varaiable configuration of the launching process.

    Variations
    1) Use a batch file to modify the PATH variable before launching any process.
    2) Use a shortcut to lauch a CMD process that runs a batch file
    3) Use a shortcut to launch a Batch file
    4) Use the Start command with or without the /I switch to laucn procresses with the current environemtn or with the original system environment.

All Replies

  • Monday, November 09, 2009 12:14 AMMeinolf Weber [MVP-DS]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Hello,

    as far as i know they must be local admin to achive that. Another option is that you configure them(even it is more work) according to:
    http://technet.microsoft.com/en-us/library/cc772047(WS.10).aspx
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
  • Monday, November 09, 2009 2:32 AMGunner999 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    There are several variations of the same basic principal you can use to do this.

    Basic Principal
    Any manually started command prompt allows manipulation of the SYSTEM PATH variable in only that isolated instance.  For example open two command prompts.  In the first one type "SET Path=" to clear the path, in the other "Set Path=D:\;%path%".  In both type "Set Path" to view the results.  They are both different....but how can this be?  By default, each time a process is started it receives a copy of the current system state, each can then modify that state independently of each other.  Also, all processes launched from that parent CMD.exe is part of a Process Tree, and should inherit the PATH varaiable configuration of the launching process.

    Variations
    1) Use a batch file to modify the PATH variable before launching any process.
    2) Use a shortcut to lauch a CMD process that runs a batch file
    3) Use a shortcut to launch a Batch file
    4) Use the Start command with or without the /I switch to laucn procresses with the current environemtn or with the original system environment.