I'm a problem control engineer on the PSS Escalation Services team. My team is the primary escalation point for the most critical technical situations for Exchange. If a very complex transport issue is encountered, its my job to lay hands and pray on it. I joined Microsoft pretty much after I was allowed to graduate. I graduated from Morgan State University with a computer information science degree and I'm also a product of the Harvard Business School SVMP. While in college...

I first touched Exchange 4.0 Beta 2 (as a customer) and saw the future of reliable mail delivery, then never looked back. I’ve been with Microsoft for about 9 years, spending most of that time working in “the field” (as a pre-sales technical specialist, covering messaging, collaboration & mobility technologies) before transferring into the Exchange product group as a Program Manager, running the Technology Adoption Program for future releases of Exchange...

Now - this is one of those things that should be easy and obvious. How do you figure out what version (or build) a specific MMC snap-in is? For example - how do you find out if the ADC management MMC snap-in or ESM MMC snap-in have been updated to SP3 or some other build? Why would you ever want to know anyway? Well, there were some issues that have been fixed in Exchange MMC snap-ins too. For example - you do not want to use Exchange 2000 ESM straight off the CD to change...

Hi! I’m currently a Senior Program Manager on the Exchange Team. I’ve been working on the Exchange product at Microsoft for over 10 years in various roles. In that time, my focus has been on performance, scalability, capacity planning, and deployment going all the way back to Exchange 2000. I’ve also been heavily engaged in the initial architecture and deployment of some of our large online hosted services. My current work on the Exchange Customer Experience...

It is possible while installing the Active Directory Connector (ADC), or while running an Exchange setup Forestprep action, to be greeted with this incredibly generic error message: Extending the schema in the Active Directory failed.  Please consult the error log LDIF.ERR in your TEMP directory. When presented with this error message, you might dutifully go off to find yourr LDIF.ERR log, as directed, and find nothing of the sort present in your temp directory.  So now...

I'm a tester in the Exchange Core team, have been in Interop for the past 5 years using all the flavors of Outlook and other clients to test Exchange. Done lots of automation. I owned calendaring and free/busy for a very long time, worked with the Outlook team during the Exchange 2003/Outlook 2003 ship cycle, and love to talk about Exchange in areas I know well.

As companies adopt Outlook 2003 cached mode for their users, the Offline Address Book ( OAB ) becomes increasingly important. When Outlook 2003 users open the GAL or use name resolution, the OAB is used instead of making requests to a Global Catalog server. The OAB itself consists of a set of .OAB files which are attached to a message object and stored in a special public folder (commonly called a system folder). The size of these files will vary depending on how many mail-enabled...

I am a Program manager on the System Management team in the Exchange product group. Previous to becoming a PM I worked in PSS as a support professional, doing what else, supporting Exchange. In support I did everything from disaster recovery to deployment to directory integration issues and so on... I also supported other areas that don't begin with "D" but you get the gist. I'm currently involved in the planning phases for a future release of Exchange but have background and...

I am a Program Manager in the Exchange Customer Experience team and work on various programs that aim to improve the quality and capabilities of Exchange Server through customer connection and understanding. I’ve been in Exchange for about 6 years and have worked extensively on customer touch programs, validating Exchange deployment scenarios. Prior to that, I was a Consultant at PricewaterhouseCoopers in their Package Selection and Implementation Service line.

I've been at Microsoft for more than 10 years, first as an editor in PSS and Exchange UE, and now as a content release manager for the Exchange UE team.