For more information on this mechanism, please see the following knowledge base. Handling 32-bit redirection on 64-bit Windows (4272388)
Running 32-bit Applications (learn.microsoft.com)
- Registry Redirector
- File System Redirector
Redirection of C:\Windows\System32 by 32-bit programs on 64-bit Windows platforms
| Designation within KACE | 13.2 or earlier: The actual path of the file that the agent calls | 14.0 and above |
|---|---|---|
Files/commands in C:\Windows\System32 Example: calling to cmd.exe or full path C:\Windows\System32\cmd.exe | (32 Bit redirection) Files/commands in C:\Windows\Syswow64 | (64 Bit native) Files/commands in C:\Windows\System32 |
| Invocation for C:\Windows\SysNative\cmd.exe | Files/commands in C:\Windows\System32 (64 Bit native) | Not found (error) |
| Actual registry path being referenced | Specifying registry key for v13.2 or earlier | Specifying registry key for v14.0+ |
|---|---|---|
| HKLM\SOFTWARE\Wow6432Node\MyKey (Path for 32-Bit) Check with reg.exe C:\Windows\System32\reg.exe query HKLM\Software\MyKey /reg:32 or C:\Windows\Syswow64\reg.exe query HKLM\Software\MyKey | HKLM\SOFTWARE\MyKey or HKLM32\SOFTWARE\MyKey | HKLM32\SOFTWARE\MyKey |
| (64-Bit native) HKLM\SOFTWARE\MyKey Check with reg.exe C:\Windows\System32\reg.exe query HKLM\Software\MyKey or C:\Windows\Syswow64\reg.exe query HKLM\Software\MyKey /reg:64 | HKLM64\SOFTWARE\MyKey or HKLMNAT\SOFTWARE\MyKey | HKLM\SOFTWARE\MyKey or HKLM64\SOFTWARE\MyKey or HKLMNAT\SOFTWARE\MyKey |
NOTE: All existing agent-managed devices are assumed to be 64-bit Windows platforms and 32-bit Windows will not be supported on this article.
Reworking may be necessary in the following cases too:
You can run the following Custom SQL report to extract manually created Software and list the names and inventory rule contents.SELECT ID ,DISPLAY_NAME ,INVENTORY_RULE FROM SOFTWARE WHERE (ifnull(IS_MANUAL,0 ) = 1) ORDER BY DISPLAY_NAME;
Reference: How to find Software Items created manually (4260597)
In the Administrator UI of v14.0, a new menu (Inventory | Custom Inventory) has been added that allows you to list only items with custom inventory rules.
The above steps can be performed whether the server version is 13.x or 14.0 or later, as long as the device agent is before 14.0 (or later).
Important: We will make every effort to enable you to continue to use items you have already created, but we cannot guarantee that the same KScript will behave the same on agent versions 13.2 and earlier and 14.0 and later.
If you are unable to understand behavior of enabled KScripts after updating to agent version 14.0, it is recommended that disabling KScripts and recreating new ones for 14.0 and later (native).
Since there is no need to consider redirection detours for the new version, in most cases you will simply need to re-incorporate the operations that were originally performed by commands during testing
SELECT
KT1.ENABLED
,KT1.ID
,KT1.NAME
,SP1.SECTION
,SP1.ATTR_VALUE
FROM KBOT KT1
LEFT JOIN KBOT_VERIFY_STEPS SP1 ON SP1.KBOT_ID=KT1.ID
WHERE KT1.TYPE NOT RLIKE 'system|oval|boot' AND SP1.ATTR_VALUE RLIKE 'SYS|HKEY_LOCAL_MACHINE.\SOFTWARE|HKLM.\SOFTWARE|KACE_DEPENDENCY_DIR'
ORDER BY 1 DESC,2,SP1.VERIFY_INDEX,SP1.STEP_INDEX;
Break on Columns: ID,NAME
@echo off
if exist "C:\Windows\SysNative\cmd.exe" goto wowflag
if "%PROCESSOR_ARCHITECTURE%"=="AMD64" goto x64flag
goto end
:wowflag
(Processing for v13.2: Call the command/bat file to be executed from WOW64 mode (32bit). If you want to execute natively, call C:\Windows\SysNative\... )
goto end
:x64flag
(14.0 and above: Call of the command/bat file for native execution. If you want to execute in 32bit, call C:\Windows\Syswow64\...)
goto end
:end
Step "Launch a program..."
SELECT M1.ENABLED,M1.NOTES ,M1.INSTALL_FULL_COMMANDLINE FROM MI M1 WHERE (IFNULL(M1.INSTALL_FULL_COMMANDLINE,'' ) != '' ) ORDER BY 1 DESC;