Before you automate
As significant chunk of my work involves automation using PowerShell. I speak as an Infrastructure specialist, when I say that automation has gained a lot of traction. Automation has several benefits, such as: Reduction in human errors. Higher speed. Higher efficiency. Reduction in effort. No boring tasks. This is all good, shiny. However, can everything be automated? Here are some things you should consider before you automate anything, whether it is an odd user account termination process, or disaster recovery of your datacenter.
Service Status Monitoring using PowerShell
PowerShell is a blessing for Windows administrators. With the level of reach that PowerShell has in Windows, there is hardly anything in Windows administration that cannot be achieved using PowerShell. Recently, a colleague requested for a script that could help them monitor a set of services on a set of computers. They wanted the script to run every so many minutes, check if some specific services are running on a specified set of servers, and notify them if a service wasn’t running.
Removing Chrome data (or anything) from Citrix profiles
Citrix User Profile Management (or UPM) is used in many environments to ensure that users' data is uniform across the entire Citrix infrastructure. This way, a user can access his work anywhere. Citrix UPM handles this by synchronising users' profiles using the UPM share, which can be hosted on a file server. However, there is a drawback to this: data like browser cache are synchronised across the environment as well, along with user profile data.
Get a server health status report for multiple servers
As administrators, we juggle multiple servers at a time. Hardly do we deal only with a handful servers. Imagine a situation where you use SCCM to patch your servers, and that the patching is completely automated using an automatic deployment rule and a maintenance window. Chances are, you are patching seventy servers at a time. Unattended. This is a dream-come-true for many environments that have thousands of servers. However, it is also true that every good administrator wants to ensure their servers are up and running healthy, after the patching process.
Distribution Group clean-up using PowerShell
One of the downsides of old environments is the scope (and necessity) for clean-up. It often happens that there are more groups in an environment than users. And it is certainly not uncommon. In today’s post, we look at a small distribution group clean-up project in Microsoft Exchange. How to go about the project Safe clean-up Address DL redundancy Further clean-up Summing up I once embarked on such a project in an environment that had over three thousand groups, but only two thousand users.