Client Automation - All supported versions.
Solution 1:
In the Configuration policy it is possible to specify the bit mode (32 or 64 bit) for Command interpreter :
DSM/Software Delivery/Agent/File Association: Command interpreter bit mode :
Solution 2:
The disadvantage of Solution 1 is that all "command file" SD jobs will be executed in 64 bit mode.
If we need to execute the command interpreter in 64 bit for only one or few SD jobs we could let the cmdBinaryMode to default value (32 bit) and create a .cmd file containing following code :
@echo off
setlocal
SET PROCESS_64=0
SET CPU_64=0
IF DEFINED ProgramFiles(x86) (
SET CPU_64=1
IF NOT %PROCESSOR_ARCHITECTURE% == x86 SET PROCESS_64=1
IF DEFINED PROCESSOR_ARCHITEW6432 SET PROCESS_64=0
)
SET CMD_PATH=%SystemRoot%\system32
IF %CPU_64% EQU 1 (
IF %PROCESS_64% EQU 0 SET CMD_PATH=%SystemRoot%\sysnative
)
%CMD_PATH%\cmd /C script_to_launch_in_64_bit.cmd
endlocal
Replace script_to_launch_in_64_bit.cmd by the command to execute in 64 bit.
Add this script in the SD Package and use it for the SD Procedure.
Remarks: