Servers
Every server in the inventory in one table — what each column means, what the update-status color marks, and which actions run on a multi-row selection.
The screen is titled Update status, and it is the most-read table in the product. It shows the server inventory as it arrives from the inventory sources, and adds two things the inventory does not know: when the server is next due for an update, and whether that date has already passed.
Of all the columns in the table, Comments is the only one Regulaxy writes. Everything else is read-only.
The columns
| Column | What it says |
|---|---|
| Host name | The identity. Clicking it opens the server record. It is the one column never pushed off the screen |
| IP | Address from the inventory |
| System | The business system the server belongs to, from the asset register |
| System manager | Who is responsible for it — same source |
| Physical/VM | Whether this is a physical machine or a guest |
| Tier | The exposure rating of the location: B2B, Tier 1, Tier 2, Tier 3, MGMT. It is what decides the update cadence |
| Update configuration | The target group the server belongs to in the update distribution system, as recorded there |
| Environment | Production, DR, test — as the inventory marks it |
| OS type | Windows or Linux |
| Operating system | The full string, with the vendor mark |
| Domain | The domain the server is joined to |
| Last update | The date of the last recorded update |
| Next due | The date to reach |
| Frequency | How many months between updates |
| Comments | A free-text note from the team, up to 400 characters |
Next due and Frequency come out of the same calculation, from the Tier, so they cannot contradict each other: if the frequency says six months, the next date is six months after the last update. A blank or unrecognized Tier gets the longer frequency — missing data will not produce an aggressive date. A server with no readable last-update date keeps whatever date the inventory supplied; the system does not erase a date it has nothing to put in place of.
The update-status color
Every row is in one of three states, painted both in the Next due cell and in the dot beside the host name:
| State | When | How it looks |
|---|---|---|
| Overdue | The due date has passed | Red, and the whole row takes a faint red tint |
| Update soon | Fewer than 14 days to the date | Amber |
| OK | 14 days or more | Green |
The tint is on the whole row and not only on the date cell, deliberately: the question this screen exists to answer is "which servers are late", and it has to be answerable without first finding the right column. The same three numbers appear in the header strip, beside the total.
Filtering
Three routes, and all of them write to one filter state — so what you filtered stays true in a saved view, in an export and when you clear:
- Quick filter — the rail behind the filter button in the toolbar. Values are grouped by update status, system, infrastructure and operating system, and each value carries the number of rows that would remain if you ticked it.
- Column filter — the menu in each column header, including date ranges on Last update and Next due.
- Search — the toolbar box, across all fields.
Below the toolbar is an Active filters bar: one removable chip per filter clause and per sort level, plus Clear all.
Clicking a column header sorts. Shift+click adds a second sort level.
Selection and bulk actions
Ticking a row opens the selection bar. "Select all" selects every row the current filter allows, across all pages — not the ones on screen. Filter after selecting and the rows that left the filter leave the selection too, so no action runs on a row you cannot see.
Two actions are available to an administrator:
- Schedule event — opens the scheduling wizard with the selected servers. The link carries up to 50 servers; if you selected more, the system says how many will be dropped before it continues.
- Update comment — writes the same note to every selected row, in one transaction. Rows that failed are listed by name and the dialog stays open.
Above 20 rows a confirmation states the count.
Comments
The note belongs to Regulaxy, not to the inventory source, and it is the only thing in the table that gets written. Edit it by clicking the cell; up to 400 characters.
Columns, density and export
- Column order and visibility are a global setting an administrator saves for everyone, behind the columns button. Density (compact / normal / comfortable) and rows per page are a personal choice and are kept in the browser.
- The table never scrolls sideways. When space runs out, the lowest-priority columns — the last in the order the administrator set — collect into a per-row "+N" panel instead of crushing all of them.
- CSV and Excel export exactly what is on screen: the filtered and sorted rows, and the visible columns. In the Excel file the Next due cells carry the same status color the table shows.
- Fields defined in custom fields with "Show in table" switched on arrive here as ordinary columns — filter, sort, saved view and export included.
A server that does not appear
Two common reasons, both in the source rather than in Regulaxy:
- The server is marked in the source as decommissioned (OFF). The mark is judged per server: it drops off the list only if it has no active location record at all.
- No read permission on one of the inventory sources. That does not look like a permission error — it looks like a missing inventory.
The freshness indicator in the toolbar says how old the data on screen is, and clicking it re-reads it.
Updated
This page is the file content/docs/en/v1/assets/hosts.mdx