Why does Win 2000 servers need to restart after installs ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Why do you have to restart your WIN 2000 servers after software installs ?
 
This is a question you should ask your software supplier.
He installs certain files and makes certain changes to
your registry, and he determines if a reboot is required
or not.
 
Well not only the registry, but also to register certain system files that
were in use and not able to be replaced until a reboot based on the registry
value PendingFileRenameOperations.

--
Doug Allen, Windows 2000 MCSE

This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
 
Indeed. Also to sync (ensure) registry on disk is same registry in memory

Reboot absolutely guarantees registry is re-read and registry synced
Everyone is so used to rebooting after an install, its taken for granted as nequired

You must be a unix person. Unix people hate to reboot anything ever.
They've hated it for decades. (I gave up my hate)
 
Michael said:
Indeed. Also to sync (ensure) registry on disk is same registry in memory.

Reboot absolutely guarantees registry is re-read and registry synced.
Everyone is so used to rebooting after an install, its taken for granted as nequired.

You must be a unix person. Unix people hate to reboot anything ever.
They've hated it for decades. (I gave up my hate).

Novell people, too.

Steve
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top