I really really *love* my smartphone. I take it everywhere and do most of my email triage on it. I’m lost without it, so I was really pleased to see rumours of the next Smartphone appearing in Marcus’ blog this morning. Then to read that it’s going to have GPRS class 10. Oh Heaven…
Or do I wait for the C600? It would fit in my handbag (US=purse) more easily!
Oh, decisions, decisions…
I really wanted to highlight the time of this webcast again, as this management pack for Exchange puts all of the bells and whistles onto Exchange that the old Resource kit tools used to, back in the days of Exchange 4.0 and 5.0. Take time to have a look at just what you can pull out of the box to manage your Exchange environment, and this, coupled with the Exchange Best Practices Analyzer, really makes it simple and intuitive to manage your Exchange environment.
TechNet Webcast: Managing Exchange 2003 with MOM 2005: Better Together (Level 200)
Friday, March 25, 2005 – 9:30 AM – 11:00 AM Pacific Time
Chris Hallum, Program Manager, MOM, Microsoft
Learn how Microsoft Operations Manager (MOM) 2005 and the Exchange Server 2003 Management Pack for MOM 2005 can help improve the health and performance of Exchange Server 2003 through specialized, proactive monitoring and alerting. This webcast explores the wide range of valuable tools and knowledge contained in this Management Pack and shows how you can use them to identify, understand, and resolve IT health issues to keep Exchange running and your organization’s e-mails flowing.
Whenever I present at TechNet events I get questions on how to deploy the ADC so that the Exchange 5.5 Server coexists with AD. There is a comprehensive walkthrough in the Exchange Deployment guide showing how this is done, and I’ve also created a blogcast on configuring the ADC.
The Exchange team blog covers lots of extra information about the ADC, such as using SRS, extending the schema, troubleshooting NDR’s and looking at connection agreements so it’s a bit of a hot topic when you’re migrating from Exchange 5.5.
You can have a look at other blogcasts here:
Paul mailed me after my TechNet presentation to ask if we had any solutions for producing statistics for mailbox usage, size of mailboxes etc. He’d had a look around and had a look at Quest MessageStats but was asking if we had anything that would do this out of the box for Exchange 2003.
Well, we do have something out of the box, but it’s not the Exchange box. It’s the MOM box. There is an Exchange Server 2003 Management Pack for MOM 2000 SP1 which provides quite a few reports on Mailbox and folder sizes:
Top 100 Mailboxes by Size,
Top 100 Mailboxes by Message count,
Top Public folders by size,
Top 100 Public folders by message count,
Highest growth mailboxes,
Highest Growth Public Folders
There is also an Exchange Management pack for MOM 2005 available and also a comprehensive guide.
So its out of the box, or off the web – but we have something that will work for you Paul…
I received a mail from Ed today who had attended my TechNet session. He wanted to know if I had any ideas about the errors he was getting in his Exchange 2003 server.
Information Store (6116) First Storage Group: The database page read from the file “C:\Program Files\Exchsrvr\mdbdata\priv1.edb” at offset 1000951808 (0x000000003ba95000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 1049570905101168 (0x0003ba9444f71370) and the actual checksum was 1049572726996704 (0x0003ba94b18efee0). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://web.archive.org/web/20051210052402/http://www.microsoft.com/contentredirect.asp.
Hmmm. The giveaway here is the error 1018 code. Exchange has introduced an algorithm to help correct errors caused by a bit flip. A bit flip is a transient memory error where a single page in the database has flipped from a 1 to a 0 or vice versa, and causes an error. Even though a single -1018 error is unlikely to cause extensive data loss, -1018 errors are still cause for concern because a -1018 error is proof that your storage system failed to reliably store or retrieve data at least once.
1018, 1019 and 1022 errors should be monitored carefully with Exchange as they refer to file level damage to the Exchange database:
These articles help to understand the 1018, 1019 and 1022 database errors and talks about the new ECC included with Exchange 2003 SP1. There’s a useful webcast talking about SP1 here too……
This document outlines the steps you should take to upgrade from Microsoft Systems Management Server (SMS) 2003 to Microsoft SMS 2003 Service Pack 1 (SP1).
For a complete discussion about planning for an implementation or upgrade of SMS, especially if you are deploying a new installation of SMS 2003 SP1 rather than an upgrade, review the Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment guide, which is available for download from the SMS Product Documentation Web page.