By Stephanie DeCamp Posted January 31, 2020
For most IT admins, the first question asked when troubleshooting either a server or an end user is simple: “When was the last time you rebooted?”
It’s a simple question that answers a lot, and the issue of uptime is especially critical with servers. Knowing if a server recently rebooted, crashed, or has been up for a long time helps determine further actions when every minute counts.
Value of Checking Your Last Reboot
Given the tools to know these things immediately, admins can much more efficiently manage their fleets of systems, be they Windows®, Mac®, or Linux®. And when it comes to resolving issues for a specific user and their device, having the most recent information about that device goes a long way.
It also helps to prevent issues in the first place, to get them figured out faster, and to meet auditing and compliance standards. And of course, rebooting systems on a regular basis is imperative when applying patches and updates. Making sure these go into effect saves time, frustration, and money.
User identities and access are the biggest factors in security risks for IT organizations today. User endpoints are often the gateway to critical data, so admins need the means to query those endpoints at a moment’s notice.
Checking Individual Systems for Last Reboot
It’s fairly simple to check each operating system for when it was last rebooted. All three have their own set-ups to do so, with command-line entry being the most common method.
First you’ll need to open up the Event Viewer and navigate to Windows Logs. From there you’ll go to the System log and filter it by Event ID 6006. This will indicate when the event log service was shut down, which is one of the last actions to take place prior to rebooting.
For Macs, you’ll open the Terminal and type “last reboot” into the command line, which will pull up the dates and times of the last few reboots on that system.
Similar to Macs, you can use the ‘“last reboot” command to display all of the dates and times of previous reboots for that system.
How Do I Check All Three OS Uptimes? (System-Agnostic)
Directory-as-a-Service® makes it quick and easy to see the uptime across your fleets when you enable the premium Systems Insights® feature. Upon confirmation of enablement, you can simply go to the Systems tab, select which one you wish to view, click Details, and expand the section. The first thing you’ll see listed is your uptime.
A Comprehensive, Centralized Solution
Your organization’s security is only as strong as its weakest link, so when you’re in charge of a hybrid environment and need to work across operating systems, it helps to have one verified tool that can access it all. Luckily, there’s a solution in JumpCloud® Directory-as-a-Service.
JumpCloud has many distinct advantages for the small- to medium-size business, especially when it comes to security. With its System Insights tool, admins can query hundreds of data points via the JumpCloud UI, PowerShell module, or the JumpCloud API.
This gives in-depth, system-level insights across your fleet. Updating every hour, it helps admins meet compliance and keep their IT environments secure and operational. It not only checks when a system was last rebooted, but can also query and track the other data points. This includes local accounts, browser extensions, applications, network configurations, and hundreds more.
To learn more about JumpCloud and Systems Insights, check out our product or Systems Insights page. You can also contact us for a free demo, or sign up to try it out for yourself. Your first 10 users are free forever.