Not a problem.
Unfortunately the error in SolarWinds is less than helpful being fairly generic about a failed dependency.
As there was no firewall involved and only one module, the job engine module, was failing, it wasn't a permissions issues, so I looked at our antivirus logs and found that our access protection was blocking the module from installing. I then had to go into our ePolicy Orchestrator and add an exclusion within our access protection rules for C:\ProgramData\SolarWinds\Agent\Plugins\msvcrt_12.0.21005_x86\vcredist_x86.exe and subfolders. I also ran into another issue trying to get the QoE sensor installed and through the same process had to make another exclusion for C:\ProgramData\SolarWinds\Agent\Plugins\msvcrt_12.0.21005\vcredist_x64.exe and subfolders. Once the policy roll out took place, then the installs/deployments succeeded.