# Update Center Source: [https://docs.virtosoftware.com/docs/virto-license-manager/update-center/](https://docs.virtosoftware.com/docs/virto-license-manager/update-center/) Product: Virto License Manager Updated: 2026-11-17 The **Update Center** lists the Virto products installed on the farm and the License Manager, and updates them on every server of the farm when a farm administrator starts the update. It is part of the License Manager from version 3.3.0. The versions published for each SharePoint version are listed on [Virto License Manager](https://docs.virtosoftware.com/docs/virto-license-manager/index.md). In **Central Administration**, open **Virtosoftware Web License Manager** → **Update Center**. The group has the links **Products**, **Subscriptions**, **Health** and **Update Center**. The up arrow with a version number that the License Manager shows next to a product with a newer version (on the installed products list and on the License Manager status page) also opens the Update Center. ## Products The **Products** block lists the installed Virto products and the License Manager in the columns **Product**, **Installed**, **Available**, **Released**, **Size**, **From** and **Status**. - **Update** updates one product; **Update all ({N})** updates every product that can be updated. The License Manager has its own button, **Update License Manager**, and is not part of **Update all**: see [Update the License Manager](#update-the-license-manager). - **Check again** asks the download site for new versions again; **Rescan** scans the update folder again. A row shows one of these statuses: **Ready**, **Up to date**, **Blocked**, **Cannot be verified**, **Not reachable**, **Ignored**, **Other edition, ignored**, **Not checked yet**, **Cannot be read on this server**. **Blocked** means the update cannot start now. The row gives the reason: - "The solution of this product is not in the farm." - "The solution of this product is not deployed." - "A deployment job of this solution is running." - "Requires License Manager {version} or later; {version} is installed. Update the License Manager first." - "The SharePoint Timer service does not run jobs on: {servers}. The deployment would not reach the server." - a license reason. **Cannot be verified** means one of the signature checks failed (see [Update methods](#update-methods)); the row shows the reason. Nothing is installed. **Cannot be read on this server** means that a product is registered, but its files on the server are not the ones it is registered with: "The files of this product on this server are not the ones it is registered with, so its version and license cannot be read here. No update is offered for it." Updating recycles the application pools on every server. The page says so: "Updating recycles the application pools on every server. Run it outside working hours. This page may be unavailable for a short time and reconnects by itself; the update continues on the server, and closing the page does not stop it." **Restart the SharePoint Timer Service on all servers after the update** is selected by default, so that the products' timer jobs run the new version. ## Update source Click **Update source...** and choose where the Update Center takes the packages from: - **Virto download site (Internet)**; - **Folder** — a folder on the Central Administration server or a network share, for a farm without internet access. Click **Check** to test the source, then **Save**. For every package, the folder holds three files downloaded from the Virto download site: the `.zip` archive, its `.SHA256` checksum file and its `.cat` catalog file. The SharePoint farm account must be able to read the folder. The check reports what it found ("the folder is readable, {N} file(s) found.") and what is missing ("Missing in the folder: {files}. Download the file together with the archive; a package without its signature files is not installed."). The block **Files to download for the products installed on this farm** lists the packages to put into the folder; **Copy the list** copies it. The path must be absolute: a drive path (`C:\folder`) or a network share (`\\server\share\folder`). A local path is a folder on the disk of the Central Administration server; on a farm with several Central Administration servers, use a network share. The Update Center does not accept: - device and extended paths (`\\?\` and `\\.\`); - WebDAV paths (`@SSL`, `@port`, `DavWWWRoot`); - a folder in the SharePoint installation, the Windows folder or the working folder of the updater. If the share is on a server that is not in the farm, the page warns that the farm account will sign in to it. Select **I trust this server** to use it; otherwise nothing is saved. If the download site cannot be reached, the page says: "The download site is not reachable from this server. If the farm has no Internet access, choose a folder as the update source and put the downloaded packages there." ## Fill the update folder on a farm without internet access With **Folder** as the update source, click **Script for filling the folder**. The dialog gives a PowerShell script, `Get-VirtoUpdates.ps1`, to run on a computer that has internet access and can reach the folder. The script downloads the Virto packages for the edition of the farm from the Virto download site, checks every file and puts the files into the folder. Run it again whenever newer packages are wanted; the Windows Task Scheduler can start it. It needs Windows PowerShell 5.1. The same script is in the License Manager package, next to `Deploy.ps1`. The dialog shows: - **Command line** — the command for this farm: the edition, the update folder, the installed Virto products and the License Manager. Run it in Windows PowerShell in the folder where the script is saved. **Copy command** copies it. - **Download script** — the script file as it ships, digitally signed by UAB Virtosoftware. - **Text of the script** — the script in a read-only box; **Copy script** copies it. A copy made from the text is not signed: where the PowerShell execution policy requires signed scripts, use the downloaded file. If the update folder is a local folder of the Central Administration server, another computer needs a network path to the same folder, for example `\\server\share\folder`. The command then holds the placeholder ``: replace it with that path. ### Script parameters | Parameter | What it does | |---|---| | `-Edition SE`, `2019` or `2016` | Required. The SharePoint version of the packages. | | `-Destination ` | Required. The update folder; it must exist and be writable. | | `-Products ` | The archive names of the products, for example `ADUsers,Tabs,WebLicenseManager`. | | `-All` | The current package of every product in the list of previous versions. | | `-Package ` | Previous versions, by file name, for example `Virto.SharePoint.SE.ADUsers.3.2.0.1.zip`. | | `-SkipIndex` | Do not put the list of previous versions into the folder. | For example: ```powershell .\Get-VirtoUpdates.ps1 -Edition SE -Destination "\\server\share\VirtoUpdates" -Products ADUsers,Tabs,WebLicenseManager ``` The script: - downloads the `.zip`, `.SHA256` and `.cat` files of every package from `download.virtosoftware.com//` (previous versions from `/Archive/`) and the list of previous versions, `index.json` with `index.cat`; - checks every file before it puts it into the folder: the SHA-256 value equals the `.SHA256` file, the catalog covers the file, and the catalog signature is valid, made by UAB Virtosoftware and timestamped. A file that fails is not placed, the console says why, and the other packages go on; - copies the files under temporary names and renames them, so the Update Center never sees a half-written package. A package that is already in the folder with the same SHA-256 is skipped. Other files of the folder are never changed or deleted; - reports a product that has no published package for the edition as "Not published" at the end of the output. This is not an error; - uses https only (TLS 1.2 or later) and the proxy settings of the user, needs no modules and asks nothing. It sends nothing except the download requests to the Virto download site and collects no data about the computer. Exit codes: `0` — every file placed or unchanged (a product that is "Not published" is not a failure); `1` — at least one item not placed; `2` — nothing done (wrong parameters, unsupported PowerShell, or the destination is missing or not writable). The script does not replace the check on the server: the Update Center verifies the checksum, the signed catalog and the signatures again before it installs anything, and that check cannot be switched off. A package placed by the script is installed only when an administrator starts the update. ## Update methods Choose the **Method**; the Update Center remembers the choice. **What is the difference?** explains the three methods: - **Built-in update** — the License Manager deploys the solution itself and shows every step; - **Package script (Deploy.ps1)** — the License Manager runs the `Deploy.ps1` of the package; - **Package installer (silent)** — the License Manager runs the installer of the package without a window. On SharePoint Server 2019 and Subscription Edition, the modern web part package (`.sppkg`) is updated in the App Catalog together with the solution and keeps its state (deployed, tenant-wide, enabled). The Update Center does not add an app that was never added to an App Catalog and does not touch a web application without an App Catalog; in both cases the page tells you to upload the package to the App Catalog by hand. SharePoint Server 2016 has no modern packages. Before anything is installed, the Update Center checks the archive against its `.SHA256` checksum and its signed `.cat` catalog (valid, signed by UAB Virtosoftware, timestamped), the signature of the installer and the signatures of the Virto libraries in the package. These checks have no override and no setting to turn them off. If any check fails, nothing is installed and the row shows **Cannot be verified** with the reason. ## Update the License Manager The **License Manager** row is updated separately, with **Update License Manager**: a product update never touches the License Manager. A product that needs a newer License Manager is **Blocked** until the License Manager is updated. After the update, the SharePoint Timer service is restarted on every server so that the timer jobs run the new version, and the page reconnects by itself. If the service on a server cannot be restarted, the page names the server and asks you to restart it by hand: ```powershell Restart-Service SPTimerV4 ``` If the License Manager is updated with the installer or the `Deploy.ps1` of its package instead (see [Installing and updating the License Manager](https://docs.virtosoftware.com/docs/virto-license-manager/installing-and-updating-the-license-manager/index.md)), the installer restarts the Timer service only on the server where it runs. On a farm with several servers, the first operation of the Update Center after that restarts the SharePoint Timer service once on every other server that still runs the previous License Manager. The operation log shows a line "{server}: restarted the SharePoint Timer service" for each of them; a line that starts with "WARNING" names a server where the restart failed, with the command `Restart-Service SPTimerV4` to run there. ## While an update runs The page shows the steps of the update, the state of every server, the log (**Log**, **Details**) and the result. While the application pools are recycled, the page says "Central Administration is restarting. The update continues on the server; this page reconnects by itself." An update started right after another one waits until the SharePoint Timer service of the previous operation has restarted: "Waiting for the Timer service on {server} to start the update." If the Timer service has not started again after the last update, a new update is refused: "The SharePoint Timer service on {server} has not started again after the last update, so no new update is started now (it would be interrupted). Start the service (Start-Service SPTimerV4 on {server}) and try again." The updates are run by the **Virto Update Center Timer Job**. If it is disabled, an update started on the page does not start, and the page says "The timer job that runs the updates is disabled. Enable it in Central Administration (Monitoring, Review job definitions)." See [Virto Timer Jobs](https://docs.virtosoftware.com/docs/virto-license-manager/timer-jobs/index.md). The **History** block shows the latest operations with the columns **Started**, **Product**, **Version**, **Method**, **Source** and **Status**; **Show all** shows the rest. Operations older than 90 days are removed. ## Roll back an update Before an update, the Update Center keeps the current version (**Keep the current version for rollback**). **Rollback** installs the kept version on every server. The kept version is checked first: its hash recorded when it was kept and the Virto signatures of its libraries. If its Virto libraries are not all signed by Virto, the rollback is refused. A rollback keeps the backup it used. ## Install a previous version The **Previous versions** tab of the **Update source** panel lists the versions from the archive of the download site and from the update folder, newest first, with a filter and the **Edition** field. **Download** and **Copy the download links** give the files. Each version has a label: | Label | Meaning | |---|---| | Signed, can be verified; Checksum and catalog verified | The version can be installed from this page. | | Signed. Put its three files in the update folder to install it | Download the `.zip`, `.SHA256` and `.cat` files into the update folder first. On a farm without internet access, **Folder script** gives the command that downloads this one version into the folder. | | Signed, no signature file published - cannot be verified | The Update Center cannot check this version and does not install it. Download it and install it by hand with the installer of the package. | | Not signed - cannot be installed by the updater | Download it and install it by hand with the installer of the package. | | Old package without checksum or catalog - download only | Download it and install it by hand. | | Newer than the installed version: use Update | Install it with **Update**. | | Installed version | The version installed on the farm. | Only a fully signed version is installed, and only on an explicit command: click **Install this version**, type the version number to confirm that you replace the installed version with an older one, and click **Install {version}**. The installed version is kept, so you can return to it with **Rollback** or **Update**. **Update** and **Update all** never install an older version. The License Manager goes back to a previous version only if every installed product can work with it. A License Manager version without the Update Center is refused when the package is checked: the farm could not come forward again from this page. When the update folder holds the list of previous versions (`index.json` and `index.cat`, placed by the script), the page takes the list from the folder and says so. The License Manager first checks that the list is covered by a valid catalog signed by UAB Virtosoftware and is for the edition of the farm; otherwise the page says why the list was not used. If the folder has no list and the download site cannot be reached either, the page shows the versions found in the update folder. ## License Manager options and update e-mails The **License Manager** block of the Update Center has two options: - **Do not show the "License Manager is outdated" message on product pages** — for a farm that needs time to approve updates. The option ends by itself after the License Manager is updated. Use it only while the update of the License Manager waits for approval. - **Do not show users the code signature message when this server cannot verify the publisher's certificate** — messages about unsigned, changed or foreign files are always shown, and the Update Center and the License Manager status page always show the real state. See [Signature not valid or not trusted (0x800B0109)](https://docs.virtosoftware.com/docs/virto-license-manager/license-messages-in-virto-products/index.md#signature-not-valid-or-not-trusted-0x800b0109). **E-mails about new versions** sets the sender of the e-mail about new versions of the installed products: - **Sender: the address configured in SharePoint** — if SharePoint has no sender address configured, the Virto sales address is shown as the sender; - **Sender: {Virto sales address}**; - **Do not send**. The e-mails are sent by the outgoing e-mail server of SharePoint to the contact in **Contact information** (see [Product Activation](https://docs.virtosoftware.com/docs/virto-license-manager/product-activation/index.md)); the selected address is only shown as the sender, and delivery failures are returned to it. When you switch the e-mails on again after **Do not send**, the page offers to send one e-mail about the updates found while they were off (**Send now** or **Do not send**). The e-mail "Virto product updates are available" lists the products with a newer version in the columns **Product**, **Installed**, **Available**, **Released** and **Download** (links to the package, its checksum and its catalog), and explains how to update in the Update Center. If you have any questions about the Update Center, please contact our support team at [**support@virtosoftware.com**](mailto:support@virtosoftware.com) or through [**this form**](https://www.virtosoftware.com/getsupport/).