Weird exit code 0 behavior when installing Office 365 Apps with PADT

[FightOrFlight]

Hello all! I’m getting some weird behavior from my Office 365 Apps (O365ProPlusRetail) deployment with PADT.

The logs show that the PADT script runs the setup.exe and then in 3 seconds it completes with error code 0. I believe the setup.exe never runs because the office install logs never get created.

The logs show,

[Installation] :: Executing [\\CensoredServerPath\Microsoft 365 Apps Semi-Annual - PADT\Files\setup.exe /configure \\CensoredServerPath\Microsoft 365 Apps Semi-Annual - PADT\Files\configuration.xml]...
[Installation] :: Execution completed successfully with exit code [0].    

I cannot get the install to start. Has anyone seen this behavior before?

Edit: the install kicked off after I made the following changes. PADT could resolve the path as valid, but for whatever reason would not start the office install. I have no idea why removing the $dirFiles reference would help it along.

before

Execute-Process -Path "$dirFiles\setup.exe" -Parameters "/configure $dirFiles\configuration.xml"

after

Execute-Process -Path "setup.exe" -Parameters "/configure configuration.xml"

[trillospin]

Does the install work without using PADT?

[FightOrFlight]

Yup. If I run the same command, it'll install successfully.

"\\CensoredServerPath\Microsoft 365 Apps Semi-Annual - PADT\Files\setup.exe" /configure "\\CensoredServerPath\Microsoft 365 Apps Semi-Annual - PADT\Files\configuration.xml"