Friday, June 3, 2011

Multiple reboots

I am always amused by the need for Windows to reboot after making a run-time change. Or what should be a run-time change.

My office is starting our migration to Active Director, so today I booted into Windows to let our PC support folks do their thing to hook up my laptop. I just sat back and watched. It took two reboots to configure Windows to use Active Directory for login. Apparently this is the standard "Windows way" to do it - one reboot to reset the "hostname" (to a standardized name) and another reboot to connect it to the AD domain.

And given how much longer it takes Windows to boot, compared to Linux, it felt like I was waiting around a long time just waiting for Windows to come up, only to watch them reboot again.

I'm shocked by Windows' design. Okay, I can understand how Windows would need to reboot to get the network and all the services configured for a new "hostname". And I can (sort of) see why Windows might need to reboot to change the authentication service to AD.

But why can't these changes be wrapped together into one reboot? Why does Windows always assume a reboot is the right way to apply a change?

(There's more drama with configuring this laptop for Active Directory. But I'll save that for next week.)

3 comments:

  1. Nobody knows how much reboots Windows actually needs, therefore hardened Windows admins make one change at a time "just to be sure".

    ReplyDelete
  2. I believe that it's a myth to have to reboot twice to connect to AD if you change your host/computername, so I omit the first request for reboot and just connect to AD.

    .....let just say I won't be doing it again. Yeap..it needs 2 reboots!

    ReplyDelete
  3. This pertains your interests.

    http://blogs.msdn.com/b/b8/archive/2011/11/14/minimizing-restarts-after-automatic-updating-in-windows-update.aspx

    ReplyDelete

Note: Only a member of this blog may post a comment.

Followers