/build/static/layout/Breadcrumb_cap_w.png

64 bit Office processes not detected in KScripts

I have a simple Online Kscript that just copies a new Normal.dotm and NormalEmail.dotm to %appdata%\Microsoft\Templates.  If Word or Outlook are open, the files will not update so I have a Verify condition to "Verify a process is NOT running" set to check for "outlook.exe" and another check for winword.exe. 

As a test I have both Outlook and Word open, but KACE logs show that the scripts did not detect Outlook.exe or Winword.exe so they attempt to install the files and fail.  

I thought I could do a brute force install by just configuring the task to Kill Process Winword.exe and Kill Process Outlook.exe, but I get an error saying it Kace could not detect either running.

I have the x64 version of Office installed on a x64 Windows 10 20H1.  Since KACE is a 32 bit agent, do I need to reference Outlook.exe and Winword.exe in some special way to detect it correctly?


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Nico_K 1 month ago
Red Belt
0

You may need to start the 64Bit binaries for the query you do. they are under c:\windows\synative\ instead of c:\windows\system32.


Comments:
  • Thanks Nico, but I do not understand. Do you have an example of how I would detect and kill the x64 version of Outlook.exe using the built in KScript actions on my Kace Script? - JordanNolan 1 month ago
  • Just did some testing with Quest Support. Turns out that killing or checking processes is Case Sensitive. Ughh. Never recall that being the case in earlier versions....... - JordanNolan 1 month ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ