Tag: Exchange 2010

Exchange 2013 CU1 delayed, Planned for April the 2nd

The last piece required to support coexistence and start migrating from Exchange 2010 to Exchange 2013, just got delayed some days…

“We found an issue with Exchange 2010 coexistence. The issue actually had an easy workaround, but we made a decision; instead of burdening you with a configuration change on all of your Exchange 2010 Client Access servers, we decided to take a code change in Exchange 2013 and solve the problem so that you will not have to make any additional configuration changes. Given that the goal of CU1 is to enable coexistence with legacy versions of Exchange, we felt this was the right decision; after all, we want to ensure that your upgrade to Exchange 2013 and your coexistence period goes as smooth as possible.”

“The release date for Exchange 2013 RTM CU1 is currently planned for April 2nd”

Exchange 2013 ECP Redirects to old Exchange 2010 OWA

I recently setup an Exchange 2013 Server in an Exchange 2010 Environment.

All worked fine, but logging in to https://ex2013.wardvissers.nl/ecp redirected me to the old Exchange 2010 Interface.

image

image

 

Solution 1:

If you have this problem, you can add the Exchange Version to the URL using “?ExchClientVer=15″.

So https://ex2013.wardvissers.nl/ecp?ExchClientVer=15 will redirect you to the correct Management Interface.

image

Note: If the Mailbox of the Administrator account resides on the new Exchange 2013 Server this will be obsolete.

Solution 2:

Or you add an extra / add the end https://ex2013.wardvissers.nl/ecp/

Apple released iOS 6.1.2 Software Update Fixes an Exchange calendar bug that could result in increased activity on Exchange 2010 Server.

Apple released iOS 6.1.2 Software Update which Fixes an Exchange calendar bug that could result in increased network activity on Exchange Server.

The Bug descripted by Microsoft:
Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device

Temp Solution:
http://exchangeserverpro.com/block-ios-61-exchange-2010?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+ExchangeServerPro+%28Exchange+Server+Pro%29

Final Solution:

Upgrade to IOS 6.1.2

2012 Blogging

This blog was viewed about 110,000 times in 2012. If it were a concert at the Barclays Center, it would take about 6 sold-out performances for that many people to see it.
In 2012, there were 88 new posts, growing the total archive of this blog to 485 posts.
The busiest day of the year was March 13th with 616 views. The most popular post that day was Exchange 2010 Opening multiple shared calendars & additional mailboxes.

These are the posts that got the most views in 2012. You can see all of the year’s most-viewed posts in your Site Stats.

image

Issue with Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

Recently, Windows Update began offering the Windows Management Framework 3.0 as an Optional update. This includes all forms of update distribution, such as Microsoft Update, WSUS, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0.

Windows Management Framework 3.0 is being distributed as KB2506146 and KB2506143 (which one is offered depends on which server version you are running – 2008 Sp2 or 2008 R2 Sp1).

What does that mean to you?

Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013 (which requires it). If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Rollups that will not install, or the Exchange Management Shell may not run properly.

We have seen rollups not installing with the following symptoms:

  • If rollup is installed through Microsoft Update, the installation might error with error code of 80070643
  • If rollup is installed from a download, the error displayed is “Setup ended prematurely because of an error.”
  • In both cases, event log might show the error with an error code of “1603”

Exchange Team adviced that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once the update is removed, functionality should be restored.

Exchange 2010 SP1 RU8 and Exchange 2007 SP3 RU9

Today the Exchange CXP team released the following update rollups to the Download Center. All three releases cover Security Bulletin MS12-080. Because this is a security release, the updates will also be available on Microsoft Update.

Update Rollup 8 for Exchange Server 2010 Service Pack 1

Update Rollup 9 for Exchange Server 2007 Service Pack 3

Download: Update Rollup 8 for Exchange Server 2010 Service Pack 1

Download: Update Rollup 9 for Exchange Server 2007 Service Pack 3

Exchange 2010 SP2 Management Tools on Windows 8 RTM

Some day’s ago I installed Windows 8 Enterprise x64 RTM on my Work pc.
So I wanted Exchange 2010 Management Tools on my PC.

I found the following topic: Exchange 2010 Management tools

This worked for me Smile

  1. Install the .NET Framework 3.5 Windows Feature
  2. Install the IIS 6 Management Console Feature
  3. Install the IIS Metabase and IIS 6 Configuration Compatibility Feature
  4. Modify the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion registry key from “6.2” to “6.1” as stated above
  5. DO NOT Close REGEDIT
  6. Create a MMC with the Exchange Tools on it and I saved it under c:\Windows 8 RTM Exchange 2010 SP2\ExchangeAdmin.msc 
  7. Create a Bat File

    8. set __COMPAT_LAYER=RUNASINVOKER
    set COMPLUS_Version=v2.0.50727
    c:\Windows 8 RTM Exchange 2010 SP2\ExchangeAdmin.msc

    Now you can Manage Exchange 2010 from a Windows 8 pc. I found no issues till now. Beware this is not supported by Microsoft!!!!!

     

Re-released Exchange 2010 and Exchange 2007 update rollups

The Exchange Team re-released the following Rollup Updates. These updates address an issue in which digital signatures on files produced and signed by Microsoft will expire prematurely, as described in Microsoft Security Advisory 2749655.

The re-released Exchange 2010 SP2 RU4 includes the following additional fix:

2756987 Only one result is returned after you click “view all results” in Outlook 2010 or in Outlook 2013 in an Exchange Server 2010 environment

Announcing Exchange 2010 Service Pack 3

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

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

Need To Now Before You Deploy Exchange 2010 SP2 RU4

Calendar and Tasks Retention Tag Support in Exchange 2010 SP2 RU4 means you’ll need to treat this update rollup differently. If you don’t use Retention Policies or if you don’t mind Calendar and Tasks items being moved to archive or deleted automatically based on the DPT settings, you can skip the rest of this post. Else reed this Blog Post: Calendar and Tasks Retention Tag Support in Exchange 2010 SP2 RU4

However, if you are concerned about the effects of this new functionality will have on your calendar and task items, you can implement the following temporary workarounds:

If you don’t want Calendar and Tasks items to ever expire, you can disable the functionality that is included in Exchange 2010 SP2 RU4. Add the following registry key to your Mailbox servers:

  • Path: HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants\Parameters
  • Name: ELCAssistantCalendarTaskRetentionEnabled
  • Type: DWORD
  • Value: 0 = Do not process Calendar and Task folders
  • Value: 1 = Process (default with RU4)

If you want Calendar and Tasks folders to expire at a different interval than DPTs, you can follow the following steps:

  1. Place all mailboxes on Retention Hold
  2. Apply Exchange 2010 SP2 RU4 to your Mailbox servers.
  3. Create RPTs for Calendar and Tasks folders with the desired retention settings.
  4. Inform users about the change.
  5. When ready, remove the retention hold from mailboxes.
Translate »