Upgrading assets to v17
All of your auto-upgrade settings will have migrated from NIMS to OMS. Assets in OMS all follow the same upgrade behavior as before migration, but these are now conveyed in upgrade policies.
OMS contains a mechanism, named an upgrade policy, for automatically pushing upgrades to assets. Upgrade policies remove the need to distribute new versions of the asset software using outside channels like FTP and network shares. Plus, an upgrade policy provides unattended installation, so coordinating personnel to be present at the time and place of installation is now a choice—it is no longer a requirement.
Under what circumstances should I use an upgrade policy?
There are no steadfast requirements or conditions that must be met for an upgrade policy to prove beneficial.
However, there are scenarios where an upgrade policy proves especially useful. Here are a few examples:
You need to upgrade off-site assets that you have no direct access to.
You have many assets that need to be upgraded; an upgrade policy can apply to full asset groups.
You want to transfer the installation files during non-peak network times.
You have limited uplink speeds and need to throttle the transfer speed.
You want to ensure the installation occurs during non-peak network times, like overnight.1
You want to resume the data transfer from the point of termination if the connection terminates unexpectedly.1
Understanding which upgrade policy is in effect on assets
Individual assets always honor the nearest upgrade policy. For example: if an asset has an upgrade policy applied to it, that upgrade policy is always honored—even if the asset is a member of an asset group that has its own upgrade policy.
This behavior allows individual assets to follow a different upgrade policy than the upgrade policy applied to its parent asset group.
In the context of any specific, individual asset:
If an upgrade policy is missing from both an asset and its asset group, then the default upgrade policy takes precedence.
If an upgrade policy is missing from an asset but one exists on its parent asset group, then the upgrade policy of the asset group takes precedence.
If an upgrade policy exists for both an asset and its asset group, then the upgrade policy of the asset takes precedence.
Table 5. Which upgrade policy is in effect on a specific asset?
Upgrade policy applied to asset
Upgrade policy applied to asset group
Default upgrade policy is enabled
Policy that takes precedence on the asset
X
X
X
Asset
X
X
Asset
X
X
Asset
X
X
Asset Group
X
Asset Group
X
Default Upgrade Policy
No policy
How does the scheduled transfer operate?
Scheduling your upgrade transfer is an effective strategy for limiting the ill-effects of network resource consumption otherwise caused by an on-demand upgrade transfer. Because upgrade data is sent over the same link that the target assets use for other duties, it is recommended that upgrade transfers are only scheduled during opportune times. Scheduling the upgrade transfer does not define when the transfer should start or finish. This sets the window of time OMS can transfer upgrade data to assets. OMS makes every attempt to send data during the scheduled transfer time, but you should schedule a large enough time frame for OMS to facilitate the transfer.
If a transfer cannot successfully finish within the time frame you set, OMS resumes the transfer—from where it was interrupted—during the next time frame available.1 For example, if you set a one-hour transfer window for Tuesday each week, and the transfer did not complete during that hour, then the transfer is suspended until the following Tuesday for the transfer to resume.
How does the scheduled installation operate?
When asset upgrades occur, the probe must be stopped from its monitoring duties during the upgrade installation and must ultimately reboot. These two events cause downtime. Therefore, by controlling the installation time, you can control when the downtime occurs. In this way, scheduling the upgrade installation is, essentially, scheduling the time frame an asset outage is acceptable. Scheduling the upgrade installation does not define when the upgrade installation should start or finish. This sets the window of time OMS can initiate an upgrade installation of your assets.

1 These options are only available to Observer and probes already at or above version 16.1.