I have a bunch of swag and I'd like to find it a good home. Some of it is fun new stuff (Exchange Communities "Road Warrior" kits (including mini-USB mouse etc) and a nifty one-handed stapler/tape dispenser), the rest is mainly legacy gear [oops I mean vintage ] from past releases - Exchange 2000 and 2003 t-shirts, jackets, other tchotchke's. I thought I'd check if any Exchange user groups would like small care packages of this swag for a future meeting. In order to be eligible for this, you must

To try help local Exchange User Groups, we'll have a few posts related to the subject. We want to help build stronger Exchange community! You are invited to attend the first ever Austin Exchange User Group Meeting! Are you interested in learning more about Microsoft Exchange Server? Would you like to meet some of the local Microsoft Exchange MVP's? We will be holding the first ever Austin Exchange User Group meeting. Join us for a lively discussion and an opportunity to network with peers. During

Someone asked the following, so I thought I would try and address the issue as I think it is one that is commonly misunderstood: Could you enlighten us on what happens when an Outlook user uses the permissions tab on a folder to grant access to other users? It apparently isn't the same as when they use the Delegates. I found a script to dump the delegates, but I have users who are out of control assigning folder permissions! Setting Permissions on Folders So when an Outlook User uses the Permissions

CALL TO ACTION A change in Exchange permissioning behavior may impact mobile communications and other add-on applications for Exchange. Shared and resource mailboxes may also be affected. By evaluating in advance whether this change will impact your environment, you can take simple remediation steps to ensure that installation of a new Exchange update will not impact critical services. A script is available to help you identify accounts and applications in your environment that may be affected. EXECUTIVE

With Beta 2 approaching, Exchange "12" needed a name. I know the suspense has been killing everyone. Well the wait is finally over: Exchange Server 2007 If you keep hearing the team talk about "E12" , "12", or "Exchange 12" - please understand - it's all the same thing. It just takes a while for us to adjust. Thanks! - Terry Myerson

Seems like yesterday that Exchange 4.0 hit the market. In March of 1996 Exchange 4.0 was released. I thought I would give you a link for the geeks among you that have been along for the ride and for those that go even further back to ALL-IN-ONE, MailWorks, cc:Mail, IBM PROFS etc. ITPRO has a great look back if you're interested in taking a look back at the evolution of hardware, Exchange Clients, Mobile devices, OWA, etc. http://www.windowsitpro.com/Common/adforceimages/Decade_of_exchange.pdf It's

We've seen a few issues recently where members of DGs (Distribution Groups) in mixed-mode Exchange 200x and 5.5 seem to randomly and mysteriously disappear. We thought we'd share one known root-cause and also show you how to prevent the problem while doing your migration, if for whatever reason you are still running Exchange 5.5 =). One easy way to prevent this problem (and a few others) is to ALWAYS use the Exchange 2003 post SP1 cross-site mailbox migration wizard if you ever have to move mailboxes

Here is a great opportunity for few "right" customers. If you might be interested, please respond to "michael DOT liu AT microsoft DOT com" and I will set up a call with you to go through details. The Exchange team is currently recruiting our best global brand name customers with an interest in Unified Messaging or Mobility to participate in Fall advertising (Note: Only 4 Customers will be selected). The Exchange team would provide: - Resources to deploy Unified Messaging to 100 Exchange "12" mailboxes

Recently we have been seeing several issues in Support Services where Event ID 623 is being logged on the server. The symptoms include "Users unable to access their inbox", "Email backing up in the local delivery queue" and "Email awaiting directory lookup". Clients may also see emails stuck in the Outbox. Rebooting the server usually fixes the issue. In this blog, I have tried to explain what "Version Store" is and how to troubleshoot this issue. A transaction is a series of operations that are

Recently MSIT wanted to make some global changes to the retention time of public folders. In the past we had a global limit of 3 years retention on items in public folders. The plan was to change the default limit to 1 year, and then exempt folders as needed. But there were a couple of complications... After examining the public folder tree and gathering feedback from the user base, we found that about 30% of the public folder tree would need an exemption for one reason or another. About 100,000

This is my 4 th blog post on the subject of Exchange 2003 Auto Accept Agent. If you want to see previous posts, you can see them here: one , two and three . The listings of Mailboxes that are registered on any given server are currently homed in the SystemMailbox. These registrations are populated by running the RegisterMailbox.vbs script and are listed as GUID items under the StoreEvents/Internal folder of the SystemMailbox as mentioned earlier. The inbox of the resource mailbox permanently contains

Hi All, I thought I would introduce myself to the BLOG-O-Sphere, my name is Scott Roberts and I'm a Software Developer in Test for the Exchange Sustained Engineering team. One of my responsibilities on the Exchange team includes being part of a team that pushes out the update for Intelligent Message Filtering (IMF) via Microsoft Update (MU). This BLOG will cover a few of the areas that we seem to find customers having problems with when trying to get the latest IMF update via MU. By now, I hope all

If you are following Eileen's blog - you already know about this, but for you that don't... A few more Exchange 12 WebCasts are coming up. Mark your calendars! Here are the subjects: TechNet Webcast: Improvements to Calendaring in Exchange "12" (Level 300) Tuesday, April 18, 2006 11:30 A.M.-12:30 P.M. Pacific Time TechNet Webcast: Exchange "12" Management Shell and Scripting (Level 300) Thursday, April 20, 2006 11:30 A.M.-12:30 P.M. Pacific Time TechNet Webcast: The Improved Exchange System Manager

Introduction This is the first of a four part Web log where I will focus on the different server roles in Exchange 12 and their disk I/O characteristics. Over the next few months I'll be addressing other Exchange 12 storage concerns in three upcoming Web logs: Exchange 12 High Availability Storage Considerations This focuses on Exchange 12 features that increase availability, and hardware strategies you can use to increase fault tolerance. Exchange 12 Data Protection This focuses on the features

Be the first to know about upcoming Microsoft Betas! Register to receive updates on the Exchange "12" public beta via a customized Microsoft TechNet Flash Newsletter! Find out more here: http://www.microsoft.com/technet/prodtechnol/beta/preregister.mspx . - The Exchange Team

A while ago, I blogged about Exchange Server Profile Analyzer tool here . We now have some updates! We are pleased to announce the availability of the Exchange Server Profile Analyzer WR2.5. The new version can be downloaded from the Microsoft Download Center . List of enhancements included in EPA WR2.5: - Dumpster collection - EPA now includes message content from mailbox "dumpster" folders when calculating message frequencies. Dumpster folders contain deleted content which has not yet been purged

This release of ExPTA includes the following: 1. Perfmon data collection: C ollect performance data to log file or analyze previously collected logs. ExPTA can collect for durations between 5 minutes to 8 hours. Collection works remotely. Data is analyzed in 20 minute time ranges, and results are grouped by the time in which the problem occurred. You can analyze logs previously collected by ExPTA or via perfmon. ExPTA will expect that the performance counters listed below are included in any log

We wanted to announce the new major build of ExBPA that we released today: v2.6 (U.S. English). We did a lot of work to improve usability of the tool in this release. Here are the major differences and improvements that we have made since ExBPA v2.5: 1. Tabbed reporting interface instead of a drop-down control. Viewing reports is now much more intuitive with this cool reporting structure. 2. Scan types are presented through radio buttons, so the different scan types available are much more obvious.

Background Exchange 2003 introduced the Always Up To Date notification feature (AUTD) that kept devices up to date by sending SMS triggers to the device. The triggers were sent from the enterprise as SMTP messages to the SMTP front end at the mobile operator. They were then sent through the SMS gateway as SMS messages to the device. This approach had some limitations since not all mobile operators did the SMTP to SMS conversion. Even when they did, there was latency involved with SMS messages and

I just posted instructions on how to create this OWA theme on my blog: In addition to the cow look, it also has a moooooooooooo for a new mail sound, and a cowbell for the reminder. Have fun! - KC Lemson