Skip to main content

Powershell and WMI to calculate the Windows server uptime

Use the following PowerShell commands to find out how long the server has been up for since the last restart.

PS C:\> $wmi = Get-WmiObject -Class Win32_OperatingSystem
PS C:\> $wmi.ConvertToDateTime($wmi.LocalDateTime) –
$wmi.ConvertToDateTime($wmi.LastBootUpTime)

To display the uptime in formatted output, use the following commands:

PS C:\Windows\system32> $name = "bcdpprd01"
PS C:\Windows\system32> $wmi = Get-WmiObject -Class win32_operatingsystem -ComputerName $name
PS C:\Windows\system32> $uptime = $wmi.ConvertToDateTime($wmi.LocalDateTime) - $wmi.ConvertToDateTime($wmi.LastBootUpTime)
PS C:\Windows\system32> Write-Output "Uptime for $($name): $($uptime.Days) Day(s), $($uptime.hours) Hour(s), $($uptime.minutes) Minute(s), $($uptime.seconds) Second(s)"

Output will be displayed as:

Uptime for bcdpprd01: 0 Day(s), 15 Hour(s), 2 Minute(s), 4 Second(s)

To check the uptime for multiple Windows Servers, create a text file with a list of servers and create a Powershell script with a loop construct like foreach. The beauty of the following script is that it does not require uptime.exe to check uptime for any Windows Server(s).

$servers = Get-Content "C:\Nirav Store\servers.txt"
@(
foreach ($server in $servers)
{
if ( Test-Connection -ComputerName $server -Count 1 -ErrorAction SilentlyContinue )
{
$wmi = Get-WmiObject -Class win32_operatingsystem -ComputerName $server

$uptime = $wmi.ConvertToDateTime($wmi.LocalDateTime) - $wmi.ConvertToDateTime($wmi.LastBootUpTime)

Write-Output "Uptime for $($server): $($uptime.Days) Day(s), $($uptime.hours) Hour(s), $($uptime.minutes) Minute(s), $($uptime.seconds) Second(s)"
}
Else
{
Write-output "$server is not pingable."
}
}
) | Out-file -FilePath "c:\Nirav Store\results.txt"


If you do not want to redirect the output to a text file, do not pipe the output to a text file, which means, omit “| Out-file -FilePath "c:\Nirav Store\results.txt"”.

Comments

Post a Comment

Popular posts from this blog

Microsoft Azure Administrator (AZ-104) Course in Hindi

 Below in the link for the YouTube Video series for the Microsoft Azure Administrator (AZ-104) course in Hindi. https://www.youtube.com/watch?v=fqnsqJoWyjM This video is the first video in this series teaching you the Microsoft Azure Administrator (AZ-104) course in Hindi. I hope, you will enjoy this series, and I am sure that it will help you prepare for your Microsoft Azure Administrator (AZ-104) certification.  If you are enjoying my videos, please like and share them. Please also subscribe to my channel to get notified about the new videos that I publish. Thank you, Nirav Soni
Post a Comment
Read more

Working with Server Core machine

Before I talk about the Server Core, I would, first of all, list the editions of Windows Server 2012 R2. There are 4 editions in Windows Server 2012 R2. Data Center Standard Essentials Foundation They can be installed with two states - either GUI or without GUI i.e. Server Core. Actually, there's also a third state here and it's kind of the middle ground between Server Core and Server with the GUI and that is the Minimal Server Interface. Server Core is being installed mostly for Domain Controllers, DHCP, Hyper-V and DNS. Server Core only has Command Line and PowerShell. All of those user interface elements that you're used to in Server with GUI like the Microsoft Management Console, Server Manager, Explorer, all of those things are gone. The whole idea here is that it contains a much smaller footprint. It's actually four gigabytes smaller than server with a GUI. This is going to reduce the potential attack surface too. So, it's smaller and more secure....
Post a Comment
Read more

Setup Wireshark capturing for a remote Windows server

Many times, while working as a Systems Administrator providing support for the Windows or Linux Infrastructure, you come across some issues where you may suspect that those issues might be causing on some server(s) due to network related issues. It might be a DNS related issues where DNS queries do not resolve some times for some unknown reason or it could be a case where remote user who establishes a VPN connection and assume that his/her domain user password is about to expire soon and he or she needs to reset the password over VPN connection, but password cannot be reset because the TCP port 464 is blocked. These are just some examples of the incidents when you would think to capture network traffic on some servers to find the root cause. Below, you will find the step-by-step instructions showing you how you can use the Wireshark to capture the network traffic for a remote server. You can capture the network traffic from within the server too on which you have issues, but some t...
Post a Comment
Read more