Do you have what it takes to become a Microsoft Certified Master?
Great post about the Ranger no I mean Master program by Greg Taylor posted on the MSExchangeTeam blog.
Most of you know I been through it, and I can only agree with every single line in that post. It was a great experience!



Mursleen Ahmed Says:
December 3rd, 2008 at 3:38 am
MsExchange.org is the best site to update yourself in exchange
Kanta Prasad Says:
December 11th, 2008 at 8:47 am
Microsoft Certified Master: Exchange Server 2007:::::
• Five or more years of hands-on experience with Microsoft Exchange Server 2003: installing, configuring, and troubleshooting
• One or more years of hands-on experience with Microsoft Exchange Server 2007: installing, configuring, and troubleshooting
• A thorough understanding of Microsoft Exchange Server design and architecture
• A thorough understanding of Active Directory, Domain Name System (DNS), and other core network services related to Exchange Server
• Ability to speak, understand, and write fluent English
Successful completion of the following exams and certifications
• Exam 70-236: TS: Exchange Server 2007, Configuring
• Exam 70-237: PRO: Designing Messaging Solutions with Microsoft Exchange Server 2007
• Exam 70-238: PRO: Deploying Messaging Solutions with Microsoft Exchange Server 2007
Additionally required:
• Microsoft Certified Systems Engineer (MCSE) on Windows Server 2003
or
Exam 70-640: TS: Windows Server 2008 Active Directory, Configuring
Kanta Prasad Says:
December 11th, 2008 at 8:48 am
This Website is realy the God Father for those who realy want to update and keep theirself up to date.
John "Where's my bailout?" Dough Says:
December 11th, 2008 at 5:01 pm
I bet Microsoft could not get the naming rights for “Microsoft Certified Jedi Master” or
if not politically correct to have the title “Microsoft Certified Exchange Guru”.
Novell has the product name “Zen Works” so “Microsoft Certified Zen Master” is no go.
I also claim to be a cyborg and disagree with the terms of use which discriminate against robots.
John Dough