From the SD Agent log perspective:
First execution:
240418-17:04:07.9048231L|003228|0000062c|SDAgent | |sdjecontainerif.cpp |001226|NOTIFY | Running SD job 1: Office x86 V2 setup32 2016
240418-17:04:44.8505432L|003228|0000062c|SDAgent | |sdjecontainerif.cpp |001402|NOTIFY | SDjob 1 returns: 0 ExitCode: 0
Second execution:
240418-17:35:53.2006301L|001776|000007d0|SDAgent | |sdjecontainerif.cpp |001226|NOTIFY | Running SD job 1: Office Home x86 setup32 2016
240418-17:36:28.1772554L|001776|000007d0|SDAgent | |sdjecontainerif.cpp |001402|NOTIFY | SDjob 1 returns: 0 ExitCode: 0
Third execution:
240418-17:48:46.1552587L|002200|00000230|SDAgent | |sdjecontainerif.cpp |001226|NOTIFY | Running SD job 1: Office Home x86 setup32 2016
240418-17:48:58.7411357L|002200|00000230|SDAgent | |sdjecontainerif.cpp |001402|NOTIFY | SDjob 1 returns: 0 ExitCode: 0
Fourth execution:
250418-11:54:19.9670203L|002784|00000c70|SDAgent | |sdjecontainerif.cpp |001226|NOTIFY | Running SD job 1: Office Home x86 setup32 2016
250418-11:55:01.1621340L|002784|00000c70|SDAgent | |sdjecontainerif.cpp |001402|NOTIFY | SDjob 1 returns: 0 ExitCode: 0
Thus from the SD Agent log perspective, we can tell ITCM is delivering the package and running "setup.exe /s", as you have specified. We can see the package is returning exit code 0, in under a minute in all instances.
What happens if you manually copy the package to the test agent, open a command prompt, and run "setup.exe /s" ?
Does the installer provide any visual feedback as to why it's not installing office?
Does it leave a log file in the temporary files?
From an ITCM perspective, the agent is delivering and executing the package fine, just the package is not resulting in the desired outcome of Office getting installed...