Select Page
Subscription comparison chart:
Subscription | Basic | Enterprise | Enterprise Plus | |
|---|---|---|---|---|
Price | ||||
Publishing Method | ||||
Deploy as a software update in SCCM | ||||
Auto-sync the third-party catalog | X | |||
Auto-publish updates as metadata-only | X | |||
Customizable synchronization schedule | X | |||
Auto-publish updates as full-content | X | |||
Disable product(s) self-update feature | X | X | ||
Automate update deployments in SCCM | X | X | ||
Auto-close application before installations | X | X | ||
Skip update if the app is running | X | X | ||
Auto-delete public desktop shortcuts | X | X | ||
Add a custom pre-installation script | X | X | ||
Add a custom post-installation script | X | X | ||
Add custom command line parameters | X | X | ||
Standard installation logging path | X | X | ||
Support for standalone WSUS | X | X | ||
Automatically create SCCM applications | X | X | X | |
Automatically update SCCM applications | X | X | X | |
Subscription comparison video:
The Basic Subscription subscription will only support publishing our catalog to WSUS from Microsoft SCUP. SCUP publishing doesn’t support automated publishing. You will need to manually import and publish third-party updates whenever there is a catalog update.
The Enterprise Subscription would support publishing our catalog automatically using our publishing service or the SCCM 1806+ third-party software update catalogs feature. Our publishing service does support extra customization options (see chart below) that wouldn’t be available when using the SCCM 1806+ in-console publishing feature.
The Enterprise Plus Subscription contains all the feature of Enterprise, and also allows the creation of base installation packages in SCCM.
Bank Transfer (ACH transfer)
American Express
Discover
MasterCard
Visa
Bank Check
Bank Transfer – (Wire/ACH transfer)
American Express
Discover
MasterCard
Visa
We use Net 30 terms for any invoices unless otherwise agreed upon prior to receiving a purchase order.
We offer the following subscription lengths for the Enterprise and Enterprise Plus subscription levels.
The Basic subscription level is offered in a 1-year subscription length only.
We offer a standard 15% discount for education customers. Please let us know in the comments on the quote request form if you are an educational institution.
We offer a standard 15% discount for non-profit organizations. Please let us know in the comments on the quote request form if your organization is non-profit.
We offer multi-year discounts, as shown below.
Multi-year discounts can be combined with other discounts mentioned in this topic.
We can offer volume discounts when needed.
As of June 20, 2019, we are standardizing on volume discount percentages based on device ranges to be up-front and save time in the discount process.
Volume Discount Percentages
| Device Range | Discount Percentage |
| 5,000 – 5,999 | 5% |
| 6,000 – 6,999 | 6% |
| 7,000 – 7,999 | 7% |
| 8,000 – 8,999 | 8% |
| 9,000 – 9,999 | 9% |
| 10,000 – 10,999 | 10% |
| 11,000 – 11,999 | 11% |
| 12,000 – 12,999 | 12% |
| 13,000 – 13,999 | 13% |
| 14,000 – 14,999 | 14% |
| 15,000 – 15,999 | 15% |
| 16,000 – 16,999 | 16% |
| 17,000 – 17,999 | 17% |
| 18,000 – 18,999 | 18% |
| 19,000 – 19,999 | 19% |
| 20,000 – 20,999 | 20% |
| 21,000 – 21,999 | 21% |
| 22,000 – 22,999 | 22% |
| 23,000 – 23,999 | 23% |
| 24,000 – 24,999 | 24% |
| Above 25,000 | Please request quote |
Note: if the volume discount exceeds other applicable discounts with the exception of multi-year discounts, only the discount with the highest percentage will be applied.
You know your environment better than us. We currently use the honor system with regards to allowing you determining your own managed device count when requesting a quote.
If you plan to deploy third-party updates to all managed devices, using the All Desktop and Server Clients member count would be a good option.
You can exclude machines where third-party updates will not be deployed such as Mac OS devices and other machines you want to exclude from your third-party update deployment collections. For more details about excluding please see Can I exclude devices?
For environments between 1-500 devices, the following base prices are applied:
We price our software subscription competitively. We believe the value and time savings provided by our service makes our base pricing fair. We determined our base pricing allows for small profit margin after payment processing fees, quote and invoicing time and subscription provisioning.
We ask that you try to calculate your active client count that will receive our third-party updates to the best of your ability. A few examples could be:
You can use the same catalog subscription in multiple environments as long as the client count for all locations were factored into the initial purchase.
For example, you could use the same catalog subscription in Development, Quality Assurance, Production environments.
We try to reduce friction for our customers wherever possible. We allow up to 25% client growth within a subscription year from the initially purchased device count. We determined 25% growth will cover normal device fluctuations within one year period.
If you are in a scenario where the growth has exceeded 25%, please use our contact form to determine if a true-up for the current subscription year would be required.
We will send notifications out to the primary contact(s) on the subscription at the following intervals:
If you aren’t sure the contacts associated with your account or need to add additional employees for the renewal notifications, please use our Contact Us Form.
For one-time sales, we offer a 10% reseller discount for all orders $1,500 or smaller. For purchases larger than $1,500, we have a standard 5% reseller discount.
All you need to do is request a quote and purchase on behalf of your client (a contract is not required).
On the quote request form, choose “Yes, I’m purchasing for another customer” on the following question:
You will be required to enter the end user’s company name, primary contact name, and primary contact email. We need the end user contact details for subscription delivery, expiration notifications, and significant service updates.
You will need to ensure you know the number of devices in your client’s environment for the quote for the following question.
We use Net 30 terms for any invoices unless otherwise agreed upon before receiving a purchase order.
When purchasing for a client as a reseller, you will enter need to enter primary end users information when requesting a reseller quote.
The license details for the catalog subscription will be sent directly to the end user, and the primary reseller contact(s) will be included in the CC line in the delivery email within one business day of the purchase.
Most of our customers choose our publishing service over SCCM 1806+ in-console publishing since it offers better automation and helpful deployment options.
Here are a few essential items to consider in your decision:
<li”>Our publishing service does offer some helpful options when performing updates such as running customer pre/post update scripts, skipping the update if the application is in use, deleting public desktop shortcuts, disable products self-update feature, creating standard installation logs, and republishing updates.
Please see the chart below for a detailed comparison between the different publishing options.
Subscription | Basic | Enterprise | Enterprise Plus | |
|---|---|---|---|---|
Price | ||||
Publishing Method | ||||
Deploy as a software update in SCCM | ||||
Auto-sync the third-party catalog | X | |||
Auto-publish updates as metadata-only | X | |||
Customizable synchronization schedule | X | |||
Auto-publish updates as full-content | X | |||
Disable product(s) self-update feature | X | X | ||
Automate update deployments in SCCM | X | X | ||
Auto-close application before installations | X | X | ||
Skip update if the app is running | X | X | ||
Auto-delete public desktop shortcuts | X | X | ||
Add a custom pre-installation script | X | X | ||
Add a custom post-installation script | X | X | ||
Add custom command line parameters | X | X | ||
Standard installation logging path | X | X | ||
Support for standalone WSUS | X | X | ||
Automatically create SCCM applications | X | X | X | |
Automatically update SCCM applications | X | X | X | |
Our standard support hours are from 6 AM – 10 PM (EST / UTC -5) Monday – Friday, it’s included in your catalog subscription cost. If you have a critical issue outside of standard hours, you can call the number below and choose the option to be transferred to the on-call engineer 24/7.
There are a few ways you can contact support. Please choose the option that works best for you below.
Email Us: https://patchmypc.com/technical-support (Great place to start since the support form will guide you through attaching relevant logs)
Forum Post: https://patchmypc.com/forum
Live Chat: https://patchmypc.com/technical-support
Support Screenshare: 15 Minutes | 30 Minutes | 45 Minutes | 60 Minutes
Call Us: +1-866-343-3083
We’re a small team, but we think it benefits our support experience. Our support engineers are also software engineers that write our code and have an in-depth knowledge of WSUS and SCCM software update components. You won’t be transferred to multiple times to get the answers you need. – Justin Chalfant, Founder
Please don’t take our word for it. Check out some of the feedback the community has about our support and product 👇
Step-by-step guide for setting up the catalog using our publishing service – https://patchmypc.com/publishing-service-setup-documentation
Step-by-step guide for setting up the catalog using SCCM 1806+ in-console publishing – https://www.youtube.com/watch?v=rBdmWbf5Vgg
Step-by-step guide for setting up the catalog using Microsoft SCUP – https://patchmypc.com/scup-setup-documentation
Yes, we have a trial catalog available for proof of concept Patch My PC Third-Party Catalog Trial.
Yes, our publishing service has the capability in the advanced tab to make third-party software updates visible directly in the WSUS console so you can deploy third-party software updates without requiring Microsoft SCCM.
Our software updates are supported on Windows operating systems only. We make use of the existing SCCM and Windows update agents, so no extra client agents or scanning is required.
When creating an automatic deployment rule in SCCM, we recommend using at least the following criteria in the software updates tab.
Superseded = No
Update Classification = Critical Updates, Security Updates, Updates
Vendor = Patch My PC
Note: We generally don’t recommend including the Update Rollups classification as that classification contains migration updates.
If you have a need to filter by specific products, you can use a title filter to include or exclude specific products as defined in Filtering Specific Third-Party Products from ADRs in Microsoft SCCM – Patch My PC Update Catalog
When sending the logs files, please attach the logs using a ZIP file using our technical support form.
When using the Patch My PC Publishing Service, we will need the following log files from the SUP/WSUS server where the service is installed.
When using the SCCM in-console publishing, we will need the following log files from the SUP/WSUS server where the service is installed.
When troubleshooting updates failing to download into a deployment package from the SCCM console, we will need the following logfile from the machine running the SCCM console:
When troubleshooting automatic deployment rules failing for third-party updates, we will need the following server-side logs files. In this example, we will assume the main SCCM installation directory is: C:\Program Files\Microsoft Configuration Manager
When troubleshooting application installation errors on a client, we will need multiple client logs files. Please include the following logs:
When troubleshooting update installation errors on a client, we will need the following client logs files:
Generally, we can detect, validate, and release new updates on the same day the vendor’s release the update. You can review a full list of past catalog release for reference using our catalog release RSS feed.
We don’t offer an SLA from when a vendor releases an update before it’s added to our catalog due to the following factors:
Updates released after 10 AM (MST), are generally not published in our catalog until the following business day unless they are security related.
When we are building new features in our product, it’s always based directly on the feedback we are getting from our customers. For example, all of the custom options available for updates such as disabling self-updates, custom pre/post scripts, standard logging options, closing apps, custom command lines, and removing desktop shortcuts came from customer requests!
With regards to our supported products, we are only adding new products based directly on what our customers and potential customers are requesting. Over 80% of the supported products in our catalog today were from customer request. If you see a product that a competitor offers that would provide you value, please just let us know and we will get it added!
We understand it may help from a decision perspective to know how one product stands out. We have a recorded live webinar showing the simplicity of our setup and deployment. If needed, we can set up a live demo with your team to answer any questions.
Of course, we think the best way to understand if our solution would fit your needs is to take it for a spin! You can download our free trial, no sign-up forms required! Install it, choose some products, set a sync schedule, and see how easy keeping third-party applications patched can be!
Although we don’t provide any competitor comparisons, we have been keeping track of some community feedback! We think community feedback has more merit than any direct comparison we could offer, check it out below. 👇
Absolutely! We are love adding new products that provide value to our customer base!
We have approved the majority of the requested products. The criteria for approval is the product’s installer/updater has the necessary detection logic, supports silent installation, installs under SYSTEM context, and has a publicly available download URL for the update binary.
A list of products requested and approved products are available on our application request page. You can request a new application on our application request page.
NOTE: for new application request, please use our new Ideas UserVoice Portal. This updated tracking system allows better collaboration for new product/feature request including an up-voting system to help prioritize the products and features that would provide the most value for customers.
We have a public roadmap available to show what features is are currently developing based on our customer feedback portal.
If you have any feedback or features you would like to see, please visit our customer ideas portal and submit any feedback or new product request.
We have no plans to create updates for drivers for Dell, HP, or Lenovo because each of these vendors already provides a free catalog for their drivers.
For Dell and HP, you can subscribe and publish the catalog directly in the SCCM 1806+ console under the Third-Party Software Update Catalogs node.
For Lenovo, add their catalog URL https://download.lenovo.com/luc/v2/LenovoUpdatesCatalog2v2.cab as a custom catalog in the SCCM 1806+ console.
You can find more details about Lenovo’s catalog on their forum post here.
We also have a step-by-step video guide covering how to use the in-console publishing feature in SCCM 1806+, or you can review the Microsoft Docs.
We test update logic (Installable and Installed) against multiple operating system and architectures. We ensure all updates are detected and installed correctly in two separate test labs. Our labs contain the following OS platforms:
When you subscribe to a custom third-party software update catalog using the SCCM 1806+ third-party software update catalogs feature, updates are published as metadata-only during the catalog synchronization until you manually choose to publish the update content.
You can determine if updates are metadata-only from the All Software Updates node if the updates are displayed with a blue icon.
Updates published as metadata-only can’t be deployed until they a re-published with full-content. If you attempt to download a metadata-only update into a deployment package, you will receive the error “All software updates in this selection are expired or meta-data only, and cannot be downloaded.“
In order to download and deploy third-party updates in a metadata-only state, you will need to right-click the update(s) and choose to “Publish Third-Party Software Update Content“.
You can review the full-content publishing progress in the SMS_ISVUPDATES_SYNCAGENT.log. The log is located on the top-level software update point in the site system Logs folder.
Once the publishing of third-party update content is complete, you can sync your software update point for SCCM to pick up the change from metadata-only to full-content faster.
Once the software update point sync is complete, the third-party updates should show in a normal state with a green icon meaning they are available for software update deployment.
When using the third-party software updates catalogs feature directly in the SCCM 1806+ console, there is currently no way to automate the publishing of content for third-party updates.
The third-party update integration in the SCCM console feature is pretty new, and we are working with the Configuration Manager product group to make this feature more automated. We recommend voting on this user voice item Automatically Publish Full Content for Third Party Software Updates.
If you would like to avoid this manual step, you can use our publishing service for full automation and additional features as compared to the SCCM 1806+ third-party software update catalogs feature. Please see the comparison below.
What’s the Difference our Publishing Service and SCCM 1806+ In-Console Publishing?
There are a few scenario’s where you may need to use the Republish update(s) right-click option in our publishing service on product(s).
Here’s a few scenario’s when republishing an update would be required:
How to Republish updates:
Once you determine what product(s) meet the criteria for requiring a republish operation you can click the product, vendor, or all products level and choose the Republish update(s) item.
You will be prompted whether you want to supersede the currently published updates for this product when the new updates are republished.
The republishing of the selected updates will occur during the next publishing service sync. You can trigger this sync to happen right away by clicking the Run Publishing Service Sync in the Sync Schedule tab.
If you review the PatchMyPC.log you should see the updates being republished. Republished updates will have the date appended to the update title here’s an example: Chrome 73.0.3683.86 (x64) – (March 27, 2019)
Once the republishing has completed, the updates will show up in SCCM after the next software update point sync has occurred. You can force a sync to happen by clicking Sync Now
You can monitor the SCCM software update point sync by reviewing the wsyncmgr.log. Once the sync is complete, you should see the newly republished update(s) in the console with the date appended. If you choose to supersede previously published updates for this product, you will see the previous update(s) as superseded.
If you ever need to remove published updates from WSUS and SCCM, this operation can be performed using our publishing service.
Determine what specific update(s) you want to expire/remove. In this example, we will remove the following 7-Zip updates.
Next, within the publishing service go to the “Advanced” tab then click the “Modify Published Updates” wizard.
Select the updates you would like to remove from WSUS/SCCM and click the “Decline Selected Updates“.
Note: we don’t recommend using the “Delete Selected Updates” option unless you are on a call with a support engineer and instructed to do so.
If you want to remove all “Patch My PC” updates or other third-party vendors, you can use the filter by vendor option and select all and decline.
After the updates are declined in the publishing service, you can manually sync your software update point in SCCM for the changes to occur immediately.
After the software update point sync is complete, you should see the declined updates show as expired in SCCM and will no longer be deployed.
Expired updates will automatically be purged from the SCCM database after 7 days.
To enable the Delete button, create a new DWORD registry value: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:EnableDeleteUpdates = 1. We only recommend using this option when working with our support team.
Note: if you don’t want any future updates to be published for a product after deletion, un-check the product in the publishing service, so any future updates aren’t published.
The Basic Catalog subscription would only support manual importing and publishing updates within our catalog using Microsoft System Center Updates Publisher.
The Enterprise Catalog subscription would support total automation for importing and publishing updates within the catalog using our publishing service or the SCCM 1806+ third-party software update catalogs feature.
For a detailed process of our malware testing, please review https://patchmypc.com/deep-dive-into-security-validation-of-third-party-software-updates-in-microsoft-sccm
We upload all vendor installers (.EXE, .MSI, .MSP Files) to VirusTotal to ensure installers for third-party products are free of malware. VirusTotal scans each installer though over 70 different anti-virus engines.
All VirusTotal scans for update files in our catalog can be found here: https://patchmypc.com/scupcatalog/virustotalscans
Our software usage is governed by our Terms of Service and Privacy Policy.
Terms of Service
Privacy Policy