I thought this might have something to do with the clocks changing last Sunday in the UK
we have rebooted the entire environment this weekend the issue still occurs, had anyone else experienced this with vCenter 6.0 U1 on windows with a SQL DB (2014)?
Thanks