Overview > Credentials

This feature allows you to tailor how packages and their respective steps are executed with respect to credentials.

This is the most common setting. This means that the package will be executed using the credentials specified during deployment. The Deploy User setting will run each step from a non-interactive Windows process.

When to use this setting:
Always unless one of the other settings is explicitly required.

This is the same setting as Deploy User with one important exception. The Windows process running the deployment (or Package Step) will be run in interactive mode.

When to use this setting:
If the installation requires that the logged on user of the target machine needs to see or interact with the deployment BUT the process still requires Administrator rights that logged on users may not have.

Do not use this setting if a process needs to modify specific user settings for the logged on user.

This setting will run the deployment (or package step) as the built in System account for the target computer. It is rare that this setting will need to be used. When it is specified the credentials used for the deployment will connect to the target computer, copy any Install Files or Additional Files specified, then run the actual deployment service using the Local System credentials. At this point if the package requires additional access to network resources (such as a File Server) it will, most likely, fail. This is because a remote system will not grant access to a System account of another machine unless that machine has been specifically granted access.

When to use this setting:
A rare circumstance when an installation requires Local System. Installing certain versions of Lotus Notes for example.

This setting is similar to Deploy User (Interactive) in that it runs in an interactive process. The main difference here is that the process will executed as the logged on user. If the installation requires permissions or access that the logged on user does not have then the deployment will fail or hang.

When you need to deploy an application that is installed PER USER. Also, use this setting if you need to modify the HKEY_CURRENT_USER registry hive for the logged on user or when you need to access user specific settings such as %APPDATA% or the logged on user's User directory. Use this setting if the logged on user needs to provide information for the deployment to succeed (such as a license key, a user defined path, etc.)

Where to set Run As

The list below shows where the Run As can be set in order from lowest to highest precedence.


Preferences > Credentials	This sets the initial "default" setting for how packages and steps are executed. This method will be used on all deployments unless it is specifically overridden by the steps below. It is HIGHLY recommended that the global setting be Run Packages as "Deploy User".
Package Properties	Every package will have a set of Properties that affect all the steps in the package. Changing the Run As value will override the default setting.
Deploy Window	Run As can be changed When you deploy (or schedule a deployment) a package. Changing this value will override the Run As values set in Preferences or the Package Properties.
Package Steps	Any explicit Run As settings for a Package step will supercede all other Run As settings (for the respective step only).