Hi,
I am trying to use some Environment Variables in our network for easier handling of several packages.
I have a script that successfully sets the Environment Variables on the client PC. The problem is however that I am unable to get this seen by NALDESK(Application Explorer) without a reboot.
I have written a program that sends out the broadcast using user32.dll and SendMessage, however it doesnt seem Application Explorer listens on this and then updates.
Are there any ways I can update what the program has stored as Env Variables without a restart of the client PC?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
How do you set the environment variables?
When you set them from the Novell client login script they should be immediately visible by Naldesk
DOS SET VARIABLE="Value"
Variables set otherwise are usually only active in the session in which they are set, and thus not globally available. If you want environment variables to be systemwide you can add them with setx.exe from the Windows XP Support tools:
http://www.microsoft.com/D
BURRCM -> A nice tips, but sadly it doesnt work.
DEROODE -> It is not set during logon, it is set as a ZEN application. I use the SETX application, however NAL doesnt see this untill the computer is restarted.
On another note, I went away from the separate batch script and wrote this as pre and post distribution with the VBScript in the middle as the object to distribute.
-> THIS WORKS!! it is properly set and another refresh of NAL will allow me to see this. I wish I could skip having the extra manual refresh of NAL. I've tried tieng the application dependent upon the script to it, but it wont appear till after that extra refresh.
I've done some experimenting, with the following results:
setx or setx -m set user or machine environment variables, but they are not visible in the same session. When starting another session (cmd.exe) they are visible.
Set does precisely the opposite: these are only available within the session.
You could combine both set and setx to achieve your wanted result: environment variables that are available both inside and outside the session.
AND you can set environment variables in de NAL application itself:
Run options - Environment variables.
Business Accounts
Answer for Membership
by: burrcmPosted on 2009-10-08 at 23:56:56ID: 25532803
Try stopping and restarting explorer.exe.
Chris B