Experiencing a Chair 2 Keyboard interface issue when attempting to deploy using powershell

Comments

4 comments

  • Luke Nichols

    Chad,

    The issue is probably that you are running the package as the deploy user, so that account is just sitting at that prompt indefinitely.

    You need to change the "Run As" field in the "Options" tab of that step to run as "Logged On User" instead.

    3
    Comment actions Permalink
  • Chad Elliott

    That did it!!!  Thank you so much!!!  I knew it was a Chair 2 Keyboard issue.  Here is my next question: I thought I needed to run as deploy user so it would have local admin rights.  Will running powershell scripts as Logged on User work even if the user is not a local admin?

    1
    Comment actions Permalink
  • Luke Nichols

    The powershell script will run as the logged on user. If it requires administrator rights and the user does not have them then, as far as I know, the script will fail.

    In most cases you should run all Deploy packages as the deploy user, the only time you should change it to Logged on User is if it needs to interact with the user.

    I hope that answers your question.

    2
    Comment actions Permalink
  • Chad Elliott

    Oh!!!! That makes sense.  I wasn't remembering that I am wanting the user to interact with the "script" by clicking on the OK button.  Yea, that makes perfect sense now.  Thanks again!

    1
    Comment actions Permalink

Please sign in to leave a comment.