rom Steve Goodman:

Other links:

In Exchange 2010 there is actually somewhere to publish these settings – and once configured your documentation won’t need to be updated if the server details change. You’ll find these settings by logging into OWA, and choosing Options. The link ”Settings for POP, IMAP, and SMTP access…” should be shown on the default ”My Account” page:

By default, nothing will be listed if you click the link:


To configure these links, it’s a fairly straightforward process. Before you begin, you need to know what the settings should be and in the case of the SMTP settings, which receive connector on which Hub Transport this relates to.

First, you configure the Client Access servers for the POP and IMAP settings, using the Set-POPSettings and Set-IMAPSettings cmdlets with the -ExternalConnectionSettings parameter.

For each protocol you specify a colon-separated list of values for the ExternalConnectionSettings. For POP3 with TLS, this might be ”” or POP3 with SSL might be ””. IMAP with TLS might be ”” and IMAP with SSL might be ””.

Here’s a quick example of the commands against my test setup:

Set-POPSettings -ExternalConnectionSettings "" 
Set-IMAPSettings -ExternalConnectionSettings ""

It’s important to remember, you need to run the command on all Client Access servers users will access.

Next, you need to allow the receive connector that you want ”published” to advertise it’s settings. You do this with the Set-ReceiveConnector cmdlet specifying the -AdvertiseClientSettings:$true parameter and value.

In my example, I want to advertise the port 587 ”client” receive connector on my Hub Transport server:

Set-ReceiveConnector -Identity "hubtransport\Client HUBTRANSPORT" -AdvertiseClientSettings:$true

Finally, run iisreset to restart IIS on each Client Access Server, the log back into OWA (well, ECP) and test the ”Settings for POP, IMAP, and SMTP access…”  link again. It should now show the settings specified:

For further reading check out Set-IMAPSettings, Set-POPSettings and Set-ReceiveConnector.

(Just a footnote- thanks to Jag at Microsoft for providing this information)

Tagged with:

This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool.

Site folder server deleted
The site-wide public folder database for administrative group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’ has been deleted. Current public folder store: ‘CN=Public Folder\0ADEL:7b0fc218-05b2-4eae-9660-bbdd01f7e395,CN=Deleted Objects,CN=Configuration,DC=uw,DC=lu,DC=se’.


The siteFolderServer attribute represents the Distinguished Name (DN) of the Public Folder store that is responsible for hosting the site folders (normally the first server in the site or administrative group).

By default, the Site Folder Server is the first server that is installed in the administrative group. The public folder store on this server is the default location of the free/busy folders and offline address book folders for the administrative group. If you remove or decommission this server without replicating these folders to another server and designating that server as the offline address book server, Microsoft Office Outlook® 2003 users will see problems with the offline address book and with free/busy data.

Aa996485.Caution(en-us,EXCHG.80).gif Caution:
If you incorrectly modify the attributes of Active Directory objects when you use Active Directory Service Interfaces (ADSI) Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.

To correct this error

  1. Open an Active Directory editor, such as ADSI Edit.
  2. Locate the public folder information store that you want to designate as the Site Folder Server. For Exchange Server 2000 through Exchange Server 2007, expand the following nodes in the Configuration container:
    CN=Configuration,DC=<DomainName>,DC=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=<AdministrativeGroupName> CN=Servers, CN=<ServerName>, CN=InformationStore, CN=<StorageGroupName>
    For Exchange Server 2010, expand the following nodes in the Configuration container:
    CN=Configuration,DC=<DomainName>,DC=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Databases
  3. In the right pane, right-click CN=<PublicFolderStoreName>, and then click Properties.
  4. In the Attributes field, scroll down and select the distinguishedName attribute.
  5. Click Edit, and then copy the entire attribute to the Clipboard.
  6. Expand the Configuration container, and then expand CN=Configuration,CN=<DomainName>,CN=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups
  7. Right-click the administrative group you want to modify, and then click Properties.
  8. In the Attributes field, scroll down and select the siteFolderServer attribute.
  9. Click Edit, and then paste the value for the distinguishedName attribute into the Value field.
  10. Double-check the contents of the Value field to ensure the paste was performed correctly, and then click OK to save the change.
  11. Click OK to close the Administrative Group properties.
  12. Exit the Active Directory editor and restart the Microsoft Exchange Server Information Store service on all Exchange Server computers in the site for the change to take effect.

For more information about re-creating system folders and resetting the Site
Folder Server, see the following Microsoft Knowledge Base articles:

Tagged with:

Clarify: You want to show mail address instead of display name in the “To”, “From” and “CC” fields

Explanation: When messages arrive to exchange, server will resolve the mail address to those users who exist in the directory, there isn’t a way to change the behavior which is expected by design

Workaround (For Exchange 2003):

Notes: Not recommend [See KB 828770], it also causes all messages through modified SMTP Virtual Server to show mail address instead of display name

  1. Start Registry Editor [Set on server which your mailbox stays]
  2. Locate or create the following key in the registry
    Notes: You might need to create the ”Parameters” key and the <2> key as well, <2> is the SMTP virtual server number
  3. Add the following registry value: Name: ResolveP2 Type: REG_DWORD Value: 0
  4. Also enable ”allow anonymous senders” on the SMTP Virtual Server
    a.  ESM->AG->Server->ServerName->Protocols->SMTP->SMTPVirtualServerName’s Properties
    b. “Access” tab->”Authentication” button->check “allow anonymous senders”

Notes: For Exchange Server 2007, name resolution is forced for MAPI clients, no way to disable

Here’s a 3rd-party tool which can achieve the function you want: WhichAddress

After migrating your Exchange server (I’ve seen this in transition to exchange 2007 and 2010) the PublicFolderDatabase for your OfflineAddressBook is still pointing to the old servers public folder store.

When you run the get-OfflineAddressBook | fl command in a exchange management shell on your new server, you get a result like this:

At Server you see the new servername and the PublicFolderDatabase is still pointing to your old server. Public folder replica’s and offline address book generation server are already moved to the new server.

Solution: I found if you do the following steps you can change the PublicFolderDatabase.
First start adsiedit and browse to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Address Lists Container, CN=Offline Address Lists and open the properties of CN=Default Offline Address List

Look for the siteFolderServer attribute, here you will see the old public folder store. Choose clear and close with ok, now you may close adsiedit.

Now go to the exchange management console, Organization Configuration, Mailbox, Offline Address Book open the properties of the Default Offline Address List and go to the tab distribution.

Uncheck “Outlook version 2 and 3″ at client support and uncheck “Enable public folder distribution”. Make sure “Web-based distribution” is enabled. Choose apply and ok, then right click on Default Offline Address List and choose update. After that go back to properties and distribution and check “Outlook client support version 2 and 3″ and “Enable public folder distibution”. Again choose apply and ok and right click and choose update.

When you go back to the exchange management shell and repeat get-OfflineAddressBook | fl you now will see the public folder store on your new server.


Tagged with:


If you connect your iphone and sync with exchange you end up with fewer options for passcode lockout time.
Without exchange connection Apple makes it possible to choose up to 4 hours. With an exchange account setup it reduces to 15 min.

Solution: (

You can set how long it takes for the iPhone’s passcode lock to be enabled. The choices are immediately (every time you wake the iPhone), after 1 minute, 5 minutes, 15 minutes, 1 hour or 4 hours. However, starting with iPhone Software 3.1, if you are syncing with a Microsoft Exchange server for e-mail, contacts or calendar, you may find that you have fewer options. For example, here are two screen shots of the Require Passcode setting. The one on the left is from my iPhone; the one on the right is from another lawyer’s iPhone who does not work at my law firm. Both of us are using Exchange and both of us are running iPhone 3.1, but you can see that I have fewer options:

I am more limited because my law firm’s Exchange server imposes a ”maximum inactivity time lock” on mobile devices. (I believe that ours is set to 20 minutes, and when you combine the up to 5 minutes before an iPhone auto-locks plus up to 15 minutes for a passcode lock, that is a maximum of 20 minutes of inactivity to lock the iPhone.) Before iPhone Software 3.1, the iPhone did not pay attention to an Exchange Server’s maximum inactivity time lock. This was a security flaw, one that was pointed out to Apple by iPhone users at PepsiCo, Intel Corporation, Edward Jones and Agilent Technologies. When Apple fixed this issue in 3.1, it explained what it had done on this page and gave credit to the individuals at those companies who pointed out the flaw. So if you, too, are looking to become famous on an Apple security page, let them know if you find another security flaw.

Speaking of iPhones and Exchange servers, the following Exchange ActiveSync password policies are supported in iPhone Software 3.1:

  • Require a password
  • Minimum password length
  • Maximum failed password attempts
  • Require both numbers and letters in the password
  • Inactivity time in minutes
  • Allow or prohibit simple password
  • Password expiration
  • Password history
  • Minimum number of complex characters in password

Even if a company doesn’t use Exchange, a company can set these settings by using device profiles.

Tagged with:

Lync for Mac 2011 Released to Manufacturing

On 2011-10-05, in Exchange 2010, by Mattias Jönsson

Article at Unified Communications Group Team Blog by Kirk Gregersen

When we first announced Lync Server 2010 last November, we talked about our commitment to supporting multiple platforms and how over the course of 2011 you would see Lync become available for other platforms. Today, I’m excited to share with you today that Lync for Mac 2011 has been Released to Manufacturing, commonly referred to as RTM.

Starting in October, our Mac customers will be able to experience the integrated communications experience that Lync has become well known for. From the updated contact cards to the ability to set up Lync conferences from Outlook 2011 for Mac to enterprise voice features, Lync for Mac 2011 offers Mac users integrated functionality for presence, instant messaging, conferencing and voice and is designed to work with both Lync Server 2010 and Lync Online.

VIDEO: Lync for Mac quick tour

Lync for Mac 2011 is available to customers as a part of the Office for Mac 2011 Volume Licensing SKU, Office for Mac Standard 2011, or through many of Microsoft’s Licensing programs. Customers can also purchase the application as a standalone volume licensing SKU.

For more information on Lync for Mac 2011, please visit

Tagged with:

Announcing Exchange 2010 Service Pack 2

On 2011-10-05, in Exchange 2010, Mailserver, by Mattias Jönsson

The Exchange Team is pleased to announce that in the second half of calendar year 2011 we will be releasing Exchange Server 2010 Service Pack 2 (SP2) to our customers. With SP2, the following new features and capabilities will be included:

  • Outlook Web App (OWA) Mini
  • Cross-Site Silent Redirection for Outlook Web App
  • Hybrid Configuration Wizard
  • Address Book Policies
  • Customer Requested Fixes:

Read more about this at ”the exchange team blog”

Tagged with:

by Rajith Jose Enchiparambil on August 10, 2010

One more technical whitepaper from Microsoft. Enterprise IT organizations, including the Microsoft Information Technology (Microsoft IT) group, deal with service level agreements SLAs) and power users accustomed to high levels of performance, availability and responsiveness. The 180,000-plus users at Microsoft send over 15 million internal e-mail messages a day from more than 150 offices worldwide, as well as from home and while on the road.

This white paper is for business decision makers, technical decision makers and operations managers. It assumes that the reader has a working knowledge of Windows Server 2008, ctive Directory, Exchange 2010 and System Center Operations Manager.

Download the whitepaper here

Tagged with:

Some IMAP-clients (Thunderbird in some cases) have problem with corrupt attachments using Exchange IMAP.

One possible reason is how Exchange delivers MIME-message to users. In exchange 2003 you could set an option on IMAP – ”Fast message retrieval” and it makes IMAP answer faster to clients with MIME-messages. In Exchange 2010 this option is set thru powershell with Set-imapsettings and it is now called ”EnableExactRFC822Size”. When this is enabled it will give IMAP-clients an exact size of each MIME-message content and not an approximate size as default. Old IMAP-clients can not handle an approximate size of MIME messages and there for shows messages as corrupt. As Marek writes below: ”MS Exchange violates RFC and provides only approximate size of the message for ‘performance reasons'”.

A plot from technet and powershell-command ”set-imapsettings”.

Set-imapsetting -EnableExactRFC822Size $true|$false
The EnableExactRFC822Size parameter calculates the exact size of each MIME message that can be retrieved from the server. When you set this parameter to $true, the exact size of MIME messages stored on the Exchange server is available to POP3 or IMAP4 client programs that rely on knowing the exact size of each MIME message.
This parameter is set to $false by default. If you don’t set this option to $true, the size of each MIME message that the Exchange server returns to POP3 and IMAP4 client programs may be slightly different than the exact size of the message. Because setting this option to $true can negatively affect performance, you should only use this option if many of your users are using a client that requires knowing the exact size of MIME messages.

A post by Marek Vitek 2010-01-28
There are several reasons and also few possible solutions for solving this issue.
– MS Exchange violates RFC and provides only approximate size of the message for ”performance reasons”
– I saw also other mail servers providing incorrect RFC822.SIZE value

So sticking with this value is not a good idea. It is also discouraged by IETF author in RFC 2683 section 3.4.5.

– in Exchange disable ”Fast message retrieval” function/RFC violation. But it will have performance implications. (In exchange 2010 this is same as -EnableExactRFC822Size on set-imapsettings)
– follow RFC 2683 recommendations and in Thunderbird fix the code and use message size provided by ”FETCH RFC822.SIZE” command only for informational purposes. For message size validation and possibly truncation use e.g. size reported by ”FETCH RFC822” as it seems to be correct value all the time.

Thunderbird: E-mail attachments are corrupted and and images partially load

Tagged with:

Microsoft announced this week that starting in summer 2011, IT engineers and consultants all over the world will have an opportunity to earn MCM status on Microsoft Exchange Server 2010 by passing the required exams at one of many international testing centers. This makes the on-site training at Redmond optional. See the following link for details:

If you you want to learn even more about the MCM, you can read all about it here here. If you’re thinking about applying for the MCM program take a look at Neil Johnson’s MCM survivors guide and Brent Ozar’s blog series on the SQL MCM. Neil goes into great detail about the Exchange MCM, and Brent’s coverage of the SQL MCM is an interesting read (even for us Exchange guys). You’ll also want to keep an eye on The Master Blog for news and updates. Good luck!

Microsoft has recently created a great video highlighting the training experience you can expect when attending the Exchange MCM program. Watch the clip below to hear from MCM instructors and attendees as they discuss the program:

Tagged with: