UAC Prompt issues using Prism Deploy

When deploying certain tasks to an environment that has UAC turned on, some problems may come up such as tasks failing with an error code of 5200.  This occurs because the task needs to elevate using the UAC and cannot do so.

Prism package tasks should work with any level of UAC, but Prism script tasks and command tasks will need additional configuration to make sure they bypass the prompts. 

To do this, you will need to make sure that the task is set to “Run as the Local System account” within the task properties under the “Execution” tab.  Once this is set, the tasks should deploy successfully. 

As an additional note, command tasks can be ran either "Attended" or "Unattended", but script tasks need to be run unattended for them to work in an environment with UAC turned on.