Software Deployment

Why is this trying to run under user's credentials? If these actions were built into the MSI, I believe SMS would run them under full rights. It seems like this is a function being performed by the application itself, which would mean shame on the developers for bad practice.
What are the tasks it is trying to perform?
One thing that might work is to run Filemon/Regmon to see what is being written, and implement those with a custom action after the ForceReboot standard action in the sequence. SMS should run all of this using its elevated account.

this is not a msi. its a legacy setup. I will use filemonto check the file that kicks off on reboot. I am not sure how to start filemon utility when windows starts since this setup program starts the post reboot tasks as soon as the user logs and the users desktop loads only after this program completes it post reboot tasks. Anyways, I will try to figure it out. Let me know if you have suggestions. thanks for your time.

If this is something that happens after every reboot, try checking the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run registry. The application might be putting an entry there, so that it runs every time you log in. Remove it from there and try if it can be run from your MSI before reboot.

it does not a happen every time the machine reboots. it does that the first time the machine is rebooted after the software is installed. will it be under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce??

If the tasks run only after first reboot then it should be in RunOnce.

Check this link out. Might help

http://www.dewassoc.com/support/useful/registry/reg_run_keys.htm

Hi,

For a case like this that performs some tasks after a reboot can only be settled if you can capture what things are being changed or added. I have just encountered this scenario with Filenet Panagon IDM Capture just recently.

I used a lightweight snapshot tool, Installrite. I ran the before the snapshot before I made the reboot and finalized the after snapshot after I have reboot. This could be a time consuming task to find what registries and files were added/modified that can be put on your package but worth an efforts when done right.

It was under RunOnce. I used a wise script (as a wrapper) to install the application and delete the setup's entry under RunOnce. I wrote another wise script that called the .exe that did the post reboot tasks. So far it seems to be working. Thank you'll for your time.