This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Server Lockdown causing very long boot time

We have recently started to try server lockdown. We didn't seem to be having any issues until I needed to reboot a server. What used to take about a minute now takes fifteen to twenty minutes. The delay is in starting (black screen, spinning circle) not shutdown. Tested this on other servers that are locked and the result is the same. Checked lockdown events and there was nothing listed for the day we rebooted.

These are all Windows Server 2019 Hyper-V VMs.

This thread was automatically locked due to age.

Parents

0 Shweta over 3 years ago

Hi JasP

Could you please check under event logs if you see any specific errors?

Shweta

Community Support Engineer | Sophos Technical Support
Are you a Sophos Partner? | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.

The New Home of Sophos Support Videos! - Visit Sophos Techvids
Cancel
Vote Up 0 Vote Down

Cancel
0 JasP over 3 years ago in reply to Shweta

If you mean the 'Events' tab in the Intercept X console, there are no errors.

Also had a look at the Windows system logs and there is nothing in there either.

It all works, just incredibly.... s l o w l y !

I've disabled Lockdown on two of the servers and their boot time has returned to normal.
Cancel
Vote Up 0 Vote Down

Cancel
0 RichardP over 3 years ago in reply to JasP

Windows Events please. We are looking for processes or services failing to load.

RichardP

Program Manager, Support Readiness | CISSP | Sophos Technical Support
Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 JasP over 3 years ago in reply to RichardP

Windows event logs (system and application) show no errors. All the services have started fine.

I did some proper timings for comparison. I timed startup times to get to the windows login prompt screen:
Without Lockdown, 160 seconds (2 minutes 40 seconds)
With Lockdown, 490 seconds (8 minutes 10 seconds)

Not quite as bad as I initially thought but it's over 3 times slower. The three servers I have tried this on all have the same issue. They are all the same OS but are pretty different in terms of software installed.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 JasP over 3 years ago in reply to RichardP

Windows event logs (system and application) show no errors. All the services have started fine.

I did some proper timings for comparison. I timed startup times to get to the windows login prompt screen:
Without Lockdown, 160 seconds (2 minutes 40 seconds)
With Lockdown, 490 seconds (8 minutes 10 seconds)

Not quite as bad as I initially thought but it's over 3 times slower. The three servers I have tried this on all have the same issue. They are all the same OS but are pretty different in terms of software installed.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 RichardP over 3 years ago in reply to JasP

what do you have in your startup keys? Are there programs that run at startup? Any scripts?

RichardP

Program Manager, Support Readiness | CISSP | Sophos Technical Support
Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 JasP over 3 years ago in reply to RichardP

There is only program in startup, Open Shell (which is an updated version of Classic Shell). The only part of that program we have installed is the bit that replaces the Start menu with an interface that is like the Windows 7 Start menu.
Cancel
Vote Up 0 Vote Down

Cancel