Software Deployment

Reboots are triggered for a reason: you need to find out why and then act accordingly.

If files need to be updated but are in use during an installation, the choice is either stop the process which is holding open those files or wait until after a reboot and replace them on system start-up. Some vendor installations are pretty dumb, in that they request a reboot simply because:
- they have installed a service and rely on the reboot to start that service, or
- they placed a shortcut in the Startup folder (or add to the 'Run' registry key), or
- they added their app's target folder to the System path

Run the install with a verbose log. That will show why the system 'requires' a reboot.

The following line should be added to your config.xml if it is not already present

<Setting Id="SETUP_REBOOT" Value="Never" />

Regards,

Spartacus

hi spartacus
buddy it is worked only on those machien which have already open any office document like word,excel, ppt etc. but which have not open any office document those machines has reboot.

what should i do?

what should i do?Exactly the same as I advised before. Log the install and find out WHY the reboot is required and act accordingly.

advertais log show this

"The program for advertisement "UDP2008D" ("UDP0004E" - "2007") returned an exit code of "1641"(""), which indicates the operation was successful but a restart of the system is required for the operation to be complete. A status message indicating final success will be sent after the system has been restarted.
Systems Management Server (SMS) determines status for each program it executes. Any program dependencies will not be executed until after the restart occurs. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status."

do uhave any idea?