|
|
Toll Free: (866) 407-5279 Direct: (651) 407-5279 |
|
|
|
Toll Free: (866) 407-5279 Direct: (651) 407-5279 |
|
The patch remediation database is used by UpdateEXPERT Premium and UpdateEXPERT Standard. This database should not be confused with the MSDE/SQL database used in UpdateEXPERT Premium for storing enumeration, query, and validation data seen in the Network Pane of the Console.
Briefly, the UpdateEXPERT database files contain information describing patch detection methods, patch relationships to OSes, Applications, and other patches, patch requirements (like rebooting), and patch validation criteria. New patches are tested by the UpdateEXPERT database team, then added. The team determines how critical the patch is, the relationships, requirements (reboot), etc. This process can be shorter or longer, depending on patch complexity. New updates typically become visible in UpdateEXPERT in anywhere from 1 to 5 days after initial release, depending on time needed for testing. Note the "Custom Fix" feature can be used to deploy a patch not supported, or not yet in the database.
As a user, you want to always have the latest database for the most accurate querying. Checking for a database update is configured to occur every 6 hours by default, but it is typical to manually update the database just after installing UpdateEXPERT, or any other time you want to guarantee you have the latest database. To see the newest patches "inventoried" or "listed" for a given machine, you must 1) Update Database Now and 2) Query one or more machines, then you will have an accurate picture of what is "installed/not installed" on each machine. Background (automated) Querying can also be setup ... Go to File > Agent > Settings > General tab.
After querying, during deployment, the database is used by the Patch Install Wizard to determine the optimal way to group patches and minimize reboots (Smart Reboot Elimination), and to check if the selected or required updates chosen by the administrator are valid for the selected target systems. Use the bookmarks below to jump to further information of interest in this article.
Database
Download Requirements 
Database Downloads over Slow Links
Database Files in UpdateEXPERT Premium 7.0 and 6.3
Database Files in 6.0 through 6.2
Database File Attributes
Database File Numbering
Database Security
Microsoft Private Fixes
The UpdateEXPERT Database is a closed proprietary runtime database, with a small footprint (20MB), and is downloaded in its entirety to the Master-Agent (which checks every 6 hours by default), and automatically propagated to Leaf-Agents, whenever a new database version becomes available. Download scheduling is controlled by the Administrator from:
"File > Agent > Settings > Updates Tab"
You can manually request a database download at any time (such as the initial install) with:
"Help > Update Database Now"
An UpdateEXPERT subscription is required to continue getting database updates. It's very easy to confirm that you have the latest database version.
Note: To update the patch remediation database, receive product updates, download patches, and download security templates, specific URLs must not be blocked by the Internet Firewall(s), see:
Internet Firewall Requirements
On slow links (56K for example), be aware that you may need to increase the "Timeout" value for the database download from 20 seconds (default) to 60 or 120 seconds (max). See "File > Agent > Settings > Internet" Tab.
In the 6.3 release the *.db files were consolidated in the "Common Files" folder, and a new DLL file was added to reduce the footprint of the database overall. This convention in carried over to UpdateEXPERT Premium. The database consists of the following files:
|
Name |
Location |
|
UEInstallDatannn.db |
Program Files\Common Files\UpdateEXPERT |
|
ConsoleDatannn.db |
Program Files\Common Files\UpdateEXPERT |
|
ActorDBnnn.db |
Program Files\Common Files\UpdateEXPERT |
|
Codec4ue3dbs.dll |
%SystemRoot%\System32 |
Prior to the 6.3 release the *.db files were in various folders, and the DLL file (above) did not exist. The database consists of the following files:
|
Name |
Location |
|
UEInstallDatan.db |
Program Files\Common Files\UpdateEXPERT |
|
ConsoleDatan.db |
Program Files\St Bernard Software\UpdateEXPERT |
|
ActorDBn.db |
%SystemRoot%\UEAgent |
Regardless of which database files (prior to 6.3, or 6.3+) you are using, the following is true:
All database files must be in their correct location, and valid for UpdateEXPERT to work. The UpdateEXPERT database is safe and non-intrusive. It will not affect the operation of any other databases on your system, such as Microsoft SQL or MSDE.
These files should not be altered in any way, including moved, modified, renamed, or compressed. Doing so will violate the EULA (End User License Agreement) and irreparably damage the database.
These files are binary files (not viewable), and there is not a client utility for "seeing" or manipulating the data, as there is with SQL Server, for example.
If you ever see multiple copies of db files, don't worry. One digit (prior to 6.3) or Three digits (6.3+), are used at the end of the db filename is used to distinguish between the current and prior file.
To see which db files are "current" according to the Master-Agent, you can examine the UEDatabase key as shown below. Note that the files don't ALL have to be 0 or 1, the digit is simply a way of distinguishing between current/prior.
The Master-Agent receives an encrypted list of database files and their CRCs which it uses to validate the database update. If the file CRCs are incorrect after downloading, they are not installed. If the file CRCs match, then the contents are valid and are installed.
The database itself contains a CRC for each product download file. When a file is requested, the file on disk (if any) is checked for a valid CRC. If it is invalid, the file is deleted and the file is downloaded from the Internet. When the download completes, the CRC is checked. If the CRC is invalid, the download repeats according to the number of retries specified in the Internet options. In Conclusion, It is very secure and only a valid serial number can update the database.
Microsoft "private updates" can be included in the UpdateEXPERT database. You can submit your Microsoft private update request to Support for inclusion into the UpdateEXPERT Database. You will be advised if we can add the patch, and when we can add the patch.
If you feel that there is missing or incorrect database information, contact support with the issue so it can be investigated. Any database changes would be made at St. Bernard Software and propagated to the user community through the database update feature, Thank You!
