The New Installer Library: Ready-to-Run Installers For PDQ Deploy!

Posted by Shane Corellian on Mon, Jun 18, 2012

My favorite feature of PDQ Deploy 2.0 is the Installer Library.

Installer Library

The Installer Library will soon (Summer 2012) move to a cost subscription model. Right now it's no-cost (while we iron out the wrinkles).

The Installer Library provides "Pre-sliced, rust-proof, easy-to-handle, low-calorie..." Installers for common applications and it is available within PDQ Deploy. You do need to have a connection to the internet to view and download available Installers.

You will notice that the Installers that you download will be placed in your Installers folder. But where are the actual Installation Files stored? The Setup.exe? The MSI files? They are copied to the Repository, which is another new feature with PDQ Deploy.

The Repository

The Repository is, by default, placed in the All Users Documents folder. Go to your Preferences and you select the Repository panel and you will see what I mean.

Repository

Let's open up one of the Installers that we downloaded from the Library.

.NET 4 Installer

Now, you're ready to deploy Microsoft .NET 4 to your target computers.

See this video to see an example of deploying Adobe Flash Plugin, which was downloaded from the Installer Library.

Initially we are going to have a few popular Installers ready to go. While we always intend on having a few common Installers available the majority of the Installers will ultimately be available with a subscription. We are still working the subscription thing out.

A few words about the Repository. You do not HAVE to store your install files here. You must have, however, a valid directory (preferably a network share) that you define for your Repository. Any installer that is downloaded from the Library will be placed in this directory. Obviously to change the location of your repository go to File > Preferences. Select Repository. Change the path to a valid location. Please note that the credentials used by PDQ Deploy (PDQDeploy service (AKA Backgound Service) and your Deployment user(s)) must have the necessary rights to read and copy files from the Repository.

If you can't access the Installer Library you may need to provide your Proxy credentials. You can do that via the Preferences window. Just select Proxy Server panel and enter your credentials in the two fields.

Let us know what you think. From your Help menu select Submit Feedback. Please include your email address if you want us to write back with follow up questions or answers.

Refer to this post about the Installer Library and the $(Repository)

Tags: PDQ Deploy, Installer Library, Repository, Adobe Flash

Comments

This is a cool idea. A pre-ready deployment of most common installs. Would have loved it if it had been available a lot earlier. Now I already have "my library" built with my most common installs. But I think it will be great for the newcomers.

How is this "subscription cost" thing going to work? For example, I mentioned I already have "my library" built so what would be the benefit for me to sign up for this?

Posted @ Thursday, June 28, 2012 8:16 AM by jonathan plaza

Thanks for your words.

We are still working out the details of the subscription. The Installer Library is not intended to replace your current installers. The purpose is to provide ready-to-go installers for commonly used applications (as well as updates to those applications) so that you don't have to always stay on top of this update or that update. Of course, as you noted, this will also be great for newcomers who may be new to the concept of Software Deployment.

It is fully anticipated that the Installer Library will supplement, not replace, existing installers. You will always be able to build your own Installers.

Posted @ Thursday, June 28, 2012 11:36 AM by Shane Corellian

Is there a way for me to request application to be added to the installer library?

Posted @ Thursday, June 28, 2012 2:37 PM by Curtis Allworth

Hi Curtis. Yes, if you want to create or vote on a request for the Installer Library please visit our Installer Library Requests forum.

Posted @ Thursday, June 28, 2012 5:59 PM by Shane Corellian

Shane, are there plans for an internal Installer Library?

We currently only have two licenses in one office but are hoping to expand that considerably across two separate teams. It would be a big time saver to have a central internal library of scripts that both teams can utilise.

Posted @ Saturday, June 30, 2012 1:15 AM by Joel Johnson

I just tested one of these, very nice! However, are you going to create and de-installer set to remove the application that was deployed?

Thanks

Posted @ Friday, July 06, 2012 4:56 PM by Adrian Salas

Yes, we do have plans for an internal installer library. In the meantime, you can have both teams have their Repository (see the Installer Library Part II blog) set to a share on a file server. Have one team download the files from the Installer library. You can then export your installers (File > Export) and the other team simply imports (File > Import). It's a few extra steps but it be very helpful especially for custom installers.

Posted @ Tuesday, July 10, 2012 12:16 PM by Shane Corellian

Thanks Adrian. We do have some separate uninstall "installers" in the library. That's a great idea to bundle the installers and uninstallers together though. I'll add this to our roadmap.

Posted @ Tuesday, July 10, 2012 12:20 PM by Shane Corellian

Follow Us

Subscribe by Email

Sys Admin Sites We Like

Most Popular Posts

Latest Posts

Posts by Month

Browse by Tag