We recently updated all 3 of our SharePoint farms, dev, prod, and our dmz servers with the August 2017 CU and then found out our content deployment jobs were failing to two of our forward facing SharePoint farms. The only thing that seemed to get the deployment jobs to stop running was to log on to each of my remote SharePoint servers and using powershell to stop the owstimer process. Once this was done the content deployment jobs would report back they had completed successfully but no content was actually deployed. We opened a ticket with Microsoft to get some assistance with the issue but we were still coming up short. Knowing that there was a process or timer job that wasn't firing like it was supposed to I ran this script and all of the sudden the content jobs started working properly.
$farm = Get-SPFarm
$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
if ($disabledTimers -ne $null)
{
foreach ($timer in $disabledTimers)
{
$timer.Provision()
$timer.Start()
}
}
