Exchange PST Capture Tool released

Today the Exchange Team released the Microsoft Exchange PST Capture Tool (initial version 14.3.16.4). The tool can be used to discover and inject PST files in an Exchange 2010 Exchange Online mailbox or archive.

The tool was originally from Red Gate and known as PST Importer. It’s architecture consists of three components: the central service, agents for PST discovery, registration and collecting PST files and an administrative console

Courtesy: Red-gate

The online documentation can be found here.

Note that although it’s only supported for Exchange 2010 and Exchange Online, you can use it with Exchange 2007; it’s only untested (and probably unsupported) with that product.

You can read the official announcement here; you can download the tool and the agents here.

OCS R2 January 2012 Updates Released

Microsoft has released a few updates for OCS 2007 R2.

Here are the components:

Server Updates (6907.244) – KB 968802

· UCMA 2.0 Core Redist – KB 2647091

Note: As always, the easiest way to make sure your server is up to date across all components is to use the Cumulative Server Update Installer (ServerUpdateInstaller.exe package)

Client Updates

· Communicator Client (6907.244) – KB 2647093

Group Chat(6907.244)

· Server – KB 2647090

Lync January 2012 Client Updates Released

Just released, a minor update to the Lync client

Clients (7577.4061)

· Lync 2010 (32-bit) – DownloadKB 2670498

· Lync 2010 (64-bit) – DownloadKB 2670498

From the KB, looks like it only addresses one issue:

2670467 Large increases in load on the OrgID service because of recurring authentication requests from Lync 2010

Exchange 2007 SP3 Update Rollup 6

Today the Exchange Team released Rollup 6 for Exchange Server 2007 Service Pack 3 (KB2608656). This update raises Exchange 2007 version number to 8.3.245.2.

Here’s the list of changes included in this rollup:

· 2289607 The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment

· 2498852 “0×80041606″ error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment

· 2499841 An arrow icon does not appear after you change the email message subject by using OWA in an Exchange Server 2007 SP3 environment

· 2523695 A “System.ArgumentOutOfRangeException” exception occurs when you click the “Scheduling Assistant” tab in Exchange Server 2007 OWA

· 2545080 Users in a source forest cannot view the free/busy information of mailboxes in a target forest when the cross-forest Availability service is configured between two Exchange Server 2007 forests

· 2571391 Applications or services that depend on the Remote Registry service may stop working in an Exchange Server 2007 environment

· 2572010 The Microsoft Exchange Information Store service may crash after you run the Test-ExchangeSearch cmdlet in an Exchange Server 2007 environment

· 2575360 A new feature is available to automatically stop the Microsoft Exchange Information Store service when a time-out is detected in an Exchange Server 2007 SP3 environment

· 2591655 A journaling report remains in the submission queue when an email message is delivered successfully in an Exchange Server 2007 environment

· 2598980 The PidLidClipEnd property of a recurring meeting request has an incorrect value in an Exchange Server 2007 environment

· 2616427 An Outlook Anywhere client loses connection when a GC server restarts in an Exchange Server 2007 environment

· 2617784 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment

· 2626217 Certain changes to address lists may not be updated in an Exchange Server 2007 environment

· 2629790 The Exchange IMAP4 service may stop responding on an Exchange Server 2007 Client Access server when users access mailboxes that are hosted on Exchange Server 2003 servers

· 2633801 The SCOM 2007 SP1 server cannot alert certain issues in an Exchange Server 2007 organization

· 914533 The Microsoft Exchange Information Store service may stop responding on an Exchange Server 2007 server

· 976977 The scroll bar does not work in OWA when there are more than 22 all-day event calendar items in an Exchange Server 2007 user’s calendar

· 2641312 The update tracking information option does not work in an Exchange Server 2007 environment

· 2653334 The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment

· 2656040 An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes

· 2658613 The “PidLidClipEnd” property of a no ending recurring meeting request is set to an incorrect value in an Exchange Server 2007 environment

Quick Note:

When running Forefront Protection for Exchange, make sure you disable Forefront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable Forefront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SP). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup.

You can download Exchange 2007 SP3 Rollup 6 here.

ForeFront TMG SP2 Rollup 1

A short blog on the ForeFront team releasing Rollup 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2.

This Rollup fixes a “Bad Request” issue when accessing OWA through Forefront TMG. For a full list of changes, consult knowledgebase article kb2649961.

Note that along the lines of products like Exchange, cumulative updates for ForeFront TMG are now also called Rollup instead of Software Update or Update.

You can request ForeFront TMG SP2 RU1 directly from support here.

By msexchangeanywhere Posted in TMG Tagged

How did this blog perform in the year of 2011

The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.

Here’s an excerpt:

A San Francisco cable car holds 60 people. This blog was viewed about 2,000 times in 2011. If it were a cable car, it would take about 33 trips to carry that many people.

Click here to see the complete report.

Why Microsoft push notification messages are not delivered to Lync Mobile Clients.

Taken from Microsoft KB2664650

Microsoft push notification messages are not delivered to Lync mobile IOS and WP7 clients, when URL filtering is configured on Lync 2010 Edge Servers or office communication 2007 R2 Access Edge Server, apparently this is caused by:

Taken from Microsoft KB2664650

The Lync Server 2010 Mobility service sends SIP messages that contain active hyperlinks in their Message-Body header that define the XML namespace information for the push notification to the Lync Server Push Notification service.

Lync Server 2010 Front End Pool

Using the URL Filter page in the IM and Presence group in Lync Server Control Panel to enable the Hyperlink prefix option Send warning message, will precede the active hyperlink with a user defined warning message in the SIP packet that contains the push notification message. The Lync Server Push Notification service will reject the modified push notification information and send an error response back to the Lync Server 2010 Mobility service.

Office Communications Server 2007 R2 Access Edge server

Using the URL Filter tab of the Office Communications Server 2007 R2 Intelligent IM Filter dialog to:

o Allow instant messages that contain hyperlinks, but convert the hyperlinks to plain text

o Allow instant messages that contain hyperlinks. Enter a warning that you want to insert at the beginning of each containing hyperlinks

Will precede the active hyperlink with a user defined warning message and convert the active hyperlink to text by preceding it with an underscore or precede the active hyperlink with a user defined warning message in the SIP packet that contains the push notification message. The Lync Server Push Notification service will reject the modified push notification information and send an error response back to the Lync Server 2010 Mobility service.

for more information about the workaround and how to fix this issue please click here

How to Enable Push Notifications for Lync Mobile – (iPhone & Windows Phone 7)

Push notifications, in the form of badges, icons, or alerts, can be sent to a mobile device even when the mobile application is inactive. Push notifications notify a user of events such as a new or missed IM invitation, missed calls, and voice mail. The Microsoft Lync Server 2010 Mobility Service sends the notifications to the cloud-based Microsoft Lync Server 2010 Push Notification Service, which then sends the notifications to the Apple Push Notification Service (APNS) or the Microsoft Push Notification Service (MPNS).

Push Notification requires a Lync or OCS EDGE Server and Federation with Lync Online because Push Notification works via Lync Online Federation.

1. First step is to create new hosting provider federation with Lync Online.

New-CsHostingProvider –Identity “LyncOnline” –Enabled $True –ProxyFqdn “sipfed.online.lync.com” –VerificationLevel UseSourceVerification

2. Add push.lync.com to the allowed domains list

New-CsAllowedDomain –Identity “push.lync.com”

3. Enable Push Notifications (iPhone & WP7)

Set-CsPushNotificationConfiguration –EnableApplePushNotificationService $True –EnableMicrosoftPushNotificationService $True

4. Enable Federation if you haven’t already done that in your environment

Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True

5. Test Lync Online Federation

Test-CsFederatedPartner –TargetFqdn internaledge.contoso.com –Domain push.lync.com –ProxyFqdn sipfed.online.lync.com

6. Test Push Notifications

Test-CsMcxPushNotification –AccessEdgeFqdn internaledge.contoso.com

How to Publish Reverse Proxy URLs for Lync Mobility Discover Service with TMG

Create a new rule for the Lync auto discover service. The full functionality uses just the regular External Webservices URLs.

For more info on the previous steps go to this article:
https://msexchangeanywhere.wordpress.com/2012/01/13/how-to-install-lync-2010-mobility-installation-overview/

Create a new Web Publishing Rule

This is obviously an allow rule

Depending how you load balance or whether you have standard/enterprise edition this might be different on your end.
ISA/TMG supports cookie based load balancing (requirement for external web services URLs) if required in your deployment

You have to select SSL to the server/loadbalancer

Enter the name of the webservices loadbalancer or pool

You have to select to forward the original host header

The public name is lyncdiscover.<domain.com>

Select the correct listener (preferably both port 80 & 443)

Select authentication settings

Remove All Authenticated Users and replace this with All Users (No Authentication)

Finish

Now you have to change the following tab on the rule

You have to include both HTTP and HTTPS and forward to the correct ports

HTTP => 8080

HTTPS => 4443

Change the authentication option for HTTP on the Listener.
(you might need a new listener for security reasons so that the listener never sends authentication)

Publish your rules