Unset restart flag

Hi All,

This is a question of interest rather than necessity.

I've just installed Sql Server 2008, now the two pre-requisites on Vista Home Premium are Dot Net 3.5 and Windows Installer 4.5.

After the 4.5 installation it requires a reboot, the Sql server installation won't continue otherwise.

Now the above is just an example. However I was wondering if it is at all possible to dupe the computer into thinking it has been restarted. I don't know how this is tracked on the OS be it a simple registry entry or what.

I'm sure some components definitely require a reboot to work and i'm sure some would work fine without a forced restart.

Any ideas where the "flag" or what not is registered that tracks the requirement for reboot. It'd be interesting to see what effects occur if the computer is fooled.

Extra Note (My Idea, no need to read):
I was thinking there might be workarounds to make such installations work, for example, fool the computer into thinking it's rebooted and then end the services running say the old Windows Installer and Start them Up thus initializing the recently installed version. Might not be that simple but this is why I'd like to see what effects occur if the computers fooled. It could make for a nice little application.

Oh, points, er, well I guess whoever gets me closest to finding where the "Reboot" requirements are set. And modify as such that the computer/installer believes a reboot occurred.

Cheers

Craig
LVL 1
Newt6398Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

drewha1969Commented:
Well, here seems to be a solution for XP, should work on Server too.

http://lifehacker.com/183976/get-rid-of-windows-update-restart-nag

It looks like there is a policy to restart the machine after scheduled installations.  Now as for actually applying the updates without rebooting, someone else will have to chime it...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
matrixnzCommented:
Have a look to see if the registry key exists

HKLM\System\CurrentControlSet\Control\Session Manager
PendingFileRenameOperations

When files are locked and cannot be replaced, the files are added to this key for changing on reboot.

The problem you may have is that the Windows Installer files are locked so they can't be replaced until the system is restarted.  When SQL attempts to install it checks the Windows Installer Version which of course will still be the original version.

Hope that helps.

Cheers
0
Newt6398Author Commented:
Thank you both.  I've split the points even since it was a bit of an open ended question.  Both good pointers ;-)

Cheers

Craig
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Operating Systems

From novice to tech pro — start learning today.

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.