Check for signed releases from inside OneView, then apply them from your own server on your schedule, with verification at every stage.
Your team decides if and when a new release is installed. OneView only tells you that one is ready.
Administrators with update permission can select Check now on the System updates page to ask the online release service for a newer release. The page shows the installed version, when it was last checked, and the release notes.
A release appears only if it is newer than what you run, built for your server's architecture, and compatible with your installed version. Anything older than the installed version is rejected.
When a compatible release is available, an update notice appears in the application for users who can view update status, linking straight to the System updates page.
Every release is vetted before it is offered and verified again on your server before it is applied.
The release must be compatible with the version you are running. A release that needs a newer updater is refused.
Only a package built for your server's architecture is offered.
A release older than your installed version is rejected, so an update can never quietly take you backwards.
The package is checked on your own server before anything is installed, and an unverified package is never applied.
There is no way to upload an update file through the browser. Releases come only from the online release service.
The command you copy contains only the chosen version and local paths, with no download link, credentials or license values.
An update is designed to end in one of two safe places: the new release running, or the previous one restored.
If the new release cannot start safely, the update rolls back automatically and the page reports that the previous version was restored and why.
Administrators can follow the update stage by stage on the System updates page. During the maintenance restart the page retries automatically, and it shows the final outcome when the application is back.
Every attempt ends as completed, restored to the previous release, or needing host intervention, with a plain-language reason such as a failed health check, a timed-out drain, or an interrupted update.
Checking for a release needs a valid online license. If the license needs renewing, the page tells you so before you check again.
See how checking for a release, confirming it on your server, and following it through to completion fit together on the System updates page.
