Hello! We are a new Protect implementation and are having issues with scanning and updating of two servers that reside on the far side of a WAN from the console. On scheduled scans, the first attempt always fails with a 201 (Network connection error. Verify that you can remotely log on to the specified machine) error. Both servers are correctly configured for connections, remote registry, etc. When manually scanning the error is usually 452 (unable to connect to remote machine). Making second attempt within a few minutes of a failure will usually yield a successful scan.
In short, something about going over the WAN is causing an error on initial attempts, but follow-up attempts have a good shot at succeeding. We are clean and standard with regard to Active Directory, DNS, time synch, permissions, bandwidth, and so on. From the console I can connect to both machines over CIFS or whatever else without issue.
Has anyone else dealt with this issue over a WAN before? Suggestions?
The purpose of this article is to show full examples of the reports that are offered under Tools > Create a Report.
Description
Some of the documents found in the attached zip file at the end of this article are for one machine only. This was done to show how large some reports will be when they are generated for all machines in an environment (i.e. the more machines, the bigger the report). If you do wish to not have all machines shown in the report, then it is recommended to use the advanced filter options to narrow down the results of the generated report.
Additional Information
For more information on reports, please consult the following articles:
When trying to download Microsoft patches MS15-106 and above you receive the error message "Connection lost: The remote certificate is invalid according to the validation procedure."
If the Certificate is not in your "Computer account" Certificate store under "Trusted Root Certification Authority" it is either unable to download or it is in your "Untrusted Certificates" store. If you find the Baltimore Cyber Trust Root Certificate under the "Untrusted Certificates" store simply move it to the "Trusted Root Certification Authority" store by dragging and dropping it.
If the certificate is not in either certificate store you will need to download it manually and import it into the "Trusted Root Certification Authority" store. To do this, find the Microsoft Bulletin ID URL for the problem patch (This can be found in Patch View) and navigate to the site by clicking on the link.
Once you are there you will receive an error stating there is a problem with the sites security certificate. Download the Baltimore Cyber Trust certificate from the browser and import it into your "Computer Account" Trusted Root Certification Authority Store. You should now be able to navigate to the Microsoft Bulletin ID page without error as well as successfully download the patch in Shavlik Protect.
If you get to the Microsoft Bulletin ID URL and you receive no Certificate Error you most likely have the Certificate in your "Current User" Trusted Root store but not in your "Local Computer" Trusted Root store. To remedy this you will need to export your Baltimore Cyber Trust Cert and Import it into your Local Computer certificate store.
Since the upgrade to 9.2 when deploying updates to a different domain than the console we are seeing the status stick at Scheduled. I can see the updates being applied by monitoring the system event logs on the server but nothing is reported in to the console.
This was working before the upgrade so what has changed?
Is there a way to downgrade the system back to 9.1?
Hopefully an easy answer but I'm new to Shavlik and need some clarification. From what I've read, you should deploy service packs, before patches which makes sense. My question is that suppose you have machines that need a couple of service packs and some patches as well. If you choose to deploy all patches, will Shalvik install the service packs one by one with a restart after each installation and then rescan and deploy the remaining pertinent patches? Or do I need to schedule the service packs individually and make sure they have been deployed successfully before rescanning and scheduling the regular patches?
I just upgraded to 9.2 and everything appeared to be fine until I attempted to deploy the missing patches. I can scan my network, but I keep getting an error message that reads "Error on (Machine Name): Failed" I've tried everything I can think of to resolve the issue (i.e., disjoining the box from the network and rejoining it, setting the credentials (which I never had to do in the previous version), and selecting one patch at a time. All of which rendered the same result "Error on (Machine Name): Failed." How can I resolve this issue?
I'm trying to clean up our credentials library, but I am unable to delete credentials created by other users (predecessors, mainly). How can I remove credentials that were created by a no-longer active account?
When upgrading from Shavlik Protect 9.1 to 9.2, the database upgrade fails with a SQL install script error "A data conversion error has been detected during the database upgrade process. Cannot find the object 'APEventsDeleteHistorical' because it does not exist or you do not have permission."
SQL Management Studio is a tool used to manage permissions and setting for SQL database. For more information and download links please see the following article:
"Protect" is the default database name. If you have renamed your database to something other than "Protect" please choose the database your Shavlik install is connected to.
