Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

PDQ Deploy Schedule Import

David Linford

April 29, 2021 18:19

I manage a bunch of systems with both PDQ Inventory & Deploy. I'm constantly creating & editing Dynamic Collections in Inventory and Schedules and Packages in Deploy. When I update them in one system, I then export them and import them into my other systems. Everything works seamlessly on this Export / Import model. . .

EXCEPT

When I import new schedules into Deploy it does NOT keep the link to the Packages attached to each scheduled item. Each schedule knows its trigger time, it's collection targets from Inventory. But I have to manually go down the Schedule list and reattach the packages in Deploy. Is there any way the assigned packages can happen with the Export / Import process? Or is there any way to automate this reattaching of packages to each schedule. This reattaching process is both time consuming and error prone.

I'm in 18.4.0.0 Enterprise of both Inventory & Deploy.

Comments

1 comment

Colby Bouma
May 04, 2021 11:03

Package links are intentionally not exported. There is no built-in way to export Schedules with their Package list. https://link.pdq.com/docs-PDQDeploy?manage-schedules.htm#exportimport

I believe this is because Packages are linked to Schedules by ID, and IDs are very likely to be different between systems. You can submit a feature request to support@pdq.com, but be warned it's unlikely to happen any time soon.

If it would work to have all instances be identical, you can copy the database: https://help.pdq.com/hc/en-us/articles/360041094812

I don't know what your environment looks like, but if you have multiple instances due to bandwidth constraints, DFS could be worth looking into: https://www.pdq.com/blog/setting-up-dfs-in-your-environment/

0