Will the script be able to continue its job after an automatic restart is forced by a product installer

[Cerena]

I would need to install a product and the product forces the system to do a restart. But even after the restart there are some steps that should be automated. Is it possible for the script to handle the restart and then continue with the other steps.

 

Thank you,

[JLogan3o13]

@Cerena there are a number of ways to do this, yes. It is probably easiest to drop a small file onto the machine, so the script knows where it left off. When you launch your script, always have it check for the existence of that file; if not there, start at the beginning, otherwise begin at "stage 2", etc.

 

[water]

Should the script automatically be started after reboot or do you just need to know if it was started before or after the reboot?

[MilesAhead]

Your program can write to the RunOnce Registry key to start on the next boot.  You could have the command line include a switch to make it easy to know it was started via RunOnce.  It is pretty easy to use.  Plus it is automatically removed by the system.  No need to delete the key manually.

 

https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx?f=255&MSPPError=-2147217396

 

 

[water]

When you search the forum you will find a lot of hits regarding RunOnce.

[jdelaney]

Make everything idempotent, and you don't need to worry where you start the script from...such as validate the registry values added by your installer are already present, or install it.

Another way to autostart it is to copy it into the startup folder (make sure to delete it when your script reaches the end completion:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

Although, the startup requires someone to login.  Another way is to create a scheduled task that runs on startup.

[Cerena]

Should the script automatically be started after reboot or do you just need to know if it was started before or after the reboot?

Script should be started automatically after reboot

[water]

Then I would use the RunOnce approach.