Services not starting after a reboot

[HereIGoAgain2601]

Hi guys

 

Just wondering if anyone else is noticing strange behaviour with services not starting automatically. We have a number of different VMS running 2012 r2 and 2016, and for the last few months we have noticed that when they are rebooted some automatic startup services don't start. This is affecting things like Azure AD sync and parts of remote app services.

 

Once we go into services and start them manually everything runs fine. Wondering if it's a common issue and down to a windows update as hasn't happened to us before?

 

Only other thing I can think is Sophos Central causing an issue.

 

Thanks

Joel

[Fazza]

Common thing.

 

On our 3 exchange servers lots of the 'Automatic' services are in a stopped state after a reboot - I guess they wont kick in and start until Exchange uses one of the services. We have a server monitoring system in place that lets us know when some services arent running so we can take proactive action etc. so after a reboot we get a 'sea of red' on our monitoring station so we manually start the 'automatic' services just to keep the monitoring system happy!

[nicholab]

We have the same issue here this was after a reboot Azure AD sync will not start. I have tried different user and I did a full server restore to the Friday that it was last working.

[sparkeh]

Same here, Azure AD Sync is an issue too.

 

Also an odd issue where sometimes a VM can't connect to network and needs a reboot.

[nicholab]

Have you checked your switch configuration as I had this issue with a netgear that the configuration had not been saved. After rebooting restating the switch the issue went away.

[HereIGoAgain2601]

Thanks guys, I have tried setting them to delayed startup and that seems to be OK on the Azure AD sync client.

 

Just find it a bit perculiar that some of these servers have been running for years and rebooting services fine until recently. Was wondering if it was due to a dodgey update as there have been a few recently, or if anyone else with sophos was seeing this as that's the only things we have changed. Don't see how it could be a switch issue as it's happening across multiple sites with completely different infrastructure but thanks.