Another quick Powershell script.
Even though it is already 2020, there are still enough servers with older disks capable of slowing down because of fragmentation.
So, how can we make sure we stay up to date on the fragmentation?
It has been a while, but more posts will come soon.
For now, an easier one that has more informational value than any actual use.
Ever felt like you wanted to know how old the workstation is of a customer? Or how long that old physical server has been standing there?
Now you might be able to figure that out using Powershell.
A small one this time. Whether it is Azure servers, customer servers or workstations ... there can be many reasons why a device can not be running 24/7 and reboots need to happen.
As an example, Azure servers that have been set to turn off after work hours and turn on in the morning. To realize this, you must have set rules or other automation tools to have it shut down and start up again. However, can you trust on it always working? Maybe the server has been online for the last few weeks without you noticing!
The script below checks how long a device has been active for and executes actions depending on the result.
Today I will be taking a look at a way of gathering basic information on HPE iLO's from the physical servers themselves.
Whether you work on servers remote or locally, the iLO (HPE Integrated Lights Out) is an important part of the extra security you have to make sure that you can manage the device regardless of whether it is on or off and allows for quick access to the health of the device.
Sometimes however, you are either logged in on the device and need some quick information or you are running scripts remotely on multiple servers to retrieve specific information.
There is an easy way to get some basic knowledge without having to log in to the iLO or even have to find the iLO.
This time a niche script for those customers that use terminal/remote desktop servers with User Profile Disks.
For people unsure about what User Profile Disks (UPD's) are. They are profile folders located on for example a file server that get loaded onto a terminal server the moment the user it belongs to logs in. These contain the user-data files (documents, appdata etc. etc.). This saves space and allows you to easier set limits to how big their profile is allowed to be.
However .. problems can arise at times and if a UPD gets stuck on one of the terminal servers while the user gets directed to a different one (giving that employee constant temporary profiles) it can get annoying real quick to find out where it is stuck (as usually the best way is to manually disconnect the disk from the server), especially when you have multiple servers with 10+ users on it.
Patrick Berger AKA Powershellder.
[ i ] Parallax section below. Click on the section below to upload image. Don't worry if it looks weird in the Weebly editor. It'll look normal on your published site.
To edit or delete your image, press the "toggle" button below. Then, hover over your image until a popup appears with the "edit" and "delete" options. If you don't want a white content section, leave it blank. It will disappear on your live website.