Authentication

Top Previous Next

The type of deployment you are using will determine which type of authentication to use.

Current Authentication

Most of the time your current authentication is sufficient. With this setting PDQ Deploy will connect to the target computers in the same way that you would connect through Windows Explorer. Installations will run as LocalSystem which works fine for most installers.

Other Authentication

This authentication type is needed in the following circumstances:

•	The installer needs to refer to network resources. Most often this is needed by a batch (.bat or .cmd) installer that uses files on a server file share.

•	The installer is an MSU update. MSUs can only be installed by an actual administrator account, the LocalSystem account is insufficient.

•	Installer specific needs. Some installers, like MSUs above, require an actual system or domain account in order to run properly.

Active Directory or Local

When using Other Authentication you can use either an Active Directory account or a local administrator account on the target computers. To use a local account enter only the user name (leave out the domain.) Local accounts are the only method that can be used to install to a computer that is not a member of an Active Directory domain.

Logon as Service

When not using your current authentication the user account you specify will be granted the "Logon as Service" privilege on the target computers. This is necessary to ensure that the user's authentication can be used securely from your computer and will be compatible with UAC, which would otherwise prevent any remote deployment software from working.