🤘 80 reputation

PDQ_Colby

Administrator

Joined: 4/24/2018

Last seen: Today at 1:28 PM

Activity
  • If you haven't already, please contact support@pdq.com.

  • Zoom is on our list of applications to consider. I have no ETA on when/if it might be added.

  • It hasn't made it through our publishing process yet. It will be available within an hour or two.

  • It sounds like what you are doing should work. The Adobe Reader packages are some of our most popular, and this is the first time I've heard of something like this. Please contact support@pdq.com.

  • @Dusan_Mrozek @liltbrockie

    The Agent has been moved back to beta. I recommend uninstalling it if it is causing problems (Computer --> Uninstall Agent). We are working on bugs like this, but it's going to take a while. If you really need the Agent and wish to attempt to troubleshoot it, please contact support@pdq.com.

  • There are many things that can cause that. Check your antivirus, firewall, and proxy. If none of those are the obvious culprit then please reach out to support@pdq.com.

  • What is the full name of the package you are trying to deploy? If it's the patch, the target has to already have Reader installed. Also, the patches are specific to each train. For example, if the target has DC 2015, you can't deploy the DC 2017 patch to it.

    Another thing you can try is to deploy the "Uninstall Adobe Reader" package, then try again with a package that does not say "patch".

  • I don't think that's possible. It looks like you can manage it with Group Policy though: http://www.classicshell.net/forum/viewtopic.php?f=7&t=3374#p18752

  • Is this what you're after?

    enter image description here

  • 1603 is a generic MSI error that says little more than "something went wrong". If you dig into the Output Log you can usually find a line somewhere in the middle that gives you a better error message.

  • It's definitely not supposed to count backwards 😄

    Please open a ticket with support@pdq.com.

  • I get no results and the successful scan time doesn't update.

    Something weird is going on. Even when I run a Registry Scanner that will never find a match ("Soostem\Magic"), Successful Scan Date is updated. Does Scan Status show any errors for the computer your scanned? What about the Scans page of the Computer window?

  • I'm not sure how you didn't the first time 😄

    When you hit the Image button, it should format everything correctly.

  • I edited your post to fix the images.

  • For those of you who have uninstalled the Agent and are still encountering (Waiting for Agent): did you use "Computer --> Uninstall Agent", or did you remove it a different way? It's important to use the Uninstall Agent menu option because that cleans up the Inventory database.

  • If you haven't already, please update to Deploy 17.2.0.0.

    If that doesn't help, please contact support@pdq.com.

  • If you are trying to copy something like a shortcut to the Public desktop, you can use %PUBLIC%\Desktop as the Target Folder.

  • Oops, sorry about that! We did it this way because we don't currently have a better way to deprecate packages. We intentionally made it fail so people would notice it and switch to the other package. Otherwise it could be years before some people notice it isn't being updated anymore. Unfortunately, we didn't think about how this could wreak havoc on "baseline" packages with a bunch of Nested Package steps. We are now considering other options. One thing that might help you clean up the mess is the Redeploy from Failed Step feature.

  • It looks like you have a ticket in our sales queue currently. Someone from the Sales team will reply to that ticket soon 😃