How do yo handle the practial installation (installing when users potentially logged on)?

Comments

31 comments

  • Espen Dykesteen

    This is exacly what my command step does (i just chose to call a vbs, with the same functions) and just pass the timout as a parameter. I see no benefint in adding all the code in a command step. Booth ways work. But as you point out the main problem is that it cannot be permanently added to an autodeployment :(.

    One way AA could go would be do be able to "pin"/save steps to an autodeployemtn. wahtever step, not just a command step. that would be awsome.

    Or just add a warning step in general, and give the option to "pin"/save this to autodeployments.

    Or both.. :) that would be as good as ... beer?

    0
    Comment actions Permalink

Please sign in to leave a comment.