Powershell: Get-Help

Posted by Kris Powell

Sep 18, 2014 1:48:00 PM

kris_resizedFrom the results of my last Powershell blog post (Get-Command and Get-Member), we should have a list of commands (cmdlets, aliases, etc).

But, how do we know what each cmdlet does?  Or, what if we know how a command works but want to see some examples?

We need some more information about how to use those commands in more detail.  Let’s learn more about the Get-Member cmdlet that we introduced last time by utilizing the tools built into Powershell.


Get-Help displays detailed information about how to use a command and any examples that may exist.

The basic syntax is pretty simple and straightforward.

Get-Help <cmdlet>

In order to find out more about the Get-Member cmdlet, we type:

Get-Help Get-Member

This will give us some basic syntax and usage information about Get-Member as well as a brief description.  Let’s introduce some of the parameters that give us even more information about the cmdlet that you’d like to know more about.

Get-Help <cmdlet> -Examples

This will show usage examples for the cmdlet

Get-Help <cmdlet> -Detailed

This will show more detailed information than the basic syntax

Get-Help <cmdlet> -Full

This shows the entire help file relating to the cmdlet, including details/examples.

Get-Help <cmdlet> -ShowWindow

This will show the full help file for a cmdlet in a new window.  It includes a search box and a settings button to help you configure which information you want displayed.

Get-Help <cmdlet> -Online

This will pull up the online help files for the cmdlet.

Note: If you find that you’re help files seem to be lacking, it’s possible that they’re not fully installed or up-to-date.  In that case, run Powershell as an Administrator and type the cmdlet, Update-Help and it will update all the associated help files.)

Read More

Topics: powershell

PDQ Deploy 3.2 Beta 3 (Release Candidate)

Posted by Shane Corellian

Sep 12, 2014 3:50:30 PM

PDQ Deploy Beta 3.2Dress rehearsal is just about over, my friends. We have just released the final (we hope) beta for the new PDQ Deploy 3.2.

If you haven't heard yet, the big news is that we have added Auto Deployments from the Package Library! Yep, this means you can select packages that you want to have automatically deployed as new versions become available. This is the ultimate in Set It and Forget It.

Watch these videos to see how Auto Deployments work.

This version also follows PDQ Deploy Schedules as they leave monogamy and delve into open relationships. OK, that may be a tad too subtle. PDQ Deploy schedules can now be attached to more than one package at a time. This means that one schedule can deploy multiple packages to the same target machines.

Here is a video showing how this can be done.

Read More

PowerShell: Get-Command and Get-Member

Posted by Kris Powell

Sep 11, 2014 9:10:00 AM


Today, I want to show you a couple great cmdlets that can really strengthen your understanding of 

PowerShell: Get-Command and Get-Member.


Get-Command will list all commands that are installed on the computer, including cmdlets, aliases, functions, etc.

Try it out. The results should look something like this:



There’s a lot of output on the screen, so we can clean this up a little bit to make it easier to read.

Let’s say we just want the name of the commands. We’re going to select only one object property by piping the results of Get-Command and selecting the property that we want to see.

Get-Command | Select-Object Nameget-command select-object name

But, how do we know which object properties exist to select and sort? We’re going to introduce another command today called Get-Member.  


Get-Member tells us about the Properties and Methods of an object.

The easiest way to use it is to pipe in an object that you want to know more about.

Get-Command | Get-Memberget-command get-member

We can see that there are many properties for Get-Command that we can use to sort and view.  Let’s use CommandType and Name.

Get-Command | Select-Object CommandType, Name get-command select-object commandtype name

You should be able to look at that list and find any cmdlet that’s installed that you can use.

In the next blog, we will go over another tool that will help get more detailed information about each cmdlet from within PowerShell itself.

In the meantime, here is more help about Get-Command and Get-Member from Microsoft's Technet:



Read More

Topics: powershell

Lunch with the PDQ Developers

Posted by Shawn Anderson

Sep 9, 2014 12:26:41 PM

Dev-Fix-bwWe've been holding formal training at our offices now for several months. One of the perks of onsite training is the ability to rub shoulders with our crew. 

We've decided to do a little more. Each training class will now have lunch with the developers. No support guys. No marketing. Just our attendees and the guys who are writing the code (Adam, Chase, and Zach). Ask any question. Plead, rant, extort, beg, criticize, or exploit. You have 'em for an hour. 

Is there a feature that you are dying to have? Ask 'em. Are you curious about why a feature was implemented a certain way? Maybe you just want to know if programmers have social skills (ours do, by the way). 

For more information on our onsite training click here

We also offer private online training and free webinars, click here to view all available training options

Read More

Topics: Admin Arsenal

Auto Deployment - The Feature That Keeps On Giving

Posted by Shane Corellian

Sep 4, 2014 3:20:37 PM

PDQ_Deploy_Beta_3-2We just released the second public beta of PDQ Deploy 3.2. We made some changes to Auto Deployments (an Enterprise mode feature) - particularly in setting them up - that beta 1 users will notice.

The biggest change is related to the Approval Policy settings. There is now a global default setting in Preferences > Package Library.

What is the Approval Policy?

This is a setting that determines when new versions of packages are approved for auto deployments. Let's say you create an Auto Deployment Package for Mozilla Firefox. The current version is 32.0. When the next version is added to the package library (for example, version 33.0) the Approval settings are used to let PDQ Deploy know when it is safe to automatically deploy the new version. All new versions must be approved before they can be deployed. For those who want to Set It and Forget It you can specify when to automatically approve new versions.


Setting Up a Package for Auto Deployment

Go to your Package Library, then select the package(s) you want to have automatically deployed. Push the Add Auto Deployment button. You'll be presented with two options. Create a New Schedule or Use Existing Schedule. In the example below will create a new schedule. 



Can I Change the Approval Settings for a Specific Auto Deployment Package?

Yes. If you want to change the Approval settings (remember the Approval initial settings are whatever your default configuration is in Preferences) select the package under Auto Deployment Packages and go to the Schedules tab. Highlight the schedule and click the Change link in the right side panel (you can also right click the schedule and choose the Change Approval Policy option). Select the Approval policy that you want for this schedule. ***Note*** The deployment policy is maintained per package per schedule. This means you can have one schedule that immediately approves a new package version (perhaps for test machines) and then another schedule which deploys to the rest of your target machines that gets approved in 3 days (or manually or whatever).


If you want to change the package version that is currently being used for Auto Deployment you can click the Change link under Current Version. If you choose an older version the Approval setting (for this schedule / package) will be set to Manual. Also note that you may need to uninstall the later version on target machines that have already had the new version deployed.

The video below walks you through setting up an Auto Deployment for Adobe Flash for IE.



Read More

Topics: beta

Auto Deployment and Proxy Servers

Posted by Shane Corellian

Aug 27, 2014 3:30:00 PM

To facilitate the new Auto Deployment feature in PDQ Deploy 3.2 we had to modify how we handle proxy servers.

PDQ Deploy now connects to the Package Library using the background service user account. If you use the same account to open the PDQ Deploy console AND to run the Background Service then you're probably going to be fine. The real gotcha is if you use a different account to run the Background Service.

Why would this be the case? Well, most environments have a proxy server. Generally, proxy server configurations are usually pushed down --via a User level GPO-- to your Windows systems when a user logs on. If the user account that runs the Background Service has never logged on to your console system then there is not proxy information for PDQ Deploy to use. In these cases you have one of two options:

  1. Log on (once) to your console machine using the background service credentials. If your proxy information is populated via a GPO or a login script then you should be OK. After logging in you can log out and log back in using your normal account. 
  2. Specify the proxy information in the Proxy panel in your Preferences window of PDQ Deploy.

Look at the screenshots below. One shows the Background Service credentials in the PDQ Deploy Preferences window. You can see that the user account deadwood.local\Al.Swearengen is used to run the Background Service. 



Take a look at the running processes screenshot. You can see the PDQDeployConsole.exe (the console) is running under the Quintana account (because Quintana is the account logged into Windows). The PDQDeployService.exe (Background Service) is running as Al.Swearengen.


When the Console is started PDQ Deploy will attempt to connect to the internet (for the Package Library) as Al.Swearengen. If it can't connect then it would attempt (in this case) as Quintana (the account running the Console). This doesn't solve the problem, however, of connecting to the Package Library when no one is logged onto the console. In this case if the background service user (Al.Swearengen) doesn't have proxy information defined then the Package Library won't be able to be accessed.

If you find yourself in this position then choose one of the options listed above. If you want to simply hard-code the proxy information into PDQ Deploy then it would look something like this:



This setting tells PDQ Deploy to always use this proxy info and to ignore proxy settings in the Control Panel of Windows.

I hope this helps head off any proxy related problems you may encounter as you upgrade to PDQ Deploy 3.2.



Read More

Topics: pdq deploy

Scheduling Improvements and Pints

Posted by Shawn Anderson

Aug 22, 2014 1:39:00 PM

What do drastic improvements to our scheduling and beer pints / shot glasses have in common? 

Besides nothing, they have in common the fact that if you help us describe our improvements we will send you a really cool etched beer glass, shot glass (or shirt, for our non-drinking users). Each product has our PDQ Deploy logo on it.Admin Arsenal PDQ Deploy Shotglasses and beer pint


We've been racking our brains on the best way to both describe and market our scheduling improvements and we're drawing a blank. So, here is a description.

Packages and Schedules are now independent of each other.

Earlier versions of PDQ Deploy allowed you to create a schedule which would deploy a package. You could have multiple schedules, but each schedule could only deploy a single package. If you wanted to deploy multiple packages in the same schedule you needed to use nesting (which you can still do). However, Nesting packages JUST to have them in the same schedule isn't really what nesting is for. So, we've made it easier. 

In PDQ Deploy 3.2 a single schedule may contain multiple packages. We call this attached and detached packages (still with me?)

But wait... there's more

One of the very cool features of these 'independent schedules' is the ability to easily replace old packages with updated ones. 

For instance, let's say that you had a schedule that deployed Firefox 30.0. Now that Firefox 31.0 is out, you could replace the old package with the new updated version. You do not need to do anything else. The schedule remains in place. 

Multiple Packages in a Schedule

As mentioned above you can now have multiple packages in a schedule. Need to update 2 of the 5 packages, just detach and attach as needed. The schedule remains the same. 

Enter: You

OK - now that we've explained the process here is our marketing dilemma. How do we encapsulate that into a single sentence? All of the Marketing for Dummies books that we've read frown on marketing lines that are more than five paragraphs in length. 

Let us know your thoughts by commenting below, or you can tweet your suggestions to @admarsenal #pdqdeploy, and you could win your choice of a beer glass, shot glass or PDQ Polo. 

A Video is Worth a Thousand Blogs

See Shane and Lex explain as only they can what we are currently calling "Independent Schedules". 


Read More

Automatically Deploying Java, Flash, and other Patches

Posted by Shawn Anderson

Aug 21, 2014 9:50:00 AM

PDQ_Deploy_Beta_3-2PDQ Deploy 3.2 introduces a commonly requested feature for Enterprise mode users; Auto Deployment. As the name implies, PDQ Deploy will now have the ability to "set it and forget it" when it comes to packages that we host in the Package Library.

Admins familiar with our Package Library will notice a few interface changes. 

Import vs. Auto Deployment

From the Package Library you have two options for pulling down packages: Import and Auto Deployment.

Import replaces the "Download" button in earlier versions of PDQ Deploy. Importing a package does the same thing; it copies the package from our Package Library into your PDQ Console where you can deploy the package. All of the same features still exist.

The big change is the Auto Deployment feature. You can now select one or more packages and click the Set Auto Deployment button (or link) and you will be presented with a dialog about setting up your auto deployment. 

Auto Deployment Options


By default you will be auto deploying the latest version of the selected package(s). If you select only a single package you can change the version to be auto deployed to an older version if you choose.

Approval Policy for future versions

This setting is all about the future. When a new release of the respective packages becomes available you are telling Auto Deployment how long to wait before approving the new version. You can select to automatic approval and set the duration in days and hours for the deployment. You can also set the manual option, which will require future action on your part to specify to PDQ Deploy's Auto Deployment when to approve the new version. This option is handy if you want to double (or triple) check that a patch will not break your environment.


You then have the option to create a new schedule for your auto deployment, or you can attach the package(s) to an existing schedule, if one exists. When a new version of a scheduled Auto Deployment package is approved the older package is replaced in the schedule. This means you won't have to create or modify a schedule when a new version is approved.

You are then able to select the target computers for your future deployments. The video below demonstrates this by Shane and Lex linking to PDQ Inventory.



Read More

Topics: beta, Admin Arsenal, Announcements

Uninstall Bad Microsoft Patches Using PDQ Deploy

Posted by Shane Corellian

Aug 18, 2014 4:13:00 PM

table_flipMicrosoft has advised users (MS14-045) that have installed certain patches released last week (Patch Tuesday) to uninstall the patches. Sunday night the offending patches were made unavailable for download. The rogue patches can cause Blue Screen problem in Windows 7 (and Black Screen in Windows 8 and 8.1) and can potentially brick your system if fonts are modified or certain applications are installed. Additionally, the patches can create a vulnerability. Hackers with valid logon credentials can exploit this vulnerability. Read up on this botched patch here.

The patches affected are:

  • KB2982791
  • KB2970228
  • KB2975719
  • KB2975331

You can use PDQ Deploy to remove these patches. We have placed two packages in the Package Library. The only difference between the two packages is that one will initiate a reboot after the deployment. Go ahead and download the package "Uninstall MS Black Tuesday Patches AUG. 2014".

If you have automatic updates set on your Windows computers that successfully received the update between Tuesday and Sunday it would be in your best interest to uninstall this offending patch even if you are not currently experiencing issues, issues may not be apparent until after a reboot or even a couple reboots.

See the Microsoft Security Bulletin

New in the PDQ package library is an uninstall package you can deploy to all Windows machines to quickly and silently remove the Microsoft patch with PDQ Deploy. Normally uninstall packages are available only to Enterprise Mode licenses, but this package will be available to Pro and Pro Trial users. 

Watch the below video to see how to deploy the uninstall package. 

Read More

Topics: Microsoft Windows

Up 'n' Coming - Auto Deployments

Posted by Shawn Anderson

Aug 15, 2014 9:00:00 AM

PDQ Deploy 3.2 is finishing up alpha testing. The next step will be beta and we are excited. We're bringing a very commonly requested feature to the plate with Auto Deployments.

It's kind of interesting what you learn from your customers. When we started PDQ Deploy we assumed that every admin wanted total control over every aspect of the environment (not to mention their users' lives). After all, we had all been admins before and that's how we operated.

But lo and behold, there are quite a few admins who would actually prefer to let deployments just automatically happen, kind of a "set it and forget it" thing. So, we're very pleased to provide this new feature. 

We call it Auto Deployment, and it will be an Enterprise level feature in PDQ Deploy. 

What is Auto Deployment?

Auto Deployment will allow an IT Admin to select which packages from our Package Library should be automatically deployed to computers when new updates are released. The setting will allow the admin to select the number of days after a release to automatically deploy a package (or packages). 


Finally, you can set Java or Flash (or any other package in the Package Library) to just push out to your environment after it's released.

Beta testing will hopefully be starting next week. To sign up to receive beta notification click here.

If you are an existing PDQ Deploy user you can be notified when betas are ready for download by checking the "Include Beta Versions" checkbox in File > Preferences > Auto Update.

We have a lot of users waiting for this and we hope that they like it. If you have suggestions for product enhancements please post (or vote up) your favorites in our forums

Read More

Topics: pdq deploy

Admin Arsenal Blog

Subscribe to Email Updates