Has anyone successfully used "Execute After Logon"? I'm trying to test something, and cannot seem to get it to work. The same MI works on both "execute on next available" and "while user logged on". Nothing is showing in the logs, and no package is downloaded to %allusersprofile%. Under the machine inventory the MI is listed under "To Install List". What am I missing?

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

2

I get them to work regularly when I select "execute before logon (at machine bootup)" but I've never had anything work with the Execute After Logon...

Answered 04/09/2013 by: GeekSoldier
Red Belt

  • This is how I have installed Java, DigitalPersona, Adobe Flash, Reader, and Air. It all seems to work well when you put the work and testing in up front, but sometimes it has been a pain to get working.
    • Yeah I forgot to mention it also somewhat works with the (at machine bootup) option. The MI requires the user to be logged in. It at least attempts with that option.
  • I think at this point there's no shame in contacting KACE support. If they give you anything else about why most MSIs won't go after login post it up here so we can see why that options is so hard to get working.
Please log in to comment
2

Sometimes the variables are not declared correctly, esp. if no user is logged in.

I suggest to use "hard coded" paths. This usually works.

Answered 04/09/2013 by: Nico_K
Red Belt

  • I should probably clarify when I mentioned %allusersprofile% I meant the path were the MIs are downloaded prior to install %allusersprofile%\dell\kace\downloads. I just got lazy. The install uses no variables. It's a .msp that we push monthly that works with every other option, just not this one.
  • A quick check in Event Viewer might hightlight it for you. Good way to troubleshoot is to wrap that one with a script that display a message to make sure it is being called as expected..
Please log in to comment
1

I created another MI that was just a series of file copies, and that one worked. It looks to just be an issue with this .msp needing to run while logged in. Which I would think "Execute After Logon" would have solved? I'll keep testing.

Answered 04/09/2013 by: dugullett
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity