Search results for 'app:weblogs' matching tags 'Blackberry' and 'Exchange'

Exchange 2010 Service Pack 2 available

TBittner — Mon, 05 Dec 2011 06:00:00 GMT

You can download it from here

http://www.microsoft.com/download/en/details.aspx?id=28190

Exchange 2010 SP2 is a complete installation software pack, so for new Exchange installations, you can use it to start with from scratch.

Also when you use it for updating your current installations, be aware that you need Schema- and/or Organisaiton Administrator rights, because it contains a Schema update for your Active Directory.

And this Schema update needs to be execute in the domain where the Schema Master Role exist. So run setup /prepareAD not in the domain where you operate your Exchange Servers, it will not work. You need to go to the root domain, if there is the Schema Master or you have to move the Schema Master on to a domain controller in the domain where you operate your Exchange environment.

And remember that you should wait for replication across your AD after you’ve performed the Exchange 2010 SP2 Schema update.

During you’re waiting for replication, you can use the time to install the ‘IIS 6 WMI Compatibility’ feature. It is mandatory for your following Exchange 2010 SP2 installation, because of the new ‘Outlook Mini’ feature, which requires this feature on your CAS server roles.

Schedule

5 minutes for /prepareAD
15 minutes for replication (more if you have higher replication times set on your site links)
5 minutes for feature prerequisits
30 minutes for finishing SP2 setup per system

so you should be through with it within a hour for your first system and schedule 30 minutes for every following systems …

Reboot after SP2 installation should not be necessary.

And think about to disable Anti Virus Scanning on the box you’re going to perform Exchange 2010 SP2 Setup for upgrade.

Read the prerequisits before starting your installation

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

Exchange for Hosters

TBittner — Tue, 30 Aug 2011 05:00:00 GMT

As you know, this feature was removed from the current version of Exchange. There are some features back with Exchange 2010 SP1 back not as we had it in the past with legacy versions.

Now with Exchange 2010 SP2 we will get back functionality on a standard On-Premise Exchange environment.

Read

http://blogs.technet.com/b/hameroff/archive/2011/08/08/so-you-want-to-host-exchange.aspx

and

http://blogs.technet.com/b/exchange/archive/2011/08/30/exchange-server-2010-sp2-and-support-for-hosting-exchange.aspx

Issue with Exchange 2010 SP1 Rollup 3 and Blackberry [Update]

TBittner — Wed, 16 Mar 2011 05:00:00 GMT

The Microsoft Exchange Team has received notification of an issue impacting some customers which have RIM BlackBerry devices connecting to an Exchange 2010 SP1 RU3 environment. Now the team actively working with RIM to identify the exact scenarios in which customers are reporting this issue in order to narrow down the root cause of the problem and identify a suitable resolution for it.

Therfore you are currently not able to download the Exchange 2010 SP1 Rollup 3 anymore and have to wait for a replacement.

iPhone, OWA Premium and POP3/IMAP4 issues with Exchange 2010 SP1

TBittner — Thu, 02 Sep 2010 05:00:00 GMT

After applying E2010 SP1 iPhone users may not be able to view the content of incoming messages in their Inboxes, and when they try to open a message, they get an error that this message has not been downloaded from the server.

Also OWA Premium users may not be able to reply or forward a message. They may see the following error in OWA:

‘An unexpected error occurred and your request couldn't be handled. Exception type: System.ArgumentException, Exception message: imceaDomain must be a valid domain name.’

And POP3/IMAP4 users may also not be able to retrieve incoming mail.

The issues are caused by non-standard domain names. Verify that there is one domain marked as ‘Default’ and it's DomainName and Name values are valid domain names, and e.g. don’t have a space within the domain name.

Comprehensive Guide on Addressing Exchange Calendaring Issues

Anonymous — Tue, 27 Jul 2010 05:00:00 GMT

Rand Morimoto wrote a great article for Network World about Exchange calendaring issues. Rand is the president of Convergent Computing, the company I work for. His article covers lost appointments, duplicate appointments, odd delegate issues, etc. This article is based on the real-world experience we as a company have gained working with many organizations of all sizes.

I wanted to add a few comments of my own, to follow up on to Rand's excellent article.

Another factor that can cause calendar issues for delegates is Cached Exchange Mode, which can cause an artificial delay in updating calendar information. For example, the boss (using Entourage, which doesn't have Cached Mode) may accept or alter the same appointment that the assistant (using Outlook in Cached Mode) accepts or alters. The default Cached Mode settings may cause a delay of up to a minute before the assistant's calendar item is updated on Exchange. Who wins is anybody's guess.

By the way, my recommendation is to adjust the Cached Mode latencies to 1 second using Group Policy. There is virtually no network performance impact and it solves a lot of issues, especially "perceived performance" issues. See http://support.microsoft.com/kb/870926/%20target=.

Regarding BES, RIM is making quite a few changes recently due to inconsistency problems (especially in calendaring). BES 5.0 SP2 is supposed to make huge performance improvements so that BES IOPS are now equal to Outlook (see http://flaphead.com/archive/2010/07/24/bes-5-0-sp2-blackberry-user-exchange-2010-iops-now-equal-to-an-outlook-client.aspx). The rumor is that BES 6.0 will completely re-architect BES to use Exchange Web Services (EWS) rather than MAPI.

That said, BES changes versions as often as we change socks. I find that most orgs are WAY behind on BES versions from the current version, so they can't take advantage of these improvements. And as with any other technology with massive changes, it will probably introduce a new set of unknown problems.

Being that calendaring issues are 99% due to client issues (Outlook, Entourage, BES, iPhone, etc.), I expect that most of these issues will go away as the clients move toward using EWS. The problems documented in Rand's article occur because of the way the clients handle calendaring/email objects. If the client software lets Exchange handle these objects using standard EWS APIs, the problems will diminish/disappear.

BlackBerry Enterprise Server (BES) and Microsoft Exchange Server 2010

TBittner — Thu, 10 Dec 2009 06:00:00 GMT

Microsoft recognized that many customers rely on BlackBerry Servers. This is why they collaborated already closely with RIM to add BlackBerry Support to Exchange Server 2010.

BlackBerry Enterprise Server (BES) is now fully supported on Microsoft Exchange Server 2010 and BlackBerry Technical Support Services are readily available.

In order to enable full support, this updates are required:

All three of these updates are available to customers of Exchange Server 2010 and BlackBerry Enterprise Server v.5.0 with Service Pack 1 at no cost. BlackBerry Enterprise Server v5.0 Service Pack 1 and Maintenance Release 1 can be found here: http://www.blackberry.com/support/downloads

Additional information on the solution requirements, preparing the BlackBerry environment for Microsoft Exchange Server2010, can be found on the BlackBerry site here.

Exchange Server 2010 Roll-up 1 also includes other minor updates to areas including calendaring, OWA, and transport. You can read more about Exchange Server 2010 RU1 here.