Tag: Exchange

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/

Exchange Server 2013 Deployment Assistant

ExchangeTeam the announce the availability of the Exchange Server 2013 Deployment Assistant at http://technet.microsoft.com/exdeploy2013. The Exchange Deployment Assistant is a web-based tool that helps you deploy Exchange 2013 in your on-premises organization, configure a hybrid deployment between your on-premises organization and Office 365, or migrate to Office 365. It asks you a small set of simple questions and then, based on your answers, creates a customized checklist with instructions to deploy or configure Exchange 2013. Instead of trying to find what you need in the Exchange library, the Deployment Assistant gives you exactly the right information you need to complete your task.

The first scenarios available show you how to deploy Exchange 2013 in an organization with no previous installations of Exchange and show you how to configure a hybrid deployment between your on-premises Exchange 2013 organization and Office 365. We’re working hard on additional scenarios, such as upgrading from Exchange Server 2007 and Exchange Server 2010. These additional scenarios will be added in the coming months.

The Deployment Assistant for Exchange 2013 is supported on most major browsers and has a completely redesigned interface that’s no longer dependent on Silverlight technology. Here’s a screenshot from the Deployment Assistant after the initial set of questions were answered and the customized checklist was generated.

image

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

Setting Up Windows 8 Mail for Exchange or Office 365

Before beginning these steps, ensure that:

You have setup a Microsoft account in Windows 8.

You have your Active Directory (AD) username and password. Your username is usually the first part of your UCSD email address (before the @ symbol). If you forgot your password, you can reset it.

You have an Exchange account in the UCSD Campus Exchange Organization.

Click the Mail tile in the Start screen to open the Mail program

Press Windows key + I on the keyboard to open Mail settings

Select Accounts

win8mailsettings
win8mailaddaccount1

image

Enter your e-mail address in the Email address field

Enter your AD passsword in the Password field

Select Show more details

image
Enter <yourservername> in the Server address field

Enter <yourdomain> in the Domain field

Enter your AD username in the Username field

Click Connect to add the account

Forefront TMG 2010 SP2 Rollup 3

Microsoft released Rollup 3 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

For Exchange, this Rollup fixes unexpected authentication prompts when using OWA published using Forefront Threat Management Gateway (TMG) 2010 in conjunction with RSA authentication and Forms-based Authentication (2783345)

 

2700248 A server that is running Forefront Threat Management Gateway 2010 may stop accepting all new connections and may become unresponsive

2761736 All servers in a load-balanced web farm may become unavailable in Forefront Threat Management Gateway 2010

2761895 The Firewall service (WSPSRV.EXE) may crash when the firewall policy rules are reevaluated in Forefront Threat Management Gateway 2010

2780562 PPTP connections through Forefront Threat Management Gateway (TMG) 2010 may be unsuccessful when internal clients try to access a VPN server on the external network

2780594 A non-web-proxy client in a Forefront Threat Management Gateway (TMG) 2010 environment cannot open certain load-balanced websites when TMG HTTPS inspection is enabled

2783332 You cannot log on when FQDN is used and Authentication delegation is set to “Kerberos constrained delegation” in a Forefront Threat Management Gateway 2010 environment

2783339 A closed connection to a domain controller is never reestablished when Authentication delegation is set to “Kerberos constrained delegation” in a Forefront Threat Management Gateway 2010 environment

2783345 Unexpected authentication prompts while you use an OWA website that is published by using Forefront Threat Management Gateway (TMG) 2010 when RSA authentication and FBA are used

2785800 A “DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)” Stop Error may occur on a server that is running Forefront Threat Management Gateway (TMG) 2010

2790765 A “Host Not Found (11001)” error message occurs when an SSL site is accessed by using a downstream Forefront Threat Management Gateway 2010 server that has HTTPS Inspection enabled

 

For TMG, support will end on April 14th, 2015 and extended support will end on April 14th, 2020. You have some time to look into alternatives.

You can request Forefront TMG SP2 RU3 directly from support here.

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.

Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2

Update Rollup 5 version 2 for Exchange Server 2010 SP2 addresses the vulnerabilities that are described in Microsoft Security Bulletin MS12-080

http://technet.microsoft.com/en-us/security/Bulletin/MS12-080

. This update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment’

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment.

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment

Assume that you apply the Update Rollup 4 version 2 for Exchange Server 2010 SP2 (KB2756485), and then you apply the Update Rollup 5 version 1 (KB2719800). In this situation, when you try to run the Get-DatabaseAvailabilityGroup cmdlet, you receive the following error message:

WARNING: An unexpected error has occurred and a Watson dump is being generated: Could not load type ‘Microsoft.Exchange.Rpc.ActiveManager.AmDeferredRecoveryEntry’ from assembly ‘Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.

Download Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908)

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

Rollup 5 for Exchange Server 2010 Service Pack 2

Exchange Team released Rollup 5 for Exchange Server 2010 Service Pack 2.

List with fixes:
2707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment

2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet

2712001 ;ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment

2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment

2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used

2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list

2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment

2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server

2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment

2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment

2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment

2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment

2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment

2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment

2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment

2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging

2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment

2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network

2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment.

Download

Translate »