While many companies wait until Service Pack 1 to qualify and roll out any new Technologies, at Microsoft we put our technologies into production use at a very early stage. I have personally been running Windows Vista for the last 1 1/2 years, and my email has been coming through Exchange 2007 with Unified messaging for around 9 months. In doing so, we find bugs and usage scenarios that may not have otherwise been identified and addressed by the Product Teams.
One application that we use extensively within Microsoft to monitor our Servers (roughly 7,950 production servers, 2,700 pre-production servers, and another 50 development, staging, and test servers) is System Center Operations Manager 2007 (formerly Microsoft Operations Manager). Operations Manager 2007 RTM'd last Friday, and was officially announced at the Microsoft Management Summit.
To familiarize yourself with SCOM 2007, the following links will come in handy:
But back to my original thought... Microsoft has been running SCOM in production for quite a while now, and the "How Microsoft Does IT" team has put up a great White Paper, PowerPoint deck, and Webcast on the lessons learned from our internal implementation.
PingBack from http://www.mcseboard.de/windows-forum-ms-backoffice-31/system-center-operations-manager-2007-a-110867.html#post682875
At Microsoft, we have some product names that do not always roll off the tongue ;) The problem is compounded