/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Issues calling cmd.exe from C:\Windows\Sysnative after upgrade from 6.4 to 7.1 then 7.2

12/21/2017 2291 views
  Hi All,

We have previously been getting around the 32-Bit process limitation of the KACE product by specifically calling out c:\Windows\sysnative\cmd.exe on scripts that require 64-Bit for tasks such as registry modifications.

This however no longer functions now, and strangely while KACE will launch c:\Windows\sysnative\cmd.exe the command process has null access and cannot query the file system, registry, etc.
The product still seems to retain the 32-bit limitations though as C:\Windows\system32\cmd.exe only has access to the 32-Bit reg?

2 Comments   [ + ] Show comments

Comments

  • Try regedit.exe /s regfile.reg /reg:64
  • I narrowed the issue down to specifically when cmd.exe is called from c:\Windows\sysnative\cmd.exe and then runs an external utility that returns output to the command prompt, E.G. reg.exe or WMIC.. This prevents more complex bat files from being able to be ran natively on 64-bit systems. I can sort of work around it by invoking the command with powershell.exe but that's kind of a dirty kludge.

Be the first to answer this question

 
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