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.

Switching to Inventory and heartbeat.

So I have a dozen schedules deploying via a link to different OU's.  We just purchased PDQ Inventory and I am going to switch everything to Heartbeat and just have one schedule for all of our packages.  The question is what happens when I create a new schedule with all the existing packages most of which have already deployed under the old schedules.

Will it re-install or will it recognize that it is already installed and move on?

Items currently being deployed are:

Adobe Air

Flash NPAPI

Flash All IE

Reader XI

Shocwave

Java 8

0

Comments

2 comments
Date Votes
  • To answer your question Jim, new schedules will not have a deployment history so if you're thinking of running everything under one schedule that's fine but I'd add new packages to the "master schedule" when new versions come out.  The other way you could set this up in transition is to "link" your schedules to the prebuilt collections in PDQ Inventory that we keep up to date.  This is an Enterprise feature but then each application would have a collection and deployment package and when the new packages are released, we also update the collections for you.

    0
  • Perfect, a transition is easy enough.  I will hold off on linking to the Inventory collections, we are pretty set in our ways of testing pretty thoroughly first.

    0