It is often helpful to know the status of a server reboot before you start any install or update operations. It can help you plan the outage better. We collect this data for you.
Collector table: Collector.PendingReboots
Jobs: CollectorPendingReboots<SLA>
Alerts: No built-in alerts.
Collector.PendingReboots
| Name | DataType | NULL | Description |
| ID | bigint | NOT NULL | Table ID |
| ExecutionDateTime | datetime | NULL | Date of the collection. |
| InstanceID | bigint | NULL | ID of the server as found in dbo.Servers. |
| CBServicing | bit | NULL | Reboot is caused by CB Servicing. For info on CB servicing check here: Understanding Component-Based Servicing - Microsoft Community Hub |
| WindowsUpdate | bit | NULL | Reboot is caused by Windows Update. |
| ComputerRename | bit | NULL | Reboot is caused by renaming the computer. |
| FileRename | bit | NULL | Reboot is caused by a pending file rename operation. |
| DomainJoin | bit | NULL | Reboot is caused by joining a domain. |
| Reboot | bit | NULL | The computer needs a reboot. This makes it easier to report on cause you can just query WHERE Reboot = 1. |
| ActiveServerName | varchar(100) | NULL | Current servername. |
| ServerName | varchar(100) | NULL | New name of the server after the reboot. |
| FileRenameValue | NVARCHAR(2000) | NULL | New filename after reboot. |