MSE Blogs

Exchange Group Calendar

Exchange Group Calendar is a nifty little application which provides easy collaboration.
. Nothing to install on the workstations.. Automatic instant processing of new, changed or deleted items in users personal calendars.. Real time processing without synchronisation problems.. Works with calendars from Outlook / Web Access / Entourage / BES / PDA …. Native Exchange Server and Active Directory integration using only the power of Exchange server.. Safe server processing control (com+). Full native Outlook / Exchange resync when disconnected laptop users reconnect.  . 3 years of free phone/email support and free updates. No yearly fees.. Reschedule appointments in the groupcalendars and the changes replicate back to the owner of the item.
3 steps, that’s all you need to use your sophisticated Exchange 2000 or 2003 server for what it was designed to do: Easy Collaboration. Some or all appointments created by the users in their personal calendars will instantly become visible in one or more Exchange Public Calendar folders. Fully automatic in real time! Exchange GroupCalendar enables you to create a large number of public GroupCalendars. They will display only the type of calendar information you need, formatted the way you want, with the exact user permissions your users need. Ever wanted to see all resources (meeting rooms, equipment) in one calendar? .. Now you can! Why Exchange GroupCalendar ?The program is none intrusive, doesn’t require another server  – as many other group calendar softwares require a SQL server, and it’s very small.&n

Microsoft Introduces Exchange Hosted Services

REDMOND, Wash. – March 30, 2006 – Microsoft Corp. today announced new branding, a new licensing model and the road map for Microsoft® Exchange Hosted Services (EHS), formerly known as FrontBridge Technologies Inc. EHS is composed of four distinct services including Hosted Filtering, Hosted Archive, Hosted Continuity and Hosted Encryption. These services offer cost-effective hosted solutions to help ensure the security and high availability of an organization’s messaging environment while satisfying internal policy and regulatory compliance requirements. In addition, Microsoft today unveiled a new per-user licensing model for all the services as well as road map details, including information about the upcoming EHS 5.3 release and the 6.x series of releases that will align with Exchange “12” availability. EHS is the latest addition to the Exchange Server solution portfolio and a key offering in Microsoft’s software as a service strategy.
“We’re driving to deliver world-class software any way customers choose,” said Steve Ballmer, chief executive officer of Microsoft. “Exchange Hosted Services will give customers more flexibility in how they deploy, manage and maintain technology.”
EHS Offerings
EHS helps reduce large upfront capital investment and free up IT resources, empowering companies to concentrate on areas most critical to their business. Operating over the Internet as a service without any hardware or software to install on premise, EHS enables organizations to better protect against e-mail-borne malware, satisfy retention requirements for compliance, encrypt data to Newsletter of March 2006

All those of you who already subscribe to our newsletter can ignore this post. To the rest of you I wanted to let you know the March edition just have been sent out to the approximately 45.000 Exchange admin’s who subscribe.
The newsletter is a relatively new initiative we launched back in January 2006, and it’s very similar to the newsletter which some of you might know from our sister site –, but instead covers the hottest news and tips on Exchange.
If you think this sounds interesting and want to check out the two previous editions until the March edition is archived too (which should be tomorrow), please see the archives page.

The Recipient Update Service and Linked Value Replication

Another great post on the MS team blog…Lately I’ve seen a lot of questions regarding the use of homeMDB in policy filters. I want to use this post to explain the reason that ExBPA warns about this, and hopefully clear up the confusion about how to address this.

Linked Value Replication is a feature that was added to Active Directory in Windows 2003. The point of LVR is that when a DN-linked attribute is changed, only the changes need to be replicated. For instance, instead of replicating a list of all members every time group membership is changed, it can replicate only the DNs that are added or deleted. LVR is also used for certain single-valued attributes, including homeMDB.
A quirk of LVR is that a replication packet contains two separate lists of changes – one list of regular attributes and then a separate list of linked attributes. When a DC receives such a replication packet, the non-linked attributes are applied first, with all non-linked attributes on the same object being applied in the same transaction. Once all non-linked attributes for all objects in the packet have been applied, it moves on to processing the linked attributes. This means that in a large replication packet, there can be a delay between the time the non-linked values are updated and the time the linked values are updated for the same object. This delay is what causes unexpected RUS behavior for the system policies and, possibly, recipient policies.

Let’s cover the system policies first. The point of the system policies are to stamp certain required attributes, such as homeMDB, on

Best of Q&A from Webcast: Exchange Server 2003 Tips, Tricks, and Shortcuts

Here’s the Q&A from the webcast Exchange Server 2003 – Tips, Tricks, and Shortcuts presented by Kevin Remde the other day.
Questions and Answers:
“Does all this apply to the Exchange Server included in my Small Business Version of Exchange?”
“I hear how we can use Windows SharePoint and/Or SharedPortal server to replace Public Folder. However, I can’t seem to find good resources to how we’re supposed to do this or get more information. So my question is where can I get more information about using SharePoint for replacing Public folder? Thanks.”
You make a very good point here. The reason you don’t see much documentation on this is because the majority of this is going to be exposed in SharePoint with Office System 12 (now named 2007 Office System) and not really in the current release of WSS / SPS.
“In regards to using Share Point to replace Public folders, ANY information you can point me to would be appreciated; I’m just planning the use of both SharePoint services and public folders (exclusively), it would be nice to perhaps utilize these features with 2k3 if possible.”
We don’t really have specific documents (that I’m aware of) that specifically talk about how to "replace" Exchange Public Folders with WSS / SPS. The thing to do is look at the features of WSS / SPS such as Discussion Lists, Shared Contacts, etc. Remember that even with the next release of SPS, there is not an exact 1 to 1 "replacement" feature for PF usage – depending on what you are doing in PFs. Here’s a link to the

Supporting the Windows Mobile devices in your Exchange Server 2003 Mobile Messaging environment

Alright so you have already deployed Windows Mobile devices in your Exchange Server 2003 mobile messaging environment, and now you have one user after the other contacting the IT department with all sorts of device related issues (who said certificates ) If you can say yes to this you might want to have a closer look a Pocket Controller-Enterprise from SOTI inc. This brilliant product makes it, among many other things, possible to remote the Windows Mobile devices in your organization from a desktop PC (even over GPRS!). Is that cool or what?

Resolving MMC 3.0 errors when installing Exchange 12 CTP release

Are you experiencing problems installing the Exchange "12" CTP release? More specifically are you getting the below error message during setup?
"Exchange Server ’12’ requires Microsoft Management Console 3.0."
Then chances are you have installed the RTM version of the MMC 3.0 instead of the MMC RC1 release.In order to fix this problem see this post by Nino Bilic over at the MS Exchange team blog.

Fix available to alleviate event ID 9548

This is great news! Finally a fix for the infamous 9548 event which shows up in the application log, when disabling a mailbox-enabled user account.
No doubt many of you are familiar with the event commonly seen in application logs of Exchange 2000 and 2003 servers, MSExchangeIS event 9548, indicating that the information store came across a disabled user who is missing the msExchMasterAccountSid attribute while processing some various task.  There are many KB articles associated with this event, such as 291151, 326990, 278966, 328880, 316047, and possibly more.  There have also been countless support cases where this design was at least a contributing factor.  Almost every application log from an Exchange 2000 or 2003 server ever seen has likely been littered with 9548 events, to the point where it has become an annoyance event.  For additional information on the event and the related information, I suggest reading this article:

A CDCR (Critical Design Change Request) was accepted last year to resolve the issue without having to run tools or scripts, and the first version of this fix was released last week. The KB article is 903158.

The problem was that a decision was made during the development of Exchange 2000 that every disabled user account with a mailbox had to have the msExchMasterAccountSid attribute. This is because in order for a mailbox to function within the store, a SID must be associated with the mailbox. The logic worked like this:

1. If the user account associated w

Scroll to Top