(imported topic written by SystemAdmin)
For some reason this line of my actionscript is doing something that I can’t quite wrap my mind around on some (not all) of my machines.
Here is the line in my action script:
waithidden cmd /c setx
"Path"
"{(value "Path
" of key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
" of registry as string) & ";
" & "C:\Program Files\L1ID\TP-LSMULTI SDK\bin
"}" /M
It simply calls setx to append a value to the system path environment variable.
In the logs on the machines where it works on I see:
Command succeeded (Exit Code=0) waithidden cmd /c setx
"Path"
"C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;C:\L3270;C:\L3270\A95W;C:\Program File\L1ID\TP-LSMULTI SDK\bin" /M (fixlet 79793)
and on the ones where it fails I see:
Command succeeded (Exit Code=0) waithidden cmd /c setx
"Path"
"C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\L3270\A95W;
Notice that it doesn’t have a closing double quote or even give the fixlet number at the end of the message.
The only difference between machines is that the ones that work are running our latest Windows 7 image, which included Service Pack 1 and the BES Client 8.0. The other machines do not have SP1, and they were upgraded to the 8.0 client from an earlier version (7.2 I think).
I find it difficult to believe that the Windows SP level has anything to do with it, since it appears that the BES Client isn’t even running the entire command… so I wonder if the 8.0 upgrade is messed up on all of our upgraded workstations?
Any thoughts?