Apple IOS 6.1.2 Resolved issues with Exchange – part 2

Products compatible with this software update:

  • iPhone 3GS or later
  • iPod touch (4th generation or later)
  • iPad 2 or later
  • iPhone 5
  • Fixes an Exchange calendar issue that could result in increased network activity and reduced battery life

For more information regarding iOS 6 and the applicable updates, please refer to the following articles:

iOS 6.1.2 Software Update

http://support.apple.com/kb/DL1639

iOS 6.1: Excess Exchange activity after accepting an exception to recurring calendar event

http://support.apple.com/kb/TS4532

About the version history of iOS 6

http://support.apple.com/kb/HT5496

iPhone: Which iOS 6 Features are Available for me

http://www.apple.com/ios/feature-availability/

iOS: How to update your iPhone, iPad, or iPod touch

http://support.apple.com/kb/HT4623

Advertisements

Update: Exchange Server TechNet Library URLs

Exchange Team Blog has announced that there is an updated Exchange server Technet Library URlLs.

Many of you have seen our previous blog post announcing the Exchange documentation URL changes, and have provided us with your feedback on the matter. Starting off, we want to thank you for all of it; we learned quite a bit from it, and we think it’s fantastic that we have such passionate and vocal community.

First, a little bit of history. How did we get here?

As an enterprise product with a long lifecycle, product documentation for multiple Exchange versions is published on TechNet. If you look at Exchange documentation library, you will find content for Exchange Server 2013, Exchange Server 2010, Exchange Server 2007 and Exchange Server 2003.

As part of our content publishing process, we have historically used version-less URLs (URLs with no version info) that point to the most recent version of a topic. This has been our practice for both our IT Pro and Developer documentation for multiple releases of Exchange. Interestingly, we didn’t get any negative feedback, or really any feedback at all the previous time we made this switch, when we moved from Exchange 2007 to Exchange 2010.

One could speculate as to why the previous switch wasn’t painful, but this one was, but the main point is — this last switch was.

Where do we go from here?

Taking all of the feedback we received into consideration, and based upon upcoming documentation publishing milestones, we have decided on the following course of action to prevent this sort of pain from happening with future product releases (the changes are not live yet, but will be starting tomorrow):

– Bad news first: we will not be switching the documentation URLs back to where they were pre-November 2012. While this was a painful decision, we do not want to increase the pain more by doing another switch after 3 months.

– Looking forward, we will make it so that all of our documentation exposes the version information in the URL. So, for Exchange 2010, that would mean that you will see (EXCHG.141) as part of the URL, and for Exchange 2013 you’ll see (EXCHG.150). These are the URLs that will be used in the navigation elements on TechNet and in links in the content. Version-less URLs will still point to the latest version of the specific article. However, as version-specific URLs will be available (and visible when you browse our documentation) for everything, we expect that the use of version-less URLs will decrease over time. In other words, any Library topics you link to (by copying from your browser’s address bar) will have the version identifier.

We are hoping that this course of action will provide the right balance of what a set of our customers want and our ability to still optimize discoverability of content across multiple product versions.

Exchange Documentation Team

View this post online.

Apple IOS 6.1.2 Resolved issues with Exchange

Apple today released iOS 6.1.2, the latest iteration of the mobile operating system for iPhones, iPads and iPod touch devices, following widespread reports of errors caused by calendars connected to Exchange servers.

Both Apple and Microsoft began investigating reports that those running iOS 6.1 update caused overloading on corporate Exchange email servers. Some enterprises complained that their newly updated iPhone or iPad were “causing excessive logging” on the server. As soon as the iOS 6.1-powered device was switched off, the problem mysteriously went away.

But the effects of the bug also caused the battery life on the iPhone or iPad to suffer significantly.

Microsoft came up with a few ideas to prevent the overloading, such as switching off the calendar function altogether or simply banning all iOS 6.1 users from accessing the network.

iOS 6.1.2 arrives on shiny rectangles of multiple sizes just over week after iOS 6.1.1 was released, which fixed cellular performance and reliability problems for iPhone 4S users.

Some iPhone 4S users in Europe complained that the latest upgrade caused cellular and 3G networking to degrade. U.K. and European carriers sent out text messages to customers warning them not to update to the latest version of the mobile platform as it was causing their own networks to suffer.

After this update, we tried looking the TMG logs for “cmd=meetingresponse” and found no repeating logs, suggesting that it has been fixed.

Regards

Msexchangeanywhere – Team.

By msexchangeanywhere Posted in Apple, IOS

Exchange 2010 SP3 RTM

Exchange Server 2010 Service Pack 3 (SP3) has been released, raising the Exchange version number to 14.3.123.4.

For those still unaware, the 550 MB file contains the full set of binaries; you can use it to upgrade existing installations or deploy new Exchange 2010 SP3 installations.

Besides the usual set of fixes, SP3 introduces the following features:

· Exchange 2013 Coexistence
This Service Pack for Exchange 2010 adds coexistence with Exchange 2013. However, it requires Exchange Server 2013 Cumulative Update 1 (CU1), which hasn’t been released yet.

· Windows Server 2012 Support
This Service Pack enables you to deploy Exchange Server 2010 on Windows Server 2012 platform.

· Internet Explorer 10
You can now use Internet Explorer 10 to connect to Exchange 2010.

· Sent Items Management
You can now control behavior of Send-As or Send-on-Behalf messages regarding the folder used to store a copy of the sent message. This mimics Delegated Send Items options available in Outlook.

Be advised that after installing SP3 on Mailbox servers, the databases are upgraded to the SP3 version database schema. An SP3 database can’t be mounted on pre-SP3 Mailbox servers. Keep this in mind when upgrading your DAG (you will temporarily have limited fallback or switchover options) or for example when relying on database portability for some reason. Note that upgrading databases can be time consuming, especially with RTM or low SP version databases as the database will be upgrade from RTM to SP1, SP1 to SP2 and finally SP2 to SP3.

After preparing your forest for Exchange 2010 SP3, the schema version number will have changed.

You can download Exchange 2010 SP3 here.

The UM language packs for SP3 can be downloaded here. Note that you need to uninstall previous UM language packs before you can install the SP3 versions.

Exchange 2010 SP2 Rollup 6

Today the Exchange Team released Rollup 6 for Exchange Server 2010 Service Pack 2 (KB2746164). This update raises Exchange 2010 version number to 14.2.342.3.

In addition to these fixes, this Rollup also includes a fix for the security issue described in Microsoft Security Bulletin MS13-012 and new daylight saving time (DST) updates.

As of Rollup 4, it’s no longer required to disable/re-enable Forefront Protection for Exchange using the fscutility to be able to install the Rollup properly. However, if you want to remain in control, you can disable Forefront before installing the Rollup using fscutility /disable and re-enable it afterwards using fscutility /enable.

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

As with any Hotfix, Rollup or Service Pack, I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production.

You can download Exchange 2010 SP2 Rollup 6 here.