yeah that was due to our discussion on the mvp list, however it's not the total answer, setting the time to 720 hours should still not allow you to go to windows update if it is then there's a bug and we need it looked at.
On Wed, Nov 12, 2014 at 11:00 PM, Paul Winstanley <[email protected]> wrote: > Niall, > > This was answered by Matthew Hudson the thread. > > Thanks > Paul > > On Wed, Nov 12, 2014 at 3:21 PM, Paul Winstanley <[email protected]> > wrote: > >> Cheers Niall >> >> On Wed, Nov 12, 2014 at 3:13 PM, Niall Brady <[email protected]> wrote: >> >>> i'll check with the product group and see what they say >>> >>> On Wed, Nov 12, 2014 at 3:32 PM, Paul Winstanley <[email protected]> >>> wrote: >>> >>>> Just added in my observation to this forum thread >>>> >>>> >>>> https://social.technet.microsoft.com/Forums/en-US/56d402ab-b2d7-4d91-be5f-c21dbbe1fa95/scep-definition-updates-trying-to-pull-from-the-internet-poor-behaviour >>>> >>>> I'm currently setting up a 2012 R2 environment and presently port 8530 >>>> is not open to the SUP so no updates are occurring for SCEP. Yesterday the >>>> client updated it's def files from Windows Update. Nothing is set to >>>> fallback to WU in the anti-malware policy. So assuming here that by design >>>> SCEP will fallback to WU after x amount of failures to update. >>>> >>>> Just wanted to know if this is documented somewhere as normal behaviour. >>>> >>>> Cheers >>>> Paul >>>> >>>> >>>> >>>> >>> >>> >> >> > >
