Shared database version and compatibility warnings added to Shared Databases page. Removed ability to reorganize panels in Deployments page. PDQ Inventory Collection condition added to both the package properties and individual step properties. Issue with Repository cleanup causing the console to freeze after excluding a folder. The filter on the Select Target List window is now working as expected. Fixed an issue when copy/paste would fail with remote control software running. Download packages set to manual approval were not listed in the Update tab of the Package Library until after a console refresh. Ability to change the order of steps in a Package by dragging and dropping in the Package window. Fixed an issue with printing from the Schedule Target History tab. Packages now show deployments where the package was nested within another. Added credentials user name to the notification email report. Various other bugs, including locking issues in regard to Central Server. Importing Targets Lists with multiple entries now import correctly. Fixed a bug preventing the use of name@domain credentials in some places. Variables are no longer duplicated upon upgrade. They are both pay for utilities, but do have a free version of the programs with a few limitations. All machines should have downloaded their patches by Saturday. And in every case, the application launches but sits there doing nothing until it eventually stops itself. In this case the Win 10 (1809) and 2019 Cumulative Update package. Fixed an issue preventing deployments from using the setting on the package for Run as Local System. The default credentials are now known as default Deploy User. This will narrow down the packages being displayed. Improved main window tree with multiple selection. Once you've downloaded your chosen Windows OS ISO, you'll need to extract the files with 7-Zip. Deleted deployments would occasionally reappear after restarting the console. When using schedules via the CLI, computer names are no longer case sensitive. In the package description, adding URLs now works as expected. Added support for SSL connections to Spiceworks. Variables for UNC paths are no longer being removed when replacing install files. Preferences window can now reset to default and import/export most settings. Updated the font in theCommand Stepso similar letters are more distinguishable. I'll wait. Here's what the Windows 7 and Windows 8.1 update packages look like in PDQ Deploy. Upgraded DevExpress controls to fix certain Console problems on Windows 8.x touch screens. Etc etc. Added ability to deploy a single attached package when right clicking a schedule. New Reports were not populating in the Reports menu without a manual refresh or restart of the console. Compare Octopus Deploy vs PDQ Deploy & Inventory. Fixed an issue when using Pull file copy and Command steps. With PDQ Deploy, you have access to our package library, which is jam-packed with hundreds of pre-built application packages, including Windows updates. Why don't you have a LinkedIn profile? PDQ Inventory, on the other hand, specializes in collecting and organizing information about the computers in your environment, making it easy to keep track of which computers have the latest updates and which don't. Background Service, Central Server, Credentials, Console Users, and Variables moved out of Preferences to the new Options menu. Refreshing the console using F5 also checks for new versions of PDQ Deploy. This will ensure that the update will be carried out quietly. Variables in file names are not expanding when using something other than an .exe. Bundled old Basic subscription into Pro mode. You can install updates with just PDQ Deploy, configured with dynamic collections in PDQ Inventory, without WSUS or powershell module. However, as has recently been shown with numerous security scares already to start out 2020, patching your systems is one of the most important tasks that you need to make sure you do often. This step allows you to natively copy files to target computers. The file picker button on the Command Step occasionally opened to the wrong package. Changed the deployment process to deal with reboots caused by install and command steps. Upgraded Auto Deployments now use the correct icon. Fixed an issue with FIPS computers downloading from the Package Library. Fixed an issue with Remote Repair where scanning a local system would fail. Additional performance improvements, particularly while browsing Active Directory containing a large number of objects. Also, fixed an issue with importing MSU files. Added Duplicate menu option to duplicate selected Package or Target List. Added a Logoff step. Post Deployment Notificationsnow include a subject line and email body. You can monitor the status of your deployment in the deployment status window. It really is that simple! Integration issues between PDQ Deploy and PDQ Inventory when using Central Server. PDQ Deploy and PDQ Inventory are great for your automation. So if you scan for updates, update, then scan and find no updates.it will still show the latest results that DID return items. Fixed an issue with deploying to targets containing special characters in the hostnames. Added Run as Local System option to Packages. Standardized hyperlink display properties. More performance improvements, particularly while editing packages. Improved wording on confirmation dialogs for clarity. Saving a package occasionally changed the focus to the Package Properties. Tooltips on the variables button will display the current value of any Custom and System Variables used. Conditions for Windows XP, Server 2003 R2, and Server 2003 were removed. oUnedited Auto Download packages from the Package Library can be deployed to PDQ Inventory targets with an External Agent. deployment status). Scrolling through multiple targets in deployments results now works as expected. Opening a package while it was downloading would not be available for editing until the package was reopened. Refreshing the console using F5 also checks for new versions of PDQ Deploy. Fixed a crash when Windows spell check components are corrupt. The Updates section of the Package Library now sorts by modified date by default. Fixed potential issue with placeholders in the Post Schedule Notification not displaying the correct data once emailed. While running a deployment, the copy status on the main deployment panel now provides the percent copied as well as the copy speed. To add to the confusion, each version of Windows 10 has its own end-of-life date, which you can view here. Issue causing error messages of either incorrect or unknown user name and password. We now display number of Selected Computers in the Deploy Once window. When doing a refresh of the console, packages now prompt for unsaved changes. Changed the deployment process to deal with reboots caused by. Fixed an issue reading group names from Spiceworks 7. That's it! These updates include bug fixes, security patches, and system stability improvements. Fixed issue which could result in duplicate Packages. When doing a refresh of the console, packages now prompt for unsaved changes. Fixed an issue with downloading from the package library with certain proxy servers. Born in the '80s and raised by his NES, Brock quickly fell in love with everything tech. 'Approval Countdown' column added to the Auto Download Approvals section of the Package Library. Moved License control from File menu to Preferences window. Warnings about Caps Lock when entering a password. Fixed the ability to attach the same package to the same schedule more than once. Changed Message step to allow ANSI characters (thank you, Gnther). PDQ keeps track of the when new updates are made available writes the scripts and all l you . Database file location from the registry is now being read properly. Fixed an issue where access to the registry might cause a crash. That way I can just see what's online that needs to be patched. Repository cleanup potentially caused a timeout. Removed the import package .xml file size limit. Yes, you read that right. The Cancel Download button on the Package Library works again. https://www.pdq.com/pdq-deploy/https://www.pdq.com/package-library/Cumulative and Monthly Rollup Updates Skipped steps in a Nested Package deployment no longer reflect a green checkmark in the output display. Sorting issue when choosing target computers from Inventory now a thing of the past. Fixed the ability to deploy to an IP address as the target. Create new package to copy folder to PC, then next step is command with the following: C:\WinUpgrades\Win1021H2\setup.exe /auto upgrade /migratedrivers all /ShowOOBE none /Compat IgnoreWarning /DynamicUpdate disable /Telemetry Disable. Update notes have moved. I'm in the process of trying to deploy and update our Windows 10 clients from one version to the next. Files can be imported by dragging or copying from Windows Explorer to the application. Added condition for determining whether a user is. Improved organizing of items in the Main window, including placing items in any order. . On the package page of the console, the Approval setting for an Auto Download package now displays next to the package name. Fixed issue importing computers from PDQ Inventory All Computers collection. (To update the taskbar icon, launch PDQ from the updated desktop icon). A restart of both background services for PDQ Deploy and PDQ Inventory may be required for proper integration. Added warning icon to newly created Auto Deployments until all necessary package files have been downloaded. Fixed an issue with sharing packages that use the Repository system variable. PowerShell steps no longer add a single space that was preventing the use of signatures. I've also completely disabled UAC just in case, and made sure to bypass the execution policy, etc. Fixed an issue where nested packages may not export correctly if the target package was renamed. Ability to select a package from within the Deploy Once window. Fixed issue preventing deployment to computers with underscores or other special characters in their names. Ability to delete a computer's history from all schedules from the Target History tab of a schedule. PCs with updates available: All > Powershell Scanner > Size > Greater Than > 1kb, PCs fully patched: All > Powershell Scanner > Title > Equals > (leave blank. Download History now displays the proper download types whether downloading for the first time or approving a new version. Packages created from the PDQ Inventory Run Command window now follow correct naming conventions. Integration issues have been fixed when used in conjunction with PDQ Inventory 17.1.0.0 or later. Fixed an issue where using Duplicate in the main window could cause an item to be duplicated twice. One of the things I really like is that PDQ Inventory includes out-of-the-box many of the very useful collections that you would have to otherwise build from scratch. Added OS Condition for Windows 10 in PDQ Deploy package steps. Occasionally the temp directory was not cleared until after a restart of the service. These updates include new features, security improvements, visual differences, and more. Duplicating a folder was not always duplicating the first package in the folder. You can install updates through WSUS configured with GPO - without powershell module and PDQ. 4th: Now we need some PDQ jobs. Enabling or disabling multiple steps in a package now works as expected. Fixed issue when attaching to Spiceworks servers that are running 7.2.00508 or higher. Added option to run processes as the logged on user. We have some users with specific software that has been broken a few times in the past by automatic updates. Read the PSWindowsUpdate documentation about the switches. 2021 PDQ.com Corporation. You need to hear this. Target computers are randomized in deployments. Long running deployments would sometimes result in an incomplete schedule notification. Ability to view Concurrent Session details in the Console Users window. They went on to create tools to suit smaller and medium-sized businesses, and then expanded again to the enterprise level. So what about Windows 8.1? Once you've imported your computers into PDQ Inventory, you can sit back and relax while PDQ Inventory takes care of everything else. What are you waiting for? Potential error message stating that Auto Deployment was missing installation files. Also, don't forget to check the Include Entire Directory box. If you are like me, keeping your hosts updated can be one of the most cumbersome and tedious tasks that you have to carry out in your environment. The tab header in a schedule now shows an error icon when an error exists within that tab. Here are a few I have set up, Install ALL available updates [no reboot], Install ALL updates EXCEPT nvidia drivers, Install ONLY driver updates [except display]. This gives you tremendous visibility into the software and application landscape as it exists in your environment. I have done what this post mentioned via PDQ and it works pretty well, the only thing I don't like is the lack of a status bar. Danish characters were not displaying correctly when selecting PDQ Inventory collections as targets. Meaning, you won't have to go out and manually download the newest Windows 10 update package every month. Whenexportingpackages, folders, or target lists, the type of file is identified in the Save as type field. As always, PDQ.com is here to make the lives of our fellow sysadmins easier. New themes available for the console, including dark. In Preferences, removed Mail Notifications and consolidated it to theMail Serverpage. Can't get enough #PDQ? It is nice for slow links. Ability to attach/detach package(s) from a new schedule prior to saving it. Monthly Rollup updates are similar to Cumulative updates. Fixes issues with opening the console after an upgrade. Added library package update notification for Pro users. Once you've selected the setup.exe file, you'll need to add "/auto upgrade /quiet" as additional parameters. Also, fixed an issue with importing MSU files. Fixed an issue with changed printing margins. oA restart of both background services for PDQ Deploy and PDQ Inventory may be required for proper integration. a software deployment tool used to keep Windows PCs up-to-date without bothering end users. Moved License control from File menu to Preferences window. Configuration summary added in Help > Current Configuration Summary. Creating a deploy package for Windows 10/11 in PDQ Deploy is very simple. Print Preview can now be printed across multiple pages using the Auto Fit profile. Server 2016 added to O/S Version on the Conditions tab of a step. Issues with sorting during a running deployment has been fixed. I've also added a reboot as a second step, or else it'll appear to hang. Fixed an issue browsing to files in the Repository when using a mapped drive. Improved the speed of aborting deployments. Integration issues have been fixed when used in conjunction with PDQ Inventory 17.1.0.0 or later. inland m1 carbine serial number date of manufacture,
Does Lake Norman Have Snakes,
Prayers To Confuse The Plans Of The Enemy,
List Of Villages In Nsukka,
Cabbage Moth Decoy Template,
Give Examples Of The Direct Relationship Between Risk And Return,
Articles P