Deployments (and scans) not running when console is closed?

Follow

Robert Basil

• May 15, 2018 19:56

I have multiple instances of both Deploy and Inventory running on different machines at different locations due to our network size (but I am the only admin using them).

I'd found that if an windows update is run on the machine that Deploy and Inventory is installed on when that machine restarts the Deploy and Inventory processes restart but no scheduled deployments or scans are being run until the console is opened.

Is this a bug? Running the latest Inventory and Deploy.

 

0

• 

  Robert Basil

  • May 15, 2018 19:57

  The title should say "Scheduled deployments and scans not starting back up after server reboot".

  0

  Comment actions Permalink
• 

  Robert Basil

  • May 15, 2018 20:05

  For example.

   

  The machine running Inventory rebooted for an update on 5/13 After the reboot the service started just fine, but as you can see non Inventory scans were completed until I re-opened the console.

  

  0

  Comment actions Permalink
• 

  Robert Basil

  • May 15, 2018 20:08

  If I log out and back into the machine the deployment schedules continue to run. But if the machine is rebooted nothing scans again until I start up a console window.

   

  0

  Comment actions Permalink
• 

  Stephen Valdinger

  • May 16, 2018 13:07

  This smells like a bug to me. I'd submit this question to support@pdq.com

  0

  Comment actions Permalink

Please sign in to leave a comment.