I really like the PowerShell for Active Directory, that you find in Windows Server 2008 and above. I cut my teeth on PowerShell with Microsoft Exchange Server 2007, and love the ability to script almost everything – even if the script is just a bunch of repeated commands against a list in Excel, that’s copied and pasted.
I came across an annoying little issue today. Whether it be down to the default settings of Windows Server 2012, or one of the hardening settings of our corporate build, I don’t know, but it’s annoying either way.
My corporate provided laptop operating system is mandated at Windows XP. I regularly (90+% of every day) use it to remote control servers, and this is normally through RDP (I prefer RDP over vSphere client for Virtual Machines too).
A quick technical post!
Occasionally, I’m called upon to deal with minor issues for users of USB thumb drives, and I thought I’d pull together a few little tips and tricks here which help me get things sorted.
To begin, spend at least a week creating documentation for a procedure to install a complex messaging solution based on Microsoft Exchange 2010. Don’t bother saving it to a server or somewhere that’s backed up – it’s still just a work in progress. Save it to a nice folder on your computer desktop instead.
Yay, it’s time for another technical post!
I manage and am responsible for Active Directory for a number of customers, both public and private sector. Rather than searching my documentation to find the FSMO role holders, it’s easier to log on to a server and run “netdom query fsmo” in a command prompt.