🤘 5 reputation



Joined: 5/3/2018

Last seen: 7/24/2019

  • Thanks Colby, grabbed the updated package last week.

  • CutePDF (w/Ghostscript) package needs updating
  • Adobe Air
  • Same here. Too many Old Fashions during last week's webcast perhaps? 😃

  • They mentioned in last Thursday's webcast that they are trying to see if it's possible to make an OpenJDK 11 package that they could add to the library. https://youtu.be/VzNv4lgfXZ4

  • The PDQ central server will keep on doing all its work (inventory, schedules, deployments, etc.) without any consoles open on your server or your workstations. Awesome product!

  • I feel your pain. We use ManageEngine AssetExplorer, ServiceDesk, OpManager and EventlogAnalyzer and I hate all of them. They only thing they have going for them is that they are cheap, but the money you spend on staff keeping them running and upgraded offsets those savings. I'm looking for an affordable alternative to ELA right now and one of my co-workers wants to replace ServiceDesk/AssetExplorer. We're a much smaller shop than you but have MSSQL running on many servers so would not be averse to switching over to it instead of SQLite.

  • Deploy - Package Library Requests - Windows 10 Service Stack Updates (SSU)
  • Maybe not detailed enough for you but I just have a simple report that looks at all the machines that belong to (Old) collections in PDQ Inventory. Doesn't show me the versions but it does show me which machines don't have the latest version of an app installed. I had to filter out .NET collections though because I didn't want to see those since we aren't running the latest version of .NET everywhere yet.

    enter image description here

  • There's probably a more elegant solution but the quick and dirty one I created a while back looks like this.

  • For this reboot package under Properties you could try unchecking Offline Settings -> Retry Queue so that it doesn't use the settings from Preferences and then leave the "Put offline targets in Retry Queue" unchecked. No need to retry offline machines. If they were offline then they've obviously already been rebooted. :-)

  • Here's the one I use. I created my own variable for SEP. If you want servers too just delete that last filter.

    @(AppNameSymantecEndpointProtection) = Symantec Endpoint Protection

  • We have PDQ Deploy and Inventory running on the same 2012R2 WSUS server. No issues here.

  • Collection Library
  • I followed the blog instructions and everything worked fine for me. Except Intel's test tool choking on some of our older HP machines. :D

  • Win10 1703 KB4055254
  • Awesome, thanks! It's worked on most machines I've tested it on so far. A few are getting an error from the detection tool, I believe it's because the hardware isn't found. We have some older machines out there. But a few have also got this PowerShell error.

    Invoke-Expression : Exception calling "Load" with "1" argument(s): "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
    At C:\WINDOWS\AdminArsenal\PDQDeployRunner\service-1\exec\Error Handling Wrapper.ps1:39 char:1
    + Invoke-Expression "& '.\$($Parameters[0])' $($Parameters[1])"
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Invoke-Expression], MethodInvocationException
        + FullyQualifiedErrorId : DotNetMethodException,Microsoft.PowerShell.Commands.InvokeExpressionCommand

  • Intel® Management Engine Critical Firmware Update (Intel SA-00086)
  • PDQ Deploy bug?
  • Windows 7 Pro x64.

    I resolved it. I'm running PDQ products under my admin account while logged into my non-admin desktop profile. Logged into my admin profile, changed default browser to Chrome and then the links opened with Chrome. But now Chrome doesn't work running under a different account than currently logged into. So I may have to switch it back to IE anyway.

    Stephen, also haven't seen that NTUSER.DAT locking issue since that one time so I now have PDQ Inventory scanning all of our machines. I still believe it was SEP causing the problem. Thanks for your feedback.