Good afternoon,
I am wondering if anyone has every seen a behavior where a client fails to execute at a specified remediation time when set to run to close to a Maintenence Window?
Ex. Maintainence Window set to go on client from 9:00 PM - 5 AM.
We have another MSD that doesn't use the MW but is set to run it's remedation schedule at 9:05 PM. we are seeing some clients actually refusing to execute. In the logs we see that it was aware of it earlier in the afternoon but at 9:05 it claims the jb has no valid schedule or future. (FYI, restarting the agent gets it to run)
Has anyone ever seen this or are there any thoughts on this? We saw this on about 12% of a large distribution test.
See log entries below:
At 3:05PM today, WPWKCT022076001 was aware that the OD Vid job was pending:
<event date='Jan 04 15:05:03' severity='4' hostName='WPWKCT022076001' source='CDeliveryPolicy::GetNextWakeup()' module='smfagent.dll' process='AeXNSAgent.exe' pid='124' thread='2940' tickCount='46690334'>
<![CDATA[Policy BR_MSD VidCopy Video({A2B3388C-B133-4DFA-BC8C-49D235FA84E6}) due at: 1/4/2015 9:05:00 PM]]>
</event>
But at 9:05PM, it has had some sort of memory lapse, and says there’s no valid schedule, so doesn’t execute the job…
<event date='Jan 04 21:05:00' severity='4' hostName='WPWKCT022076001' source='CDeliveryPolicy::GetNextWakeup()' module='smfagent.dll' process='AeXNSAgent.exe' pid='124' thread='2940' tickCount='68288345'>
<![CDATA[Policy BR_MSD VidCopy Video({A2B3388C-B133-4DFA-BC8C-49D235FA84E6}) has no valid future scheduled run time (other than logon or startup schedules).]]>
</event>
Our next test will be set to run a bit later than when the MW opens up. Just to try to rule out it is related in any way.
Thanks
DCHAD