Please see the below Frequently Asked Questions and Answers.
Can I Use Standalone WSUS without SCCM?
We only test publishing our updates to WSUS with SCUP 2011 and deploying the updates through SCCM. Some customers successfully publish and deploy updates in our SCUP catalog using WSUS only and a third party tool WSUS Package Publisher
. This is not a scenario we test or support if there are any issues.
Can I Request A New Application Be Added To The SCUP Catalog?
Yes, we will look into every new application request. We have approved most of the applications that have been requested. The criteria for approval depends on whether the update has the necessary logic and silent installation method to work with SCUP. A list of application requests can be found here: Application Request Forum
. You can request a new application on our Application Request Forum
Do I Need To Manually Download And Import The Catalog Each Time It's Updated?
No, if you add your catalog into SCUP 2011 as documented in our Step-By-Step Guides
you will be notified in the overview node in the SCUP 2011 console each time the catalog is updated on our servers. You can simply click import to receive the latest updates.
How Are Updates In The SCUP Catalog Tested?
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:
- Windows XP (x86)
- Windows 7 SP1 (x86)
- Windows 7 SP1 (x64)
- Windows 8.1 (x86)
- Windows 8.1 (x64)
- Windows 10 (x86)
- Windows 10 (x64)
- Windows Server 2008 R2 (x64)
- Windows Server 2012 R2 (x64)
How Are Installers/Updates Tested For Malware?
We upload all vendor installers (.EXE, .MSI, .MSP Files) to VirusTotal
to ensure installers are free of malware. VirusTotal scans each installer file using 55 different anti-virus engines
. All VirusTotal scans for update files in our catalog scan be found here: https://patchmypc.net/scupcatalog/virustotalscans
After verifying the scan results, we will use the vendors installer file for the update. When we create the update, SCUP 2011 will create a hash of the installer file and save it in the catalog (.CAB file). If the installer file changed (e.g. installer updated/modified on the venders web sever), SCUP 2011 will fail to publish the update due to a hash mismatch.
We then code sign our SCUP catalog (.CAB file) file using a SHA256 code signing certificate. This ensures the metadata in our catalog always came from us and can’t be modified prior to importing it into SCUP.
I Need Help Setting up SCUP 2011 and My Catalog Subscription?
We offer step-by-step PDF and Video guides for all the configurations needed to use our SCUP Catalog. You can review the guides here: Step-By-Step Guides
Is There A Trial Catalog Available For Proof Of Concept?
Yes, we have a trial catalog please see our SCUP Trial Catalog page.
What Is The Turnaround Time For Updates To Be Published In The Catalog?
Generally, we are able to test and publish a new update to our catalog the same day the vendor releases the update. Complicated or updates released late in the day may take an additional day for testing.
Why Isn't Adobe Acrobat, Reader And Flash Player In The Catalog?
We have chosen not to include these updates because Adobe already provides a free scup catalog
for these products. You can add the Adobe catalogs from the Catalogs workspace by clicking Add Catalogs in SCUP 2011.