5.4.10622 32bit only?!
Since upgrading clients to 5.4.10622 I've noticed our MI installs are having issues.
It seems like klaunch now launches C:\Windows\SysWOW6432\cmd.exe instead of C:\Windows\System32\cmd.exe maybe?
Reason is that %PROCESSOR_ARCHITECTURE% now returns x86 on a 64bit system instead of AMD64. I'm going to try %PROCESSOR_ARCHITEW6432%, but it's not just that and registry that's a problem. The bat installation file we use can do many things including copy files to locations, using cacls to set file permissions, underfortunately files are no longer found because they're being redirected to C:\Windows\SysWOW6432\ instead of C:\Windows\System32\.
This is a big change and causing me problems, didn't see it mentioned on the release notes.
Need to review all my install scripts to find all the problems.
Anyone else come across this yet?
Answers (3)
the 5.4AP1 (5.4.10622) agent seems really to be only 32Bit, I will check it later, when I have access to x64 clients
5.4 ? what product?
Comments:
-
of the K1000 agent that gets deployed to client machines. - dallama1985 11 years ago
-
check - jaybee96 11 years ago
The agent for Windows has always been 32 bit. There are 64 bit options for Linux, but not Windows yet.
I'd submit a support ticket so that it can be looked into.
Comments:
-
Perhaps it's not so much the bit of the Kace client, but when calling a bat file inside a zip file, perhaps it used to use C:\Windows\System32\cmd.exe and now it's using C:\Windows\SysWOW6432\cmd.exe - AJStevens 11 years ago
-
I'd say that's actually working as expected. 32 bit apps get redirected to WOW6432: http://msdn.microsoft.com/en-us/library/windows/desktop/ms724072%28v=vs.85%29.aspx
This helps explain it too: http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.aspx
I don't know if this is a new thing when calling a batch file in a MI, but it's been the case with kscripts since at least K1 version 5.2. - jknox 11 years ago
-
Make a MI, attach a ZIP file containing a .bat script file, and inside it just do something simple like @echo %PROCESSOR_ARCHITECTURE%. In the MI set the command as: test.bat >> C:\Test.log
Now, run this on a computer with the 5.4.10622 client, and another running the previous 5.4.5315 (or whatever it was).
You'll get two log files, the 5.4.10622 will say "x86", and the 5.4.5315 will say "AMD64".
Now there is an alternative to use for %PROCESSOR_ARCHITECTURE%, but it's all the other things that are redirected which are a problem, C:\Windows\System32\ is forced redirected to C:\Windows\SysWOW6432\ including subfolders, which is causing me grief with one particular MI install script.
but overall I'm having to go through all my MI's to test they still work. - AJStevens 11 years ago
