Summer is winding down and school is back in session for many people across the country. So, if you were busy fitting in a last-minute vacation, taking kids school shopping, or gearing back up for the next quarter and missed out on the webcast last week, no need to fret. We've got you covered so you won't miss a thing. You can watch the whole webcast below or just skim through this post to see what might apply to you in your environment.
We are using Central Server with 6 humans plus 1 service account. We use the service account as our default deploy/scan user and this account also runs the background service. Each person and the service account are console users and they each have their own license, but I’m curious if we’re being redundant with giving the service account a license?
I have a PDQ Deploy job that runs multiple packages with ‘Include Entire Directory’ that are all in the same folder. Does copy run on every package or is there any check? If not, how do I arrange this to copy just once?
Is there a way to produce reports for auditors proving that our patch game is on point? I have tried showing a deployment schedule.
I love the “Run Command”’ in Inventory, but it looks like it has a limit of 16 concurrent sessions. Is there a way to modify the limit like we have with Deploy and it’s Concurrent Target Limits under Performance? Before you say use Deploy, the Run Command seems to be the only way I can get LiteTouch.vbs (MDT) to kick off correctly.
Will Inventory eventually have the ability to automatically scan the registry for software Product Keys? If not, why?
Windows updates in PDQ is great, but I’m wondering if you will start adding manual Win 10 upgrades as a part of Deploy?
Can PDQ Deploy automatically or by schedule, scan a Spiceworks group for devices that have been added/removed?
Brook is 100% definitely a human and enjoys human activities such as sleeping, correctly solving captchas, and eating food for energy. He's been sentient a sysadmin for ten years.