新聞財經娛樂♬資訊 News Economy

I'm looking for a quick and easy way of exporting and importing Windows environment variables.

I have a user who creates a lot of custom Windows environment variables that do things such as launch custom Windows Explorer paths, open different programs, and do other things.

These variables are defined with letters such as u that has a value of C:Users so that when the user types in %u% within a Windows Explorer browser window or within the run dialog box Windows Explorer will open in the C:Users folder.

The user also has several programs that will launch if other variables such as %a% or %m% are typed in.

We would like to be able to export these custom Windows Explorer environment variables so that they can be exported into another Windows operating system.

How can this be done?

Once you export the registry key(s) as a .reg file--using one of the methods above--all you have to do is double-click the .reg file and it will import them in a couple clicks. (Be sure and remove all but your "custom" entries from the .reg file using a text editor before importing, or you will likely mess up the Windows defined variables that may vary from computer to computer.) This will be the easiest method to setup, and probably also the fastest (even with the additional clicks) if you were planning on running the script "manually" on each computer.

If you specifically want a script that can be run during logon, you can do it directly from a .bat file using the "reg add" command. (reference: http://technet.microsoft.com/en-us/library/cc742162.aspx.) -- This approach requires one "reg add" command for each environment var you want to add.

Alternative ways to script it: Use powershell (I've never done it this way, so I don't know the exact process.)
Use a third party utility like kixtart that can be used in a script to import a .reg file.

Note: You may come across mentions of importing a .reg file from the command line/script using the "regedit" command. If I remember correctly this method no longer works with the increased security in Win7/8, at least it doesn't work easily. The other script solutions I mentioned will likely need to be ran from an elevated command prompt.

Win environment variables that is depended on how you define its definition.

Some third-party application variables being installed in the window that you can classify it as win variables so, regedit is useful

IF just window 7 variable system itself, set > env.txt

So, all insides and outside application or system variable stored in window ,we
call window variable, Right ?

Duncan

if so, why not just "set" command at cmd.exe shell without powershell

 set > env.txt


Duncan

Hi,

The registry keys will work, but just thought an easy way to export is with PowerShell.

dir env: >env.txt  

This will save all the environment variables to a text file. If I knew more PowerShell I could suggest a way to import them, but I'm still learning it.
It has the advantage of producing a nice list you can print (or read).

Mike

You can write batch script to save all registry key into file and import it on other computer, for example,

regedit /e "c:yourtargetkey.reg" HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerEnvironment HKEY_CURRENT_USEREnvironment

Hope understand your question.If not, pls pt it out
Duncan

The environment variables are stored in two registry keys (system wide and user specific)

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerEnvironment HKEY_CURRENT_USEREnvironment

Use a text editor to edit (and combine/if desired) the .reg file it exports. Keep only the "custom" entries you want to export/import. E.G. You do NOT want to import the windows created environment variables from another computer.

If double-clicking the .reg file on each computer to "manually" import is not sufficient, there are various ways to automate pushing the registry entries onto multiple computers. (But most of the methods are more work than they are worth if you're just doing a one-time import onto a handful of computers.)