Use PowerShell to get a list of the most recent entries in the event log and manipulate the list according to your specific needs. For instance, the below PowerShell command helps you find all of the sources that are represented in the 1000 most recent entries in the System event log.
The Windows 8 and Windows Server 2012 PowerShell cmdlet Get-WindowsEdition allows you to get the current edition of the operating system running on your computer.
If you have file servers, you most likely run user quotas. Not running quotas would allow users to quickly fill up the entire drive.
I didn’t really like the reporting features on the server so with a bit of PowerShell – I extended it:
Because AD can be extended in so many ways (more on that soon!), you can store a ton of data for easy retrieval. For example, we write the last logged on user to the Managed By attribute in AD. This allows us to find out what computers a user has used.
A “regular” topic on this blog will be simple PowerShell scripts to help with your Active Directory maintenance. Often, you may need to add an additional computer to an OU. You will almost always want this new computer to have the same group membership as a computer in that existing OU.
Still creating accounts by hand? Yeah – we just got out of that boat! If you would like to automate your account creation – here is a sample script you can use!
The faster things become – the faster we want things to become.
For example – PowerShell. On my machine, it takes about 5-6 seconds to be fully functional. Because I link PowerShell scripts into certain MMCs, starting PowerShell quickly is very important to me!
If you use home folders and/or folder redirection, you probably are wasting some space! When a user in AD is deleted, their documents will still remain on your server. To reclaim this space, we can use a very simply PowerShell script:
Every environment has to deal with software upgrades. Sometimes, these upgrades can get messy. For example, we recently centralized on Adobe Photoshop Elements 11. We previously used a mixture of version 2, 4, and 6. Every site (22 in total) had software deployment security groups for each version. We needed a way to compare members between the new security groups (including nested groups) and the old groups.