🤘 24 reputation

Brodiemac

Standard

Joined: 11/28/2018

Last seen: Monday at 1:03 PM

Activity
  • You would still use the syntax I mentioned earlier (Application --> Version --> Version Between) but PDQ now gives you two metrics to fill in. You need to be specific with the versions, however. So in your instance, using v14 and v15 won't work since you have versions 14.1.5, 14.1.7, etc. It would have to be something like 14.1.5 and 15.0.1.

  • How about Version --> starts with --> 14

  • Application --> Version --> Version Between

    It's built in already.

  • WSUS

  • What happens when you run it manually from one of those machines using any of the credentials you used to test the deployment?

  • How are you applying the deployment? How are you determining which computers the package is deployed to?

    1. You will need two separate apps for the copies; one for the network share and one for the desktop shortcut.
    2. Create dynamic groups based on the "version" of the desktop shortcut. When you upgrade the applications from v2 to v3, then you can target all computers that have the v2 shortcut for the upgrade.
  • I'm guessing they are waiting for a stable release. It looks like the fixes found during the European bug bounty program has caused some of their own issues as they have released 3 version is the past few days.

  • I have not done a direct upgrade but I can tell you that it works just fine running on Server 2019. I followed the documentation on moving the installation which worked perfectly.

  • Help, possible feature request
  • I see your point. I suppose you could modify the report to include disk size and free space, export it to Excel and just have Excel do the math. It's not elegant but it works.

  • Nevermind, I figured it out.

  • There is already a pre-built report called Logical Disks in PDQ Inventory. Just run that against the pre-built collection of Servers and you should have the info you are looking for.

  • Looking at the pre-built scanner and it shows ** preceding the *.exe. Perhaps trying the ** preceeding your sqlservr.exe?

    Available Wildcards: **\ - Current and All Subdirectories.

  • Is there an option to get a log file on the install?

  • Have you tried doing it based on installed applications?

  • You need to install it silently. /qb is usually used with MSI files. You probably need to use /S.

  • As a 'sledgehammer' approach, you can delete it from PDQ then allow the AD sync to re-add it. That may not solve the underlying problem but it might help in troubleshooting if the problem re-appears.

  • Last night apparently.

  • It's almost entirely seamless. You just need to tweak your packages in PDQ Deploy to link to PDQ Inventory and a few other minor things.