Exchange Admin Center redirects to OWA

When installing Exchange 2013 in an environment with Exchange 2010, there is no link or application for Exchange Admin Center. Open a browser and type https://<Servername>/ecp/?ExchClientVer=15, this will give you direct access to the Exchange 2013 server, not on the Exchange 2010 server where the mailbox may reside.

Exchange Admin Center redirects to OWA

When installing Exchange 2013 in an environment with Exchange 2010, there is no link or application for Exchange Admin Center. Open a browser and type https://<Servername>/ecp/?ExchClientVer=15, this will give you direct access to the Exchange 2013 server, not on the Exchange 2010 server where the mailbox may reside.

How to set up a forwarder – Microsoft Online Services

1. Download MOS Migration tool from below url :
Microsoft Online Services Migration Tools (32 bit)
http://www.microsoft.com/downloads/en/details.aspx?familyid=9ed5f4c1-7f0b-4506-a214-32093af6147a&displaylang=en

Microsoft Online Services Migration Tools (64 bit)
http://www.microsoft.com/downloads/en/details.aspx?familyid=5547634c-5e49-4dbd-b6b0-457b38a75f33&displaylang=en

2. Log in to Administration Center for domain in BPOS-S and create a contact for the email address to whom you want to forward emails.

3. Launch the ‘Migration Command Shell’ from your programs folder.

4. Use the below cmdlet to set external forwarding.

Set-MSOnlineAlternateRecipient -Identity <email address of your hosted account> -AlternateRecipient <email address to forward to> -DeliverToBoth $true

Example: Set-MSOnlineAlternateRecipient -Identity name@kazmarek.com -AlternateRecipient name@gmail.com -DeliverToBoth $true

*Note: The ‘$true’ on the end means it will leave a copy and forward. Change to ‘$false’ and it will only forward and not fill up mailbox.

*Note: If you want to remove a forwarder:

Clear-MSOnlineAlternateRecipient -Identity <email of hosted account>

Example: Clear-MSOnlineAlternateRecipient -Identity name@kazmarek.com

Redirecting OWA URL’s in Exchange 2010

Great blog post on redirecting OWA URL’s for Exchange 2010 on WS08 R2, tested and it works.

http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/

Renew SSL self-signed certificate in SBS 2008

With Small Business Server 2008, you have the option to use a third party SSL certificate or the default self-signed SSL certificate. By default the self-signed certificate is valid for two years, but how to you renew it without interrupting OWA, Outlook, and Exchange? When the certificate is expired, Outlook 2007/2010 will give you an error message when opening, that the certificate is not valid. Here are the steps to fix it.

1. Goto the Windows SBS Console, click on Network Tab, then Connectivity Tab
2. Click on the certificate icon, then click the “view certificate properties” in the right pane. In the General tab of the new window, it will show the dates that the self-signed certificate is valid for.
3. In the “Connectivity Tasks” area, click “setup your Internet address”, go through the wizard to renew your self-signed SSL certificate.
4. When you now check the certififcate properties, you will see that it is now valid for another two more years.

BPOS – Exchange Hosted important Shell Commands

To add mailbox permissions to other users in Microsoft Exchange Hosted Services (BPOS).

Add-MSOnlineMailPermission -Identity user@example.com -TrustedUser admin@example.com –GrantFullAccess True –GrantSendAs True

http://technet.microsoft.com/en-us/library/ee662271.aspx

Get Mailbox size settings from Microsoft Exchange Hosted Services

Get-XsHostedExchangeMailbox -SourceServer red001.mail.microsoftonline.com -SourceIdentity user@domain.com -SourceAdminCredential $cred -SourceDetail Full

http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=85 [Read more…]

Installing Thawte’s new 2048 bit certificates

Thawte now is conforming to the new 2048 bit standard for their SSL certificates, which will require you to install two intermediate certificates on your server before they work and is validated. Below are the links to the articles and intermediate certificates. Download both certificates and import them into the “Intermediate Certificate Authority” in the Certificates MMC.

Thawte Intermediate and Cross Root CAs – link

Primary and Secondary Intermediate CAs – link

Comparison of Exchange ActiveSync clients (mobile devices)

Great table on the features of ActiveSync and what each client (device) can do, – Wikipedia

Windows server backup fails consistency check of the Exchange database

Trying to backup Exchange 2010 and purge transaction logs using the built-in Windows Server Backup app (Windows 2008).

– Backup completes but with warnings and log files won’t purge

-Found that the backup will run successful only if database files and the transaction log files on the same volume

Moved the transaction logs files via the EMC to the save volume as the databases and got past the consistency check failure issue, and got a good backup w/flushed logs.

Outlook 2003 (connected to Exchange 2010) gives unknown error when deleting some messages

When users delete items from folders, outlook doesn’t seem to refresh the item list.  If you try and delete the item again, outlook throws an “unknown error” message.  If you delete an item and then navigate away from a folder or even use the navigation pane to display the same folder, the item list will refresh and remove the deleted message.

The issue is “The basic issue is that Outlook 2003 support UDP and polling notifications. Exchange 2007 supports UDP, polling and Async notifications. Exchange 2010 only supports polling and Async notifications. This means when Outlook 2003 move from Exchange 2007 to Exchange 2010, Outlook clients will fall back to polling which by default only gets notifications every 30secs-1min. This means any change won’t show up immediately.

UDP notification support was removed from Exchange 2010. As a result, Outlook 2003 can only use polling notifications in online mode, which are still supported by RPC Client Access. This will result in a slight delay in updates to item status (30 seconds on average up to a 1 minute delay) when changes are made to items in a mailbox accessed by Outlook 2003.”

The fix:

Method 1: Install Update Rollup 1 for Exchange Server 2010

Important This method contains steps that tell you how to modify the registry. However, serious problems may occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For more protection, back up the registry before you modify it so that you can restore the registry if a problem occurs. For more information about how to back up and then restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

You can download Update Rollup 1 for Exchange Server 2010 from the following article in the Microsoft Knowledge Base:

976573 Description of Update Rollup 1 for Exchange Server 2010

After you install the update, you must add the following registry data to the server by using the Client Access role.

  1. Start Registry Editor.  
  2. Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeRPCParametersSystem Create the ParametersSystem

    Note

    registry subkey if it does not exist.

  3. Add the following registry data to the server:Value type: REG_DWORD
    Value name: Maximum Polling Frequency
    Value data: any integer between 5000 and 120000 (decimal value)

  4. Exit Registry Editor.

Notes

  • The registry change is dynamically detected. Therefore, the new settings will be applied to any new connections that clients make after the change is made. If you want to make sure that the new settings are applied to all clients, you should recycle the Microsoft Exchange RPC Client Access service because connections from clients can remain alive for a long time.
  • Outlook 2003 does not poll the Exchange Server 2010 server in intervals that are less than 10 seconds. Therefore, any value less than 10000 will generally have the same effect.
  • This change does not reinstate UDP communication between Exchange Server 2010 and Outlook 2003. This change only enables polling to occur more frequently between Exchange Server 2010 and Outlook 2003.

Microsoft KB – link