Windows 2008 R2 updates and reboot too long

Hi

we have problems doing windows update and rebooting my windows server 2008 r2.

it says we have updates to do so we did them and everything seems to be fine but the window seems to be not responsive after a certain time.

I did a log off and see my window change status from installing update #3 to finished and need rebooting.

I log again and windows update ask me to reboot. so I click on restart.

my server initiate the reboot process but stay 1 hour 30 minutes on the window "shutting down windows modules installer service..."

this problem is happening on all my server 2008 r2 and it takes from 1 hour to 1 hour 30 minutes depending which server.

this is not a dns issue because if i do not install updates it reboot in 2 or 3 minutes. this his happening only when we are doing windows updates.

this happen on my private network without internet access and also on my public network with internet access.

if I shutdown the server when it is shutdowning the modules installer service i have to do the updates again. but if i let the server takes 1 hour and more it finally shutdown the module installer service and I can install other updates or stop if there is not anymore updates to do.

these servers are only member server with adminpak for managing my active directory dns, dhcp etc...

can you help me and tell me why windows server 2008 r2 is so buggy for the windows update service.

if I don't have this problem i have to do a checksur.exe to find which kb is corrupted and fix it before continuing my updates.... so complicated with 2008 to keep them up to date...

bluberiAsked:
Who is Participating?
 
bluberiConnect With a Mentor Author Commented:
Hi finally my server was able to shutdown and reboot after 45 minutes after installing windows updates.

it takes me 3 sets of updates to be installed before it returns to reboot with a normal timing.

and I found a series of DCOM event with ID 10009 in the event viewer system event searching for computer name who doesn't exist on this network at all or for computer name who are username like Frank Hebert who is my username and not my computer name.

so for the moment it seems to be a windows update who was really buggy.

0
 
thespiderkeCommented:
Can you give a little bit more information on the machine, is it virtual, multiple network cards??
0
 
bluberiAuthor Commented:
Hi

you are right this is virtual on ESXi vmware.

thanks
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
bluberiAuthor Commented:
Details:

ESXi 4.1.0
Vsphere

my SERVER has one network card on a production vlan
and another on a management vlan

0
 
acpangCommented:
Hit the Enter key a few times to see if it wakes the server up from whatever it's trying to
0
 
bluberiAuthor Commented:
the problem return to normal without help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.