Uptime Monitor

🍻Script Share

Here is a script I wrote a couple years ago. I just added an information section to the top. It's written to check the uptime of an endpoint. If it's been on for over 48 hours, it will reboot automatically. It doesn't give them user an option to say no, just does it. I run this in the middle of the night, so I don't need an option to say no. Would anyone like me to add that option?

<#
.SYNOPSIS
    Checks system uptime and reboots if exceeds 48 hours.

.DESCRIPTION
    This script monitors the system uptime and automatically reboots the computer
    if it has been running for more than 48 hours.

.AUTHOR
    Fred Claus

.DATE
    September 2, 2023
#>

# Get the system uptime
$uptime = (Get-CimInstance -ClassName Win32_OperatingSystem).LastBootUpTime

# Calculate the time difference between now and the last boot time
$uptimeDifference = (Get-Date) - $uptime

# Define the threshold (48 hours)
$threshold = New-TimeSpan -Hours 48

# Display current uptime
Write-Host "Current uptime: $($uptimeDifference.Days) days, $($uptimeDifference.Hours) hours, $($uptimeDifference.Minutes) minutes"

# Check if the uptime exceeds the threshold
if ($uptimeDifference -gt $threshold) {
    Write-Host "The system has been running for more than 48 hours. Rebooting..." -ForegroundColor Yellow
    
    # Log the reboot action
    Write-EventLog -LogName System -Source "User32" -EventId 1074 -EntryType Information -Message "System reboot initiated due to uptime exceeding 48 hours." -ErrorAction SilentlyContinue
    
    # Reboot the system with a 30-second warning
    shutdown /r /t 30 /c "System uptime exceeded 48 hours. Rebooting in 30 seconds..."
} else {
    Write-Host "The system has been running for less than 48 hours. No action needed." -ForegroundColor Green
}

<#
.SYNOPSIS
    Checks system uptime and reboots if exceeds 48 hours.

.DESCRIPTION
    This script monitors the system uptime and automatically reboots the computer
    if it has been running for more than 48 hours.

.AUTHOR
    Fred Claus

.DATE
    September 2, 2023
#>

# Get the system uptime
$uptime = (Get-CimInstance -ClassName Win32_OperatingSystem).LastBootUpTime

# Calculate the time difference between now and the last boot time
$uptimeDifference = (Get-Date) - $uptime

# Define the threshold (48 hours)
$threshold = New-TimeSpan -Hours 48

# Display current uptime
Write-Host "Current uptime: $($uptimeDifference.Days) days, $($uptimeDifference.Hours) hours, $($uptimeDifference.Minutes) minutes"

# Check if the uptime exceeds the threshold
if ($uptimeDifference -gt $threshold) {
    Write-Host "The system has been running for more than 48 hours. Rebooting..." -ForegroundColor Yellow
    
    # Log the reboot action
    Write-EventLog -LogName System -Source "User32" -EventId 1074 -EntryType Information -Message "System reboot initiated due to uptime exceeding 48 hours." -ErrorAction SilentlyContinue
    
    # Reboot the system with a 30-second warning
    shutdown /r /t 30 /c "System uptime exceeded 48 hours. Rebooting in 30 seconds..."
} else {
    Write-Host "The system has been running for less than 48 hours. No action needed." -ForegroundColor Green
}

Gorelo•6mo ago•

1 reply

DigitalDoctor

Uptime Monitor

🍻Script Share

<#
.SYNOPSIS
    Checks system uptime and reboots if exceeds 48 hours.

.DESCRIPTION
    This script monitors the system uptime and automatically reboots the computer
    if it has been running for more than 48 hours.

.AUTHOR
    Fred Claus

.DATE
    September 2, 2023
#>

# Get the system uptime
$uptime = (Get-CimInstance -ClassName Win32_OperatingSystem).LastBootUpTime

# Calculate the time difference between now and the last boot time
$uptimeDifference = (Get-Date) - $uptime

# Define the threshold (48 hours)
$threshold = New-TimeSpan -Hours 48

# Display current uptime
Write-Host "Current uptime: $($uptimeDifference.Days) days, $($uptimeDifference.Hours) hours, $($uptimeDifference.Minutes) minutes"

# Check if the uptime exceeds the threshold
if ($uptimeDifference -gt $threshold) {
    Write-Host "The system has been running for more than 48 hours. Rebooting..." -ForegroundColor Yellow
    
    # Log the reboot action
    Write-EventLog -LogName System -Source "User32" -EventId 1074 -EntryType Information -Message "System reboot initiated due to uptime exceeding 48 hours." -ErrorAction SilentlyContinue
    
    # Reboot the system with a 30-second warning
    shutdown /r /t 30 /c "System uptime exceeded 48 hours. Rebooting in 30 seconds..."
} else {
    Write-Host "The system has been running for less than 48 hours. No action needed." -ForegroundColor Green
}

<#
.SYNOPSIS
    Checks system uptime and reboots if exceeds 48 hours.

.DESCRIPTION
    This script monitors the system uptime and automatically reboots the computer
    if it has been running for more than 48 hours.

.AUTHOR
    Fred Claus

.DATE
    September 2, 2023
#>

# Get the system uptime
$uptime = (Get-CimInstance -ClassName Win32_OperatingSystem).LastBootUpTime

# Calculate the time difference between now and the last boot time
$uptimeDifference = (Get-Date) - $uptime

# Define the threshold (48 hours)
$threshold = New-TimeSpan -Hours 48

# Display current uptime
Write-Host "Current uptime: $($uptimeDifference.Days) days, $($uptimeDifference.Hours) hours, $($uptimeDifference.Minutes) minutes"

# Check if the uptime exceeds the threshold
if ($uptimeDifference -gt $threshold) {
    Write-Host "The system has been running for more than 48 hours. Rebooting..." -ForegroundColor Yellow
    
    # Log the reboot action
    Write-EventLog -LogName System -Source "User32" -EventId 1074 -EntryType Information -Message "System reboot initiated due to uptime exceeding 48 hours." -ErrorAction SilentlyContinue
    
    # Reboot the system with a 30-second warning
    shutdown /r /t 30 /c "System uptime exceeded 48 hours. Rebooting in 30 seconds..."
} else {
    Write-Host "The system has been running for less than 48 hours. No action needed." -ForegroundColor Green
}

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Gorelo

538 Members

Join

Uptime Monitor

Uptime Monitor

Continue the conversation

Gorelo

Continue the conversation

Gorelo

Similar Threads