Every application offers some sort of logging feature and different ways to configure it. It’s a cornerstone the software life-cycle from the moment the app is developed, tested, deployed, even more on a daily production usage and support. One characteristic of the logging process is for how much time do I need to keep my log files, in three words the retention period.
A common method to investigate for Active Directory authentication issues is inspecting logs and event viewer, it’s simple and effective. But it’s a reactive thinking and it isn’t unusual for me to check if all user credentials provided were correct, most of the time for a large number of users and that’s the reason why I wrote this simple (proactive) script to automate the testing process and the efficiency of an on-boarding process. It also works with local users, not just ActiveDirectory users.
Maintain good documentation, especially up-to-date and readable, it’s a very important requirement in every workplace. So why don’t focus some of the automation or scripting on this subject? Starting with a basic PowerShell script that generate a big part of it can be really precious, save time and bring value on a daily basis.
After the Duplicate Windows Server post this is its complementary for Linux.
Package managers and APT, YUM offer many ways to export selections of the software installed and the available documentation offer is so good that the best thing to do is just reference to official documentation.
RSAT Tools are usually considered system administrator’s best friend, offering access to servers directly from any workstation and SCCM for os/sw/updates deployments in enterprise and medium company is maybe even more!
When workloads increase or for testing purpose is a very common request to provision a server with the same specs of an existing one, a fresh installed clone.