PDQ Deploy 14 with its many features is now available for download. To update your console, click the “A new version is available” notice in the status bar of your console. If the update link is not visible, go to Options > Preferences > Alerts to enable the update notices.
Want to know what’s new?
“In the game of chess, you can never let your adversary see your pieces”
–Zapp Brannigan, Futurama
People here at PDQ.com know how much I love Futurama, and Zapp Brannigan quotes are some of my favorites.
Since I can never decide on my favorite quote, it only seemed natural to throw together a quick PowerShell function to get a random Zapp quote any time that I wanted.
I’ve had a few people ask me about it, so I figured that I’d throw a blog together.
(drum roll please) Enter PowerShell!
Today, we’re going to show how to delete all target history from a schedule using PowerShell.
Summer is almost over. Those of you who work in education may be feeling the stress of back-to-school related responsibilities. PDQ.com is here for you. We’ve got your back. (Unless you need a glass of whiskey, then you’re on your own there.)
If you’re using PDQ products, you’re already ahead of the game. We’ve got packages, and schedules, and collections! (oh my!)
We know how “fun” it is re-imaging and baselining all your computers. Getting everything installed perfectly can be a challenge.
When it comes time to re-image and baseline your computers, however, you’ll probably want to delete any existing target history from your schedules.
So sit back, relax, grab that whiskey and let’s “learn” you something new in PowerShell.
Have you ever thought to yourself, “Self… how does this PowerShell function work?” If you have, then you’re in luck! With PowerShell, it’s super simple to view Function contents.
In fact, we’re going to show you a few different ways to display that info.
So, hold on to your chairs and your monocles! Let’s dive right in and find out more!
As the saying goes, “Ya know, you don’t know what you don’t know”. Instead of delving into the tautology of that statement, let’s just start right out describing seven features of PDQ Inventory that may have been lost in the cracks, fallen through the weeds, been forgotten, are brand new, or have otherwise gotten lost in another mixed metaphor.
Would you like to see PowerShell in action and ask questions live? Join us for our brand new PowerShell Live! webcasts starting on Tuesday, July 18th at 10:00 AM, MDT. Can’t join this Tuesday? You are in luck, we will be having these the 1st and 3rd Tuesday of every month. I’m looking forward to seeing you there!
Now, onto the topic at hand…
When using remote PowerShell, have you ever run into problems with variables having the correct value? If you have, then you are probably running into one of the most common problems that people run into with PowerShell: remote variables.
For those of you who don’t know, Slack is a team communication application and platform.
Conversations are organized into channels where team members can chat, call, and share files. But one of the coolest features of Slack is their support for third party integrations, which is exactly what we’re going to use today to build a custom slash command to deploy packages directly from Slack!
Disclaimer: This project is not production ready, it’s just for funsies.
As we and everyone else predicted, a variant of the WannaCry/WannCrypt has been released into the wild: NotPetya (early virus scans marked it as last year’s Petya, but it’s not).
We’ve been keeping a close eye on this throughout the day, and have come up with a package that could possibly prevent NotPetya infection. No, this isn’t a guarantee, and while it’s been confirmed by reliable sources (Amit Serper, Hacker Fantastic, Reddit’s /r/netsec), that doesn’t really mean it’s a sure thing, magic bullet, safe unicorn.
From what we’ve been able to gather from the sources above, the NotPetya ransomware looks for a file called perfc in the C:\Windows directory using a wildcard, perfc.* when installing itself. Note: you can create a perfc.dll, perfc.dat, and perfc.bin, etc. if you want to be super thorough, but no evidence suggests this provides any added benefit. (more…)
Inventory 13 is available for download and now includes the Central Server!
If you’ve been using Central Server for Deploy 13 and you’ve been waiting for Inventory to get the same functionality, the wait is now over.
Enterprise customers can now concurrently connect multiple PDQ Inventory consoles to a single PDQ Inventory server. The number of concurrent sessions is based on the number of licenses held. This allows all consoles to connect to the same database and share custom Collections, Reports, Scan Profiles, Custom Fields, Custom Variables, and even custom Tools.
To read more about how Central Server works in PDQ Deploy, see our previous blog on the topic.
Central Server Modes
Central Server is an optional mode of operation and not a component or feature. PDQ Inventory now offers three modes in which it can run. All components installed on that computer (console, CLI, and background service) operate in that same mode and it can only be in one mode at a time. The modes are as follows:
Security advisory? Didn’t we just go through this with WannaCrypt/WannaCry?! It just goes to show you, the job of a SysAdmin is never done.
Although not related to WannaCrypt, Microsoft has just announced a Security Advisory related to vulnerabilities that are at heightened risk of exploitation. For supported operating systems, the patches for these vulnerabilities are already included in our PDQ Deploy Package Library with the Monthly Rollup, Security-only Updates, and Cumulative updates packages. However, PDQ.com no longer supports Windows XP, Windows Vista, Windows 8, or Server 2003 and we no longer create packages for them. But, you didn’t think we’d leave you in a lurch, did you?