Stop Prompting the user to Reboot

I am trying to deploy the Act Compatibility Tool kit client ( Data Collector) to Win2k clients - I can silent everything but 5 seconds after the package is installed the user is prompted YES or NO to reboot. I want do not the computer to be rebooted and I do not want the user prompted at all.

The reboot prompt can be suppressed setting REBOOTPROMPT= S or Suppress property going with the REBOOT=ReallySuppress (though I havent tried this myself). By setting this property the reboot prompt that is initiated by Windows installer can be avoided. Though I am a bit concerned about the fact that the user in your case is prompted every 5 seconds. Hence I agree with Owen's suggestion of looking for something else like any executable or CA that wants a reboot.
I have one more thing to add, according to me, investigate why the application needs a reboot??? If it really does some configuration settings for which it requires a restart then you must allow it.

ORIGINAL: India_Repackaging
<snip> investigate why the application needs a reboot??? If it really does some configuration settings for which it requires a restart then you must allow it. Why? So many MSIs I see want to reboot because of things like, amongst others:

- using System PATH instead of User
- adding an EXE to the 'Run' registry key and not running it manually after install
- adding an auto-start service and not starting it manually after install
- adding a shortcut to the 'Startup' folder and not launching its target EXE after install

Just about the only reason I would allow a reboot is to replace in-use system files.

ORIGINAL: AngelD
Ian,
You forgot to add services that only start on system startup. I covered those talking about auto-start services, no? What I think you're driving at is kernel driver services, in which case, you're absolutely right, I forgot those.

ORIGINAL: AngelD
Ian,
You forgot to add services that only start on system startup. I covered those talking about auto-start services, no? What I think you're driving at is kernel driver services, in which case, you're absolutely right, I forgot those.
Jupp, those are the once I was referring to (kernel driver).

As it seems that either some custom action from the installation is either not closed after executed or a process launched by a CA remains and trigger this restart prompt event I would try to find out which process is the owner of this event and maybe kill it at the end of your installation.

If there is a requirement of a restart then maybe the user should perform this when prompted to make sure everything will work as aspected.