Hope someone can help

I've just started using the K1000 this week, so sorry if this is a daft question (I'm sure I'll have loads more for you though). I'm just playing about at the moment trying to get my head round things

Manually created a Software Inventory record (called Disable Updaters) for a script I use that copies files to computers and runs reg entries to disable updaters on various products (Adobe Reader, Flash and Java). Associated the .bat file with the record

Created a Managed Installation and ran it on my Test group. All worked fine. Files were copied to the correct locations on 32 and 64 bit operating systems and reg entries worked OK

Noticed that the Software Inventory record called "Disable Updaters" was still showing that it was installed on 0 computers, so I thought I'd add a Custom Inventory record so that installations would be detected

Thought I'd be able to add the following
FileExists(c:\windows\system32\macromed\flash\mms.cfg) OR FileExists(c:\windows\syswow64\macromed\flash\mms.cfg)

but decided just to try this first of all

Forced an update on the clients but got odd results back

The Win 7 32bit clients were showing as having the software installed but so were the 64 bit clients

Double checked the 64bit clients manually and c:\windows\system32\macromed\flash\mms.cfg does not exist

I expect I'm doing something completely ridiculous. Can anyone offer any advice please ?


Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



Your method looks right to me. Guessing this is happening because your Kace agent is 32 bit. The SysWOW64 folder contains the 32-bit system files and System32 contains the 64-bit system files on a 64 bit machine. This is done for backward compatibility. So the 32 bit agent is getting tricked into thinking SysWow64 is actually System32. Not positive if this is your issue, but I had similar problems using the 32 bit agent on 64 bit machines.

Answered 08/09/2013 by: SDNBTP
Third Degree Blue Belt

  • I would create a short vbs script and rund a CIR with ShellCommandTextReturn as I am not happy how the CIR currently is working if you want to run a bit more complex CIR like you do. You may or may not run into strange issues.
  • Thanks for your comments. I thought that checking to see if a file existed on 32 / 64 bit OS would have been straight forward. Apparently not. Ha ha

    I'm going to have some fun with KACE aren't I ?

  • Actually, DriveBlind, you're going to go crazy trying to work with 64-bit Windows with the 32-bit KACE Agent. It's not impossible, but it's not easy, either. I think this is a perfect example.
  • Oh joy. Is there no way of having 32 and 64 bit versions of the agent on 32/64 bit operating systems ?
Please log in to comment