Downloads:

1,399

Downloads of v 17.2.0.0:

41

Last Update:

5/13/2019

Package Maintainer(s):

Software Author(s):

  • Admin Arsenal

Tags:

arsenal pdq deploy patch deployment tool trial admin

PDQ Deploy (Install)

Downloads:

1,399

Downloads of v 17.2.0.0:

41

Maintainer(s):

Software Author(s):

  • Admin Arsenal

PDQ Deploy (Install)

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

This package was rejected on 6/17/2019. The reviewer chocolatey-ops has listed the following reason(s):

bcurran3 (maintainer) on 26 Apr 2019 17:18:17 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 26 Apr 2019 17:52:08 +00:00:

pdq-deploy has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...

chocolatey-ops (reviewer) on 26 Apr 2019 19:02:01 +00:00:

pdq-deploy has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/2c81daa3b9e2893da2d43dd7a0c509bc for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

gep13 (reviewer) on 08 May 2019 07:54:23 +00:00:

On the local test environment, this pops up a warning about requiring .Net 4.5.2. I think a change to the dependencies in the nuspec is required. Thanks

bcurran3 (maintainer) on 08 May 2019 19:19:17 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 08 May 2019 19:52:56 +00:00:

pdq-deploy has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...

chocolatey-ops (reviewer) on 08 May 2019 21:05:53 +00:00:

pdq-deploy has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/97d21796057ee44d3fc3356079cfe078 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

bcurran3 (maintainer) on 13 May 2019 00:03:50 +00:00:

User 'bcurran3' (maintainer) submitted package.

chocolatey-ops (reviewer) on 13 May 2019 00:35:38 +00:00:

pdq-deploy has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...

chocolatey-ops (reviewer) on 13 May 2019 02:11:42 +00:00:

pdq-deploy has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/a880e85086215c91a9d2469dc4f83df2 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 02 Jun 2019 00:08:09 +00:00:

We've found pdq-deploy v17.2.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:
* Log in to the site and respond to the review comments.
* Resubmit fixes for this version.
* If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

gep13 (reviewer) on 03 Jun 2019 07:18:25 +00:00:

Do you need a testing exemption for this?

chocolatey-ops (reviewer) on 17 Jun 2019 00:12:27 +00:00:

Unfortunately there has not been progress to move pdq-deploy v17.2.0.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

Screenshot of PDQ Deploy

What Can PDQ Deploy Do?

Install MSIs to Multiple Computers

Need to install an MSI? Just create a new PDQ Package and point it to the MSI. If the installation has more than a single MSI file, be sure to check the “Include Entire Directory” checkbox.

Install EXEs to Multiple Computers

Need to install an EXE? All you need to do is verify that the application can be installed silently. (By default MSIs have this ability, but EXEs need to be explicitly told to run silently.) Not every EXE supports this feature, but most do.

The challenge will be to determine the correct method to run it silently. The silent parameter (sometimes called a switch) can be /s or /S, /q or /Q, /quiet, /qn, and a host of other options. Sometimes the installations are case sensitive, so be sure to use exactly what the vendor states is the correct switch.

Ready-to-Deploy Installs in the Package Library

We created the Package Library so that our users wouldn’t have to spend time with every Java or Flash update that comes down the pike. When you are a Pro or Enterprise mode customer you get access to the Package Library you can get common apps that are already in PDQ Packages, and are ready for deploying to all your computers. See the full list of ready-to-go silent installs.

Customize Your Installs

With PDQ Deploy you can install just about any application or patch just by pointing a PDQ Deploy package to an EXE or MSI. You can also make changes to the packages that you downloaded from the Package Library.

What if my Installation has more files than just an MSI or EXE?

Many installations require more than a single install file.

To be sure that these files are used during the installation, be sure to check the “Include Entire Directory” checkbox when you point the PDQ Package to the MSI or EXE.

Memory Requirements: 4 GB

OS Requirements: Windows 7, 8x, 10, or Server (2008x, 2012x, 2016x)

MORE INFO ON WEBSITE

Comparison of PDQ Deploy Free/Pro/Enterprise

SOCIAL MEDIA:
Twitter | YouTube | Linkedin | spiceworks


tools\chocolateyinstall.ps1
#https://link.pdq.com/DownloadLatest?Product=pdqdeploy
$ErrorActionPreference = 'Stop'
$packageName    = 'pdq-deploy'
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$ahkExe         = 'AutoHotKey'
$ahkFile        = "$toolsDir\pdq-deploy_install.ahk"
$url            = 'https://aafiles.blob.core.windows.net/files/PDQDeploy_17_2_0_0_fef0497c-d819-47b9-b115-c8e41f9fad94.zip'
$checksum       = '0739657360FFFCA54B706D92B6175931B1EAE3E319EDB2A68E16C2F686DD0017'
$fileLocation   = "$toolsDir\PDQDeploy.17.2.0.0.exe"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'ZIP' 
  url           = $url
  checksum      = $checksum 
  checksumType  = 'sha256'
}

Install-ChocolateyZipPackage @packageArgs

$packageArgs = @{
  packageName    = $packageName
  fileType       = 'EXE'
  file           = $fileLocation
  silentArgs     = '/S'
  validExitCodes = @(0)
  softwareName   = 'PDQ Deploy*'
}

Start-Process $ahkExe $ahkFile  
Install-ChocolateyInstallPackage @packageArgs
tools\pdq-deploy_install.ahk
#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
 
Loop, 150
; check for .Net message for 5 minutes (2*150=300s)
{
 If WinExist("PDQ Deploy Install")
   {
    WinActivate
    Send !x
   }
  Sleep 2000
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
PDQ Deploy (Trial) (Install) 12.1.0.0 304 Saturday, March 18, 2017 Approved
PDQ Deploy (Trial) (Install) 11.2.0.0 307 Monday, November 14, 2016 Approved

Discussion for the PDQ Deploy (Install) Package

Ground Rules:

  • This discussion is only about PDQ Deploy (Install) and the PDQ Deploy (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or PDQ Deploy (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus