Microsoft has baked into the upcoming Fall Creators Update of Windows 10 an interesting little feature called Controlled Folder Access, which allows you to set restrictions on which executables can make changes in certain directories. In the recent Insider Preview builds of Server 2016, Controlled Folder Access has been present, so it’s probably safe to assume the next iteration of Windows will also include this. This addition appears to be in response to recent highly-publicized ransomware attacks.
Plenty of security companies offer products that provide control over which applications are allowed to execute in which directories. Carbon Black, Trend Micro, McAfee, and many others have application control solutions that allow you to create and manage policies to keep your network safe while allowing your end-users to do their work. Make no mistake, this feature in Windows is not quite as sophisticated, but it can provide a fairly useful service for individual users if configured wisely.
So, you ready to rumble and enable it? …hold that thought!
If not implemented properly, this feature has the potential to prevent remote management such as software deployment and inventory collection, aka PDQ Deploy and PDQ Inventory.
Dear Admins of Microsoft XP and Server 2003 clients,
We feel your pain and offer our deepest sympathies. However… computers with Microsoft XP or Server 2003 can no longer be managed using PDQ Deploy 14.
XP and Server 2003 were end-of-lifed by Microsoft in 2014 and 2015 and have been unsupported by PDQ.com since 2015. Unsupported by PDQ.com means that testing PDQ Deploy and PDQ Inventory with XP and Server 2003 was officially stopped. While our products still worked with these two operating systems, without testing them, we could no longer guarantee functionality.
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.
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.
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.