Link to home
Start Free TrialLog in
Avatar of OrenRozen
OrenRozenFlag for Israel

asked on

Windows Server 2008 long restart

On a new HP DL360G5 (2 x CPU + 16GB), installed Windows Server 2008 (as VM on ESXi).

The server 2008 is a DC with the applications SQL 2005 STD and Exchange 2007.

It takes about 10 minutes for the OS to shutdown (stuck on Stopping Services) and about 10 minutes to Startup (Stuck in Applying computer settings).

how can I detect the reason for that behavior?

Thanks.
ASKER CERTIFIED SOLUTION
Avatar of George Sas
George Sas
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You a nlook at your Event Log to determina what are you waiting for... starting and stopping services usually makes entries in Event Log.
are the dns settings correct? could be having network profile issue
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of OrenRozen

ASKER

Thanks Rajith and GeoSs.

Stoping the exchange services before restart / shutdown, reduced the shutdown time to 2 minutes.

Any idea way it takes 10 minutes to load?

Thanks.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
DC should not be installed on VM. It may causing some problems because VM work is scheduled by host in a special manner.
The answers solved the shutdown process.

What about startup? it still takes about 10 minutes. No way to fix that?
You can set your Exchange system services as dependent on AD DS. So you are sure DS are started when Exchange tries to start.
There is no problem with having domain controllers on VMs. The only issue comes with the time. I have clients with their entire server farm in VMs without any issues.

Ensure that the server is using itself for DNS, that can drastically speed things up due to the behaviour of Exchange.

Simon.
Same here , 60% og my setup runs VM... over 100 servers.
Microsoft would not recommend anything that is not Microsoft :)
Hi guys,

Exchange is definitely the problem when running on the DC.

The way I solved it was creating 2 scripts. one for stoping all exchange services and a second for starting all services.

added these scripts to the startup/shutdown option in the GPO.

Shutdown takes about 2 minutes.
startup takes about 10 minutes and ALL services are up.

Thanks for all your help.