I have a new software package configured, tested and ready to go. It is set to Execute after logon (before desktop loads).

It needs to be delivered the very next time there is a logon. Some computers do if they are on when the assignment is made but if they are off it may take a few reboots to deploy the application.

Is there a way to insure that no matter what the install will happen when the next logon occurs?


3 Comments   [ - ] Hide Comments


  • Can you enable the Wake on LAN. This will ensure the PCs on online and booted. Then the user can logon. Will the Managed Install push out in that scenario? I have never used the "Execute at logon" for I believe it will add to much time from when my users try to logon. I gotta get them logged in asap.
  • I don't have the power to force the computer to be turned off at night or make them log off so WLAN is not a solution.
    I want to be SURE that the app would install if I told them to reboot or SURE if the computer was started after it had been powered off during the initial assignment.
  • I think that the machine needs to checkin once in order to schedule the install at login, but I'm not positive.
Please log in to comment

Answer this question or Comment on this question for clarity


Is the software package able to install with user rights only, or does it need admin rights?
Since a logon is essentially a user process, any application that needs admin rights to install is going to need some form of installation service that is triggered by the user logging on, and this also precludes a network installation, so the source will need to be delivered to the local hard disk.
Answered 08/01/2014 by: EdT
Red Belt

Please log in to comment