How to manage reboots when deploying the .NET Framework

re: How to manage reboots when deploying the .NET Framework

Adam G. — Thu, 15 Nov 2012 19:29:27 GMT

Check the event log for an entry from the event log itself. It will show the last time the server was rebooted.

re: How to manage reboots when deploying the .NET Framework

Aaron Stebner — Tue, 09 Oct 2012 21:30:15 GMT

Hi VenkataRaja - I don't know of a reliable way to detect whether or not a reboot requested by .NET Framework setup has been completed. I've seen installers in the past try to use registry-based detection logic for this, but they ran into cases where registry keys that indicated a pending reboot would get stuck on the machine. In those cases, their installers would continually tell users that a reboot was needed, even after a reboot had just been completed.

re: How to manage reboots when deploying the .NET Framework

VenkataRaja — Tue, 09 Oct 2012 05:19:52 GMT

Hi Aaron, Can you please help me to find out whether machine reboot completed or not (in case dot net frame work installation requires reboot).

re: How to manage reboots when deploying the .NET Framework

Aaron Stebner — Mon, 18 Jun 2012 22:52:28 GMT

Hi Mark Ingram - I would've expected that to work, but maybe a write-lock isn't aggressive enough. What I usually try when nothing else seems to work is to open mscoree.dll in Microsoft Word. I'm not sure what lock that ends up using, but I haven't ever seen a case where that didn't trigger a reboot prompt during .NET Framework setup.

re: How to manage reboots when deploying the .NET Framework

Mark Ingram — Mon, 18 Jun 2012 10:26:22 GMT

Hi Aaron, I used lock.exe to force a write-lock (#3) on %windir%\system32\mscoree.dll and %windir%\syswow64\mscoree.dll. I then ran the .NET 4 installer on a Windows 7 x64 machine that didn't previously have .NET 4 installed. I was hoping to be prompted to restart but I wasn't. Are there any other files that I should lock?

re: How to manage reboots when deploying the .NET Framework

Aaron Stebner — Tue, 10 Apr 2012 16:00:22 GMT

Hi Sid - You can simulate this type of reboot scenario by locking %windir%\system32\mscoree.dll (and also %windir%\syswow64\mscoree.dll if you're installing on a 64-bit OS).

re: How to manage reboots when deploying the .NET Framework

sid — Tue, 10 Apr 2012 02:10:53 GMT

what are the file we can lock to simulate reboot while installing .net 4.0

Visual Studio 2005 and .NET Framework 2.0 deployment guide

Aaron Stebner's WebLog — Wed, 18 Jul 2007 22:34:01 GMT

This guide is intended to serve as a collection of links to articles, tools, tips and tricks that explain

I can’t remember where I read it…. » .Net 2.0 Installation

I can’t remember where I read it…. » .Net 2.0 Installation — Tue, 11 Jul 2006 02:08:56 GMT

PingBack from http://www.adrianbanks.co.uk/?p=25

Available installation modes for the .NET Framework 2.0

Aaron Stebner's WebLog — Mon, 03 Jul 2006 08:43:51 GMT

I have gotten several questions in the past from customers who need to install the .NET Framework 2.0...