Help Center

Follow

Integration: PDQ Inventory With PDQ Deploy Version 14+ Requirements

Purpose:
You have PDQ Deploy version 14 or greater and PDQ Inventory installed on the same machine and experience any of the following behaviors (this assumes both products are properly licensed):

Heartbeat schedule trigger is locked in PDQ Deploy schedules:
00.jpg
You receive the following error from PDQ Deploy:
NEWERROR.png
Scan After Deployment is locked in PDQ Deploy’s Deploy Once window, schedules, Package Properties, or Options > Preferences > Deployments :
02.jpg

Resolution:
To Resolve this, PDQ Inventory and PDQ Deploy must be installed on the same computer and running in Central Server or a Local configuration.

Here's a handy integration matrix:

 

PDQ Deploy (server)

PDQ Deploy (client)

PDQ Deploy Local Mode

PDQ Inventory (server)

YES

YES

NO

PDQ Inventory (client)

YES

YES

NO

PDQ Inventory Local Mode

NO

NO

YES

Some examples:

If PDQ Deploy is using Central Server (either Server or Client Mode), PDQ Inventory must also be using Central Server (either Server or Client Mode).

If PDQ Deploy is not using Central Server (Local Mode), PDQ Inventory must also not be using Central Server and must be in Local Mode. NOTE: For many of the features mentioned in this KB, a Pro or Enterprise license is required.

NOTE:
If PDQ Deploy and PDQ Inventory are using Central Server, it does not matter what each is running as (Server or Client). For example, if PDQ Deploy is using Central Server and running as Server, PDQ Inventory can be running as Server or Client and vice-versa.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.