Ignite 2019: Exchange & Related Sessions

ignite2019Note: If you are looking for the script to download Ignite contents, you can find it at the TechNet Gallery or Github.

It shouldn’t be a surprise to you, but this is the week of Ignite 2019 in Orlando, where Microsoft and other speakers will not only tell you about the latest and greatest, and how to implement recent products and use their technologies, but also draw more of the roadmap of things to come. Unfortunately, I won’t be attending Ignite (again), but similar to last year Microsoft will be live streaming keynotes, breakouts as well as theater sessions. So, you can watch stuff as it happens in the comfort of your own home or on-demand at a later time.

To access the catalog, including live streams, you can of course dive in the 1981 sessions located on the Ignite portal. Details on sessions, speakers etc. as well as filtering options are already present to help you pick what to watch, and recorded media will be added as it becomes available, including slidedecks.

For your convenience, I made a short list of sessions on Exchange Server, related technologies such as Outlook Mobile but also Teams and Groups, as well as some potentially interesting IT Pros sessions on Graph:

Session When Title Speakers
BRK2296 11/4/2019 2:15 PM Communication in Microsoft 365: Outlook and Teams integration opportunities Brandon Haist
THR2269 11/4/2019 3:00 PM Using Microsoft Teams: What’s new and how to get started Aya Tange, Jeremy Chapman
THR3039 11/4/2019 3:25 PM What’s new in the Office Customization Tool Chris Hopkins
BRK3095 11/4/2019 4:30 PM Understanding the importance of collaboration in modern work and the role O365 plays to unlock your team?s productivity Ronald Pessner, Patrick Gan, Dan Costenaro, Megan Dohnal
BRK2056 11/4/2019 4:30 PM Embrace Office 365 Groups: What’s new and what’s next Mike McLean, Venkat Ayyadevara
BRK2001 11/4/2019 4:30 PM What’s amazing and new in calendaring in Outlook Julia Foran
THR3084 11/4/2019 5:45 PM Microsoft 365 admin: Ask us anything Aaron Woo, Ben Appleby, Alice Appleton, Tim Heeney, Karissa Larson, Yeonsoo Kim
THR1131 11/4/2019 6:20 PM The solution to intranet adoption…Microsoft Teams Daniel Diefendorf
BRK3013 11/5/2019 9:00 AM Modern Exchange IT admin experiences Rahul Gupta, Eddie Savage
BRK1079 11/5/2019 10:15 AM Five hybrid cloud backup and disaster recovery mistakes to avoid Douglas Ko, Shawn Gifford, Carl Holzhauer, Julian Simpson
BRK3140 11/5/2019 10:15 AM Notes from the field: Successfully steering the government to Office 365 Michael Van Horenbeeck
BRK3012 11/5/2019 10:15 AM Exchange hybrid: Advanced scenarios, roadmap, and real-world stories! Andy Ryan, William Holmes
THR2016 11/5/2019 10:20 AM Outlook for Windows: What’s new and what’s next David Gorelik
THR3082 11/5/2019 10:55 AM Protect against phishing and other cyberthreats with Microsoft 365 Business David Bjurman-Birr
THR3083 11/5/2019 12:40 PM Office 365 Groups: Ask us anything Mike McLean, Venkat Ayyadevara, Kolvekar Loveleen Ramachandra, Nivedita Rajani, Salil Kakkar, Arunkumaran Varadharajan
THR2252 11/5/2019 1:50 PM How Microsoft manages its own employee Office 365 tenancy David Haam, David Johnson, Darren Moffatt
ADM50 11/5/2019 2:00 PM Managing across tenant boundaries in Office 365 Steve Silverberg, Robert Lowe
BRK2003 11/6/2019 9:00 AM Get ahead with Outlook mobile: Intelligent technology that helps you stay on top of your day Tali Roth, Michael Palermiti
MLS1035 11/6/2019 9:15 AM Microsoft Graph 101 for developers and IT professionals Yina Arenas, Jeremy Thake
THR3003 11/6/2019 10:55 AM New, fast, and reliable Exchange Online PowerShell cmdlets Tony Redmond
BRK3311 11/6/2019 11:30 AM Outlook mobile: The gold standard for secure communications in the enterprise Ross Smith, Lexi Torres
BRK2005 11/6/2019 12:45 PM Outlook for Mac – re-invented! Vivek Kumar, Alessio Roic
THR2270 11/6/2019 1:50 PM Microsoft Teams for IT admins: What’s new and what you need to know with Anne Michels Anne Michels, Jeremy Chapman
THR2007 11/7/2019 9:00 AM Stop organizing your own meetings ? Let Scheduler do it for you Warren Johnson
BRK3264 11/7/2019 10:15 AM Transform collaboration and fight shadow IT with Office 365 groups Arunkumaran Varadharajan, Sahil Arora
THR3033 11/7/2019 11:30 AM Reading SMTP headers like a boss Jeff Guillet
BRK2059 11/7/2019 11:30 AM Data residency with Office 365 datacenters Brian Day, Adriana Wood
THR2217 11/7/2019 12:05 PM Email is the easy part: Five pitfalls to avoid in tenant-to-tenant migrations Paul Robichaux
BRK3144 11/7/2019 1:00 PM The MVP guide to Office 365 security, Exchange Online edition Theresa Miller
BRK3142 11/7/2019 2:15 PM Things you never knew about Microsoft Teams that might be important some day Tony Redmond
BRK3312 11/7/2019 3:15 PM Office 365 email enhancements that makes your organization smart, safe, and secure Leena Sheth, Kevin Shaughnessy
BRK2104 11/7/2019 3:15 PM Your users are under attack! Strengthen your anti-phishing defense with these O365 ATP best practices Girish Chander
BRK2058 11/8/2019 9:00 AM Deploy Office 365 groups at scale to power Microsoft Teams, Outlook, Yammer, and SharePoint Salil Kakkar, Martina Grom
BRK2002 11/8/2019 9:00 AM There is a new Outlook on the web: See what’s new, fresh, and exciting David Meyers
BRK2090 11/8/2019 9:15 AM Will Microsoft Teams take over from email? Tony Redmond
BRK3248 11/8/2019 10:15 AM Securing Exchange Online from modern threats Brandon Koeller
BRK3257 11/8/2019 10:30 AM Leverage the cloud to strengthen your on-premises Active Directory security Charity Shelbourne, Mark Morowczynski
THR3034 11/8/2019 12:05 PM Twenty minutes to a secure environment Jeff Guillet

Note that the table above was constructed using the Get-EventSession script. I’ll be closely monitoring things this week to try to make sure it can retrieve Ignite contents as it gets published and cope with any changes in publishing as happened in recent years during the event.

Outlook Connection Status Details

Outlook 2016 New IconA little notice on a potential helpful feature which was introduced to Outlook at some point, but I wasn’t aware of before (or it’s just new). At least the option is available in Outlook v1905 build 11629.20008 C2R; it might also be available in standalone.

Many people are familiar with the Outlook Connection Status window, which you can summon by right-clicking the Outlook icon in the system tray while holding CTRL. This will show a dialog containing the connections Outlook is managing for every configured account, together with valuable information like endpoint, response times, etc.

image

One of the columns, Req/Fail, is showing the number of Requests and Failed requests. To check the headers of the last failing response for a particular connection, double-click the Req/Fail number. This will open up a popup window similar to this one:

image

Apart from essentials like the http result code, it will show which front-end and back-end servers processed the request. This might help to quickly determine if clients are connecting to unfavorable public endpoints, or when failed requests are coming from specific in case of Exchange on-premises. Of course, this information can also be retrieved using additional tools like Fiddler, but with this shortcut you don’t need to install additional software, as well as that you can ask end users to open up this window and send you the information.

Again, another little gem which might come in handy when troubleshooting.

Support Lifecycle changes for Office ProPlus & 2016 (a.o.)

Outlook 2013 IconIn a surprise – but welcomed – move, Microsoft announced yesterday that the office support lifecycle for Office 365 ProPlus on Windows 8.1 and Windows Server 2016 are extended to January 2023 (EOL of Windows 8.1) and October 2025 respectively. In addition, Office 2016 connectivity support for Office 365 services will be extended to October 2023 (was 2020).

Other announced changes in product support lifecycles were extending Windows 10 Enterprise & Education support from 18 to 30 months. Also, for Windows 7 Professional & Enterprise, paid security updates (Extended Security Updates) will be offered, and those Windows 7 ESU devices will be supported through January 2023 – parallel to Windows 8.1 – with Office 365 ProPlus.

The intention of these changes is to provide customers more flexibility in adopting modern desktops on the client end (i.e. Windows 10) and upgrade their Office suite, preferably to the susbscription-based ProPlus. The release cadence of the cloud has significant impact on organizations, which were told in February to keep in line with product releases as a lot of product support lifecycles were going to end in 2020.

Extending those dates not only gives them more flexibility to plan and upgrade, but also might prevent organizations to do only to the minimum, which is likely the reason many organizations are still on Windows 7 and why it took many organizations a long time to get rid of Windows XP.

 

Exchange 2016 & Office Online Server

pptxiconUpdate (May 9th): Office Online Server is now also available through MSDN here.

Update (May 4th): Office Online Server became available today. OOS is available on VLSC, language packs are on MSDN as well (perhaps a clue OOS will be available later on MSDN as well). Document modification option comes with additional licensing requirements, consult the release article for more information.

On April 26th, I gave a session on Exchange 2016 and Office Online Server – or OOS. Creating the session contents proved to hold some challenges. After agreeing on the session around the January timeframe, when OOS was still in Technical Preview, OOS got pulled a few weeks ago without notice. It was expected it would become Generally Available (GA) shortly after the release of SharePoint 2016, but that didn’t happen. To make matters more interesting, OOS was moved to Volume Licensing Service Center only, where its predecessor was freely available on the Microsoft download center. Currently, the status of OOS is that it is GA, and available on the VLSC site. The session and demo were based on the Technical Preview.

Back to the event, which was hosted by the always friendly and hospitable people from the Belgian E-Communications Community. At the office of Microsoft in Zaventem, Belgium, sessions were presented by 8 Microsoft MVP’s, Microsoft and sponsors, divided in 2 tracks: one Exchange-oriented track, and one track with Skype for Business related topics. Around a total of 60 people turned up in person for the event, and sessions were also  streamed live through Skype Meeting Broadcast. Excellent usage of available technology.

image
(picture by Michael van Horenbeeck)

After the opening keynote, Tony Redmond kicked off talking about Office 365 Groups, followed by fellow countryman Dave Stork talking about using Tools to deploy and manage Exchange. After the break, it was time for my session on Exchange 2016 and Office Online Server. Unfortunately, in the category 1st world problems, lack of an HDMI connector – required for presenting as well as streaming – on my laptop prevented me from doing the demo, and the remaining time was filled by a improvised Ask the Experts session on Exchange and Office 365, in which I was joined by the other Dutch MVP’s present. After that, Michael van Horenbeeck talked in his session about Advanced Identity & Authentication scenarios for Office 365. Jaap Wesselius closed the Exchange track with a session on the Do’s and Don’ts when using Exchange 2010 for Hybrid deployments.

The links above lead to the session recordings; a complete session overview including links to the recordings for the Skype for Business related sessions can be found here. My slidedeck – with caps of the demo – can be downloaded here. A page with links to all the slidedecks and recordings can be found here.

Knowledgebase RSS feeds

Update: Added Exchange 2016 and Skype for Business 2016 feed.

rss[1]Note: This is an update of an article from January, 2010.

Like most people I still use RSS feeds to keep track of news and updates from various sources. But did you know you can also keep track of Microsoft’s knowledgebase articles per product using RSS feeds? Great for keeping track of updates in RSS readers like Outlook or sites like Feedly, or creating triggers on sites like IFTTT (If-This-Then-That) to automatically send e-mail notifications.

Here are some RSS feeds on knowledgebase articles that might be of interest to you:

Exchange Server

Outlook

Office 365

Lync/Skype for Business

For a complete list of the knowledgebase articles RSS feeds check here.

iOS 9 Outlook App & Lync 2013 App Issues

iphone6After Apple released iOS 9 to the public yesterday. From an Exchange or Office 365 perspective, iOS 9 supports the enhanced calendar features of Office 365 and Exchange 2016 when that is released. Unfortunately, incidents have been reported with the Outlook app and the Lync 2013 App.

Regarding the Outlook App, iOS9 users might not be able to start the Outlook App or the Outlook app will just crash. The far from ideal workaround offered by the Outlook team, is to reinstall the Outlook app.

outlookappcrash

Of course, this also requires users to reconfigure accounts and Outlook App settings, so organizations can expect some calls to the service desk by users who upgraded. Organizations can report on the currently registered iOS8 devices that syned in the last 30 days, using:

Get-MobileDevice | Where-Object {$_.DeviceOS -like 'iOS 8*' -and $_.whenChanged -gt (Get-Date).AddDays(-30)} | Select UserDisplayName, FriendlyName, DeviceModel, DeviceOS, whenChanged

This will product a list of users, the name of their device, the device model and OS and when it last synced with Exchange. This information can be useful when you want to proactively approach users with iOS8 devices.

For Lync 2013 users, there are sign-in issues when they have configured different region and language settings on their iOS device. Those users will be presented the following:

Lync2013SignInIssue1

The issue has officially been confirmed through publication of KB3096704, which states:

“This problem is fixed in the Microsoft Skype for Business for iOS app that will replace Lync for iPhone and Lync for iPad when it’s released. No fix for this issue is scheduled for the current releases of Lync for iPhone and Lync for iPad”.

Since the Skype for Business app is not available yet, this is not good news. Mitigation is possible by matching the region with the language setting (or the other way around), after which you need to reinstall the Lync 2013 app from the store.

With all this in mind, should organizations wish to first test the new iOS against their Exchange environment for potential other issues, you can block iOS 9 from accessing your Exchange 2013 environment, or Office 365 tenant if you must, using the Access/Block/Quarantine feature. First you need to retrieve the reported DeviceOS string for iOS 9 for a device:

Get-MobileDevice | Where-Object {$_.DeviceOS -like “iOS 9*”} | Select DeviceModel, DeviceOSLanguage, DeviceOS

The reported DeviceOS strings then is used to create an ActiveSync device rule. For example, my iPhone 6 reports DeviceOS as “iOS 9.0 13A344”. To block these devices with iOS 9.0 and put them in quarantine, run the following:

New-ActiveSyncDeviceAccessRule -QueryString "iOS 9.0 13A344" -Characteristic DeviceOS -AccessLevel Quarantine

If you would like to know more about the Access/Block/Quarantine option, check out this article.

Outlook 2010 gets MAPI/http support

Office-2010-Outlook-Icon[1]Update: Hotfix KB2899591 pulled in Dec2014 due to possible issues, replaced in Jan2015 by KB878264.

A quick heads-up today as the recently released KB878264 hotfix adds MAPI/http support for Outlook 2010 clients. This will benefit organizations using Exchange 2013 SP1 or later considering switching from RPC/http to MAPI/http. The KB article includes details on additional fixes that are included in this hotfix as well.

You can request the hotfix for x86 and x64 versions of Outlook 2010 here.

Links to background information on MAPI/http, its impact on client performance, and impact on network traffic in an earlier blog post here.

Clearing AutoComplete and other Recipient Caches

Exchange 2010 Logo

Last version: 1.3, November 15th, 2019.

Anyone who has participated in migrations or transitions to Exchange has most likely encountered or has had to work around potential issues caused by the nickname cache. A “cache,” also known by its file extension, NK2 in older Outlook clients, is a convenience feature in Outlook and Outlook WebApp (OWA) which lets users pick recipients from a list of frequently-used recipients. This list is displayed when the end user types in the first few letters.

The potential issue revolves around end users using those lists to send messages, as the list contains cached recipient information. Because this information is static, it may become invalid at some point. Thus, when users pick recipients when sending messages, they may be sending messages to non-existent recipients or invalid e-mail addresses, which create issues like non-delivery of e-mail.

Read the full article over on ENow Solutions Engine blog.

Clean-AutoComplete

Using the script mentioned in the article, which can be used to clear cached recipient information, is straightforward. It requires Exchange 2010 or later and Exchange Web Services Managed API 1.2 (or later) which you can download here. Alternatively, you can copy the Microsoft.Exchange.WebServices.DLL with the script as it will also look for it in the current folder.

The script Clean-AutoComplete.ps1 has the following syntax:

Clear-AutoComplete.ps1 [-Mailbox] <String> [-Server <String>] [-Impersonation] [-Credentials <PSCredential>] [-Type <Array>] [-Pattern <String[]>]

Where:

  • Mailbox is the name or e-mail address of the mailbox.
  • Server is the name of the Client Access Server to access for Exchange Web Services. When omitted, the script will use AutoDiscover.
  • Switch Impersonation specifies if impersonation will be used for mailbox access, otherwise the current user context will be used.
  • Credentials specifies the user credentials to use.
  • Type specifies what cached recipient information to clear. Options are Outlook  (Outlook AutoComplete stream), OWA (OWA Autocomplete stream), SuggestedContacts, RecipientCache or All. Default is Outlook,OWA.
  • Pattern is the pattern of e-mail entries to remove from cache. Only works with OWA, SuggestedContacts and RecipientCache type clearances.

So for example, suppose you want to clear the Autocomplete stream used by Outlook on a mailbox, you can use:

Clear-AutoComplete.ps1 -Mailbox Olrik -Type Outlook -Verbose

ScreenCapTo remove the Autocomplete stream used by OWA on your Office 365 account, you can use:

Clear-AutoComplete.ps1 -Mailbox olrik@office365tenant.com –Credentials (Get-Credential) –Type OWA

Be advised that clearing the Outlook AutoComplete stream will only have effect for Outlook running in Online mode. Outlook caches this information as well in the OST file, leaving the options of running Outlook with the /CleanAutocompleteCache switch, or remove and let Outlook recreate the OST file. The temporary Stream_AutoComplete files*.dat files created under %USERPROFILE%\AppData\Local\Microsoft\Outlook\RoamCache are used by Outlook to speed things up.

Disabling Auto-Complete and Suggested Contacts
Alternatively, you can disable Auto-Complete, the equivalent of unchecking the Outlook option ‘Use Auto-Complete List to suggest names when typing in the To, Cc and Bcc line‘, by setting the following registry key:

Note: In the examples below, you need to modify the version number in the examples corresponding to the Outlook version you wish to apply these settings against. Use 16.0 as indicated for Outlook 2016, but change it to 15.0 for Outlook 2013, or 14.0 for Outlook 2010.

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences\
ShowAutoSug=0 (REG_DWORD)

To configure this setting using a Group Policy, use the following registry setting:

HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\Outlook\Preferences\ShowAutoSug=0 (REG_DWORD)

You can also disable Suggested Contacts folder, the equivalent of unchecking the Outlook option ‘Automatically create Outlook contacts for recipients that do not belong to an Outlook Address Book’, with the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Contact\CreateContactsForOneOffs= 0 (REG_DWORD)

The related Group Policy setting is:

HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\Outlook\Contact\CreateContactsForOneOffs= 0 (REG_DWORD)

Feedback
Feedback is welcomed through the comments. If you got scripting suggestions or questions, do not hesitate using the contact form.

Download
You can download the script from my Technet Gallery here.

Revision History
See Technet Gallery page.

Outlook versions supporting Personal Archives and Retention Policies

Outlook 2013 IconIn an earlier article here, I mentioned which Outlook 2010 versions were eligible for Personal Archives.

Now, with the release of Office 2013, and Outlook 2013 in particular, it’s good to get an update on the Outlook versions and their support of Personal Archives and Retention Policies in Exchange Server 2010 or Exchange Server 2013.

The following Outlook versions support Personal Archives and Retention Policies:

Retail Licenses Volume Licenses
  • Outlook 2013 stand-alone
  • Outlook 2010 stand-alone
  • Outlook 2007 stand-alone
  • Outlook 2007 included with Microsoft Office Ultimate 2007
  • Outlook 2013 stand-alone
  • Outlook 2013 included with Microsoft Office Professional Plus 2013
  • Outlook 2010 stand-alone
  • Outlook 2010 included with Microsoft Office Professional Plus 2010
  • Outlook 2007 stand-alone
  • Outlook 2007 included with Microsoft Office Professional Plus 2007
  • Outlook 2007 included with Microsoft Office Enterprise 2007

Few notes:

  • As mentioned here, Outlook 2007 doesn’t support adjusting retention policies;
  • Personal Archives and Retention Policies require an Microsoft Exchange Server Enterprise Client Access License.

The case of the not updating Outlook for Mac 2011

exchange2007logo2[1]I had contact with a Twitter user on an issue with Outlook for Mac 2011 talking against Exchange Server 2007 on Small Business Server 2008.

When configuring a new account, Outlook for Mac reported “Account cannot be added.  Note that Outlook 2011 requires Exchange Server 2007 SP1 Update Rollup 4 or later.”

image

However, that couldn’t be right because that user claimed to be running a higher version of Exchange 2007. After manually entering the server name, a connection could be established and an initial download of folders and contents took place. However, items weren’t updated and contacts and calendar remained empty.

After trying and checking some things, I asked to turn on Outlook for Mac’s logging hoping to find something in the Exchange Web Services log (Outlook for Mac 2011 is EWS based). You can enable logging by checking Window > Error Log > Errors > Settings > Turn on logging for troubleshooting. After a while I was sent the log file Microsoft Outlook_Troubleshooting_0.log which contained the following excerpt:

2013-01-24 08:55:34.392,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Response data received on thread=0x7d27bdb4, XML data=
<?xml version=""1.0"" encoding=""utf-8""?><soap:Envelope xmlns:soap=""http://schemas.xmlsoap.org/soap/envelope/"" xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema""><soap:Header><t:ServerVersionInfo MajorVersion=""8"" MinorVersion=""3"" MajorBuildNumber=""297"" MinorBuildNumber=""0"" Version=""Exchange2007_SP1"" xmlns:t=""http://schemas.microsoft.com/exchange/services/2006/types"" /></soap:Header>

First, Exchange reports version 8.3.297.0 which corresponds with Exchange 2007 SP3 RU9 (EWS can report slightly different version than actual version), so something else was wrong while that’s well above Exchange 2007 SP1 RU4.

2013-01-24 08:55:39.355,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Sending request on connection=0x7dc89be8, URL=/EWS/Exchange.asmx, SoapAction=""http://schemas.microsoft.com/exchange/services/2006/messages/SyncFolderItems"""
2013-01-24 08:55:39.358,0xFFFFFFFF,Outlook Exchange Web Services,Info,EWS: Received response on connection=0x7d31dae8; status=500
..
2013-01-24 08:55:49.861,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Sending request on connection=0x7d71a648, URL=/EWS/Exchange.asmx, SoapAction=""http://schemas.microsoft.com/exchange/services/2006/messages/GetItem"""	
2013-01-24 08:55:49.863,0xFFFFFFFF,Outlook Exchange Web Services,Info,EWS: Received response on connection=0x7dc26638; status=500
..
2013-01-24 08:55:39.359,0xFFFFFFFF,Outlook Exchange Web Services,Info,"EWS: Sending request on connection=0x7d31dae8, URL=/EWS/Exchange.asmx, SoapAction=""http://schemas.microsoft.com/exchange/services/2006/messages/GetItem"""	
2013-01-24 08:55:39.477,0xFFFFFFFF,Outlook Exchange Web Services,Info,EWS: Received response on connection=0x7d7005c8; status=200

I then noticed various EWS requests returned http status code 200 (means OK) but also 500’s, which correspond to “Internal Server Error”. It happened after various requests (e.g. SyncFolderItems, GetFolder, GetItem) but not for all requests.

Now, code 500 isn’t very helpful (general terminal failure) and a quick restart of IIS with iisreset /restart /noforce didn’t solve things.

After some digging it turned out the seemingly unrelated KB2264110 pointed in the right direction. I say unrelated, because it’s on messages not being updated on Blackberry Internet Service (BIS) after installing Exchange Server 2007 SP2. Turned out the performance counters on the Exchange 2007 server were corrupt and rebuilding them solved the issue.

To rebuild the performance libraries, perform the following steps from an elevated command prompt:

  1. CD %SystemRoot%\System32
  2. Run lodctr /R (/R is case-sensitive) which will rebuild all known counters
  3. Run wmiadap /f which will update the WMI performance classes
  4. Restart the Exchange 2007 server

After these steps, Outlook for Mac 2011 could sync again with Exchange Server 2007 SP3.