The last session was on Exchange 2007 troubleshooting. Most of it was too techy to blog here, and primarily of interest only if we move to Exchange.
But they also covered off the general troubleshooting fundementals, these being (and I'm paraphrasing here):
Know your stuff;
Have a baseline, and proactively monitor systems to check for changes;
Think of the implications before you make a change.
We all know these things, but it's still good to be reminded occasionally.
Oh, and the other thing is that most of Exchange 2007 - and Windows 7 - advanced administration involved scripting in PowerShell. So, it's time to learn yet another scripting language!
Subscribe to:
Post Comments (Atom)
Posts
2 comments:
What about using things like IronPython? I guess if we're going to learn a scripting language, it might make sense to learn one with broader coverage.
True, but Powershell already has access to the object model for all of the Microsoft fleet - basically, it's the replacement for VBscript, but can do a lot more.
For example, most of the Exchange management comman line utilities (including the mailbox transfer / migration tools) are Powershell scripts.
Post a Comment