I wrote a script to update the local AD, replace the values in [] with your values. Copy and paste into a. Sounds like the AD profile on the domain is overwriting the user defined variables. I see your screenshot says you are connected to the eait. That will be the root of your issue. Just to include some details here that I spotted elsewhere, that may be of help to you:. This way, if you are using openSSH over the console anyway, it will always have the homedrive set correctly.
Changing those environment variable's values is not "supported", at least it will not work as you expect because Windows changes them back. According to this Microsoft knowledge base article KB , you should use policies, if you need to change these settings.
The article also contains links for how to do that but personally, I never tried. Note that the article was originally written for Windows , but I would strongly suspect, that it is still valid for current Windows versions. Back in the days of DOS the environment variables were part of the Program Segement which meant that you basically got a local snapshop of the variables limited to the scope of that program.
I'm guessing Windows hasn't changed this and the environment variables available to the CMD window only have the scope of that window and any further windows it spawns. This is supported by this little experiment:. This was just for one particular user.
I went to that user's profile in AD and clicked the Attribute Editor tab. I also updated the HomeDirectory attribute here. This issue had been really frustrating me trying to find a solution, but I have found what I think is the definitive answer and posted it at:.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 3 months ago. Active 2 months ago. Viewed 55k times. I found a way to change the default home directory of a user but I am having trouble with it. Improve this question. Fantastic Mr Fox. If the environment variable is reverting, it is likely that group policy is involved.
Are you the administrator of the machine? Is the machine joined to a domain? One option would be to write a batch file that changes the environment variable and then launches OpenSSH. What version of OpenSSH exactly? Add a comment. Active Oldest Votes. SetInfo e. SetInfo run this, reboot and test. It worked for me. Improve this answer. You can use environment variables in the values of other environment variables. It is then helpful to be able to see what environment variables are set already.
This is how you do it:. To set persistent environment variables at the command line, we will use setx. Prior to that, it was part of the Windows Resource Kit. If you need the Windows Resource Kit, see Resources at the bottom of the page. When setting environment variables through the registry, they will not recognized immediately.
One option is to log out and back in again. One way is to get this message issued is to open the environment variables in the GUI, like we do in HowTo: Set an Environment Variable in Windows - GUI ; we do not need to change anything, just open the Environment Variables window where we can see the environment variables, then hit OK.
Another way to get the message issued is to use setx , this allows everything to be done on the command line, however requires setting at least one environment variable with setx. With Windows XP, the reg tool allows for accessing the registry from the command line. We can use this to look at the environment variables. This will work the same way in the command prompt or in powershell.
