1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

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.

Scheduled Deployments Don't Queue

Avatar
Brett Purcell

I've noticed an issue where scheduled deployments will kick off on a machine even if another deployment is already running. Any deployments that are triggered manually will queue with others and wait until one deployment finishes before starting the next, but one triggered by a schedule will start immediately, usually resulting in an MSI 1618 error because there's already an installation in progress. Is there any way around this?

0

Comments

3 comments
Date Votes
  • Avatar
    Colby Bouma

    I am unable to reproduce that behavior. The deployments queue properly for me.

    1. What is the version number of Deploy and Inventory that you have installed?
    2. Which mode are Deploy and Inventory running in? (Server, Client, Local, etc.)
    3. Is the running deployment a different package from the one in the schedule?
    4. Where is the schedule pulling its targets from? (Inventory Collection, Target List, static targets in the schedule itself, etc.)
    5. Are the targets formatted the same in each deployment? (FQDN, short name, IP, etc.)
    0
  • Avatar
    Brett Purcell
    1. We're on Deploy 17.1.0.0 and Inventory 16.5.0.0.
    2. They're both running on a central server.
    3. It is a different package.
    4. The schedule is pulling from a dynamic Inventory collection and triggers on a heartbeat.
    5. It looks like the schedule is using a fqdn and the other deployment is just using the hostname.
    0
  • Avatar
    Colby Bouma

    Is this still an issue for you in Deploy 17.2.0.0 and Inventory 17.1.0.0?

    0