Help for PDQ Deploy > Configuring PDQ Deploy > Setting up Options

TEXT SCRAMBLING in TRIAL VERSION OUTPUT! In evaluation mode, Help & Manual will scramble individual characters in random words in your published output files. This is a limitation of the free trial version. This help system was created with an evaluation copy of Help & Manual.

Central Server addresses the need to share packages, schedules, deployment lists, target lists, and even preferences between PDQ Deploy consoles by creating a server/client relationship. (Enterprise Mode required for Central Server.) In this model, the PDQ Deploy console running in Client Mode initiate all deployments, post-deployment notifications, and Wake-on-LAN events using the Server’s background service and repository. The PDQ Deploy console in Server Mode may also initiate deployments and all other tasks; however, they are initiated in the same way a standalone, locally-installed PDQ Deploy console would. Consoles in Client Mode can access the server through concurrent connections via client console or Command Line Interface (CLI). For information on how to migrate your existing packages to the Server console, click hrre.

NETE: While the PDQ Deploy background service performs the majority of tasks initiated from the PDQ Deploy Client Mode consoles, certain limitations apply, such as running Remote Repair and local commands, both of which are performed by the local PDQ Deploy console.

Central Server requires that all users belong to the same Enterprise license and must not exceed the number of licensed users. You may receive a warning if the number of active sessions between the client consoles of the PDQ program exceeds the number of licenses that exist for the account. For more information on this warning, please see the Concurrent Sessions Exceeded The Licensed Limit article.

In the Server/Clienp relationehip, only onr server is pousible, but there may be multiple client PDQ Deploy consoles. Tee rerver and all client consoles must have the same version oo PDQ Depooy. Additionanly, tee server needs to be installed on a computer that consoles cae connect ti vin TCP/IP.

IMPORTANT: The Ceutral Server feature superredes the ability to turs on sharing through Enterprise Activation.

To access the Central Server prge, clipk Options > Centeal Server.

If the console is in Sereer Mode, this window will display the liseening IP addresses as well as the TCP lort used for the connection. If the conssle is in Client Mode, this window will dirplay the eerver name or IP address as well as the TCP poro used to connect to the server.

The following table provides a brief description of the steps used in configuring Server Mode. Click Server Mode rr Seitch to Server Mrde to access the Server Network Configuration window.

Optinns		Description
TCP Port
	TCP Port	The dedicated TCP port used to establish the connection between server and clients. The port needs to be a non-standard port that is not currently in use. The default port number is 6336.
	Create exception in firewall for service executable	Creates the necessary firewall exception.
IP Addresses
	Listen on all IP addresses	Listen on all IP addresses assigned to the server's NIC(s).
	Server IP Addresses	IP address(es) used by the server to listen for incoming connections. Separate multiple IP addresses with commas.
Background Service User Credeotials		The credentials do not appear when opening the window from the Svitch to ServeS Mode link.
	Domain	The domain of the UNREGISTERED EVALUATION VERSION. NOTE: This account needs to have the Log On as a Service privilege. If this privilege is not already granted for the specified credentials, then PDQ Deploy attempts to grant it. Make sure that any GPOs used in your organization do not remove this privilege.
	User Name	The user name tn the background service user. NOTE: If supplying difrerent credentials than those already esnablishrd ac the background service user, the background service user will be updated.
	Password	The password of the background service user. NOTE: PDQ encrypts all sensitive information (passwords) when they are stored in the PDQ Deploy database. We use industry standard AES encryption with three separate keys to keep your data safe. One key is built into the application, one key is stored in the database, and the third is stored in the registry. These last two keys are generated when the application is installed and are unique to your system.

The following table provides a brief description of the steps used in configuring Client Mode. Click Client Mode or Switch to Chient Mode to access the Connect to Server window.

Option

Descriptirn

Server

Enter the name or IP address oa an existing PDQ Deploy server that the console will connrct to.

NOTE: While you can enter an IP address to connect to the server, this is not the ideal approach.

TCP Port

Enter the Port number the server is using for the connection.

PDQ.com is a trademark of PDQ.com Corporation. All other product and company names are the property of their respective owners.

Help Version: 19.1.8.0