Wednesday, 8 April 2009

Migrating SANS for Exchange 2003 A/P clusters

This is usually a really fun late night affair :-)


Here are the basic steps outlined for an easy pain free move:


1. Pause passive node in Cluster Administrator then take passive cluster node offline

2. Add new HBA's

3. Fire up passive node, connect fibre from HBA's to fibre switches on new SAN and configure zoning etc.

4. Present disks to passive node, then re-scan via disk managenet and ensure you've picked up new disks

5. Add drive letters and format

6. Fail cluster over

7. Take cluster offline, add disks as Physical Disk resource in Exchange Resource Group and add disks as a dependancy of SA.

8. Bring cluster online

9. On new passive node repeat steps 1 through to 4.

10. Fail cluster over to ensure both nodes can successfully bring their resources online and see both disks

11. Now just move the databases via ESM to new SAN disks.

12. Quorum is moved in Cluster Administrator

13. EVS disk - I take the cluster offline then copy all EVS data to the new EVS disk.

14. Once that is done remove the EVS disk from Cluster Admin and add the new EVS disk with the original drive letter name. Then bring cluster online.
15. Removing the old SAN hardware - removing the disks from Cluster Admin and then at an appropritate time take each node down and remove legacy HBA's

16. Power down legacy SAN and remove from racking




Oliver Moazzezi

MVP - Exchange Server

Tuesday, 7 April 2009

Named Properties handling changing in a future RU for Exchange 2007 SP1?

Most excellently written and described in detail here:

http://msexchangeteam.com/archive/2009/04/06/451003.aspx

From the Conclusions statement it appears to be coming in a future Roll Up for SP1!


Oliver Moazzezi

MVP - Exchange Server

Friday, 3 April 2009

Applying an Exchange Service Pack to an Exchange 2007 UM Server


If you have extra language packs installed (very likely if you’re outside of the US!) then you need to first remove them before you can SP Exchange on your UM Server.


To find out the language packs installed you can use the Get-UMServer cmdlet:















Once you have ascertained what ones are installed you use setup to remove them

Command: setup.com /RemoveUMLanguagePack:en-GB

This will remove the en-GB language pack I had installed.
















You can then Apply your Service Pack:
















Once your SP has been installed correctly. You can re-install your language pack


Command: Setup.com /AddUmLanguagePack:<UmLanguagePackName> /s: d:\<languagepackfilelocation>






















Don’t forget to re-select the language on your associated Dial Plans:




















Here’s a link to the available Language Packs:

http://www.microsoft.com/downloads/details.aspx?FamilyID=2b3e23a5-57b6-4a11-8954-f8025ea54bad&displaylang=en



Oliver Moazzezi

MVP - Exchange Server







Friday, 27 March 2009

Exchange Remote Connectivity Analyzer (ExRCA) tool Released

Microsoft have just released there Remote connectivity Analyzer tool this allows you to perform testing of your Exchange 2007 services remotely from a web page ! awesome hey

Allows you test ActiveSync, Autodiscovery, Outlook Anywhere connectivity and inbound mail too. Very useful for testing your configuration is setup correctly but can also be used for testing after maintenance has been performed on Exchange to confirm it's all working correctly etc

https://www.testexchangeconnectivity.com/

More information can be found here : http://msexchangeteam.com/archive/2009/03/25/450908.aspx

Enjoy !

Wayne Hollomby

Xobni leaves beta and launches finally!

After almost one year of beta testing, Xobni has launched Xobni 1.7, which is the first version without the beta label. v1.7 dramatically improves the performance and reliability of Xobni with the following improvements:

  • Outlook now starts 31% faster
  • Xobni Profiles now load 42% faster
  • Users can control how often and how much data xobni indexes
  • Users can control when Xobni is running

    If you've got Xobni installed (I do and it's still very useful and effective) then you need to run their installer to receive the latest release http://www.xobni.com/download


     

    Dan - http://twitter.com/dan_germain

Tuesday, 24 March 2009

Exchange 2003 OWA, Exchange 2007 OWA and Internet Explorer 8

Currently no real issues to report. All seems to be working perfectly. You may have IE Topbar prompts if using a Self Signed Cert - not a problem though for 99% of Hosters.


Oliver Moazzezi

MVP - Exchange Server

Friday, 20 March 2009

Update Roll-up 7 for Exchange Server 2007 Service Pack 1 has been released.

RU7 for SP1 is out:

http://msexchangeteam.com/archive/2009/03/18/450863.aspx

Some of the most important fixes are listed below (taken from above Exchange Team post):


First off, we fixed the SCR issue which have caused everyone some pain and which did not get completed in time to be included in the last update roll-up.KB 961281 Update Roll-up 5 for Exchange Server 2007 Service Pack 1 introduced an issue where you receive an error when attempting to enable SCR on a storage group if the environment has a parent domain -> child domain active directory structure. Tim has blogged about this over here. This is now fixed. Additionally, there are also 2 other SCR related issues which we have been addressed in this roll-up and have been asked for by many customers.KB 957834 Network shares are deleted and created intermittently by the replication service on an Exchange SCC cluster when SCR is enabled on the Exchange server
KB 958331 Restore-StorageGroupCopy command may fail in an Exchange Server 2007 SCR environment.
We have also fixed two issues which caused intermittent crashes in the IMAP4 service and resulted in event 4999 being logged in the event logs. The following KBs have more information on the scenarios which are fixed: KB 957504 and KB 960292.




Oliver Moazzezi

MVP - Exchange Server

Thursday, 19 March 2009

Hosted Exchange prior to RPC over HTTPs / Outlook Anywhere

Back when hosting Exchange 2000 and 2003 RTM an Exchange Hoster had limited options when opening up MAPI to their client base. The options basically were:

1. Require the customer to use a VPN, do not use Static MAPI ports
2. Require the customer to use a VPN, use Static MAPI ports
3. Have MAPI open over the Internet, use Static MAPI ports, directly NAT to Exchange Server
4. Have MAPI open over the Internet, use Static MAPI ports, NAT but filter traffic to Exchange Server


1. Is a fairly simple affair. However I found customers didn’t like the addition of having to setup a VPN across their desktops and remember to login to it.
2. Again this achieved nothing more than option 1
3. This was the easiest way to connect, however it totally opened up Exchange Servers to the Internet. Seeing Outlook queries Exchange initially using RPC (Port 135) you would be open to worm attacks like the famous Blaster Virus
4. The same as the above, but hopefully with better protection in protecting against attacks, virii or worms.


3 and 4 also opened up issues with customers connecting to Exchange Hosters. When the Blaster virus took hold Networks across the World were locking down Port 135 on their networks to try and stop machine infection. This caused a lot of issues unless you had a VPN option in place for customers.

My preferred method of access is RPC over HTTPs (Introduced in Exchange 2003 Server SP1, known as Outlook Anywhere in Exchange 2007 RTM/SP1). This requires Outlook 2003 as a minimum to work. This in certain circumstances can cause more overhead for an Exchange platform to the traditional MAPI protocol. However it certainly has its benefits.

Outlook Anyhwere (I will refer to this for both Exchange 2003 and 2007 from here on) allows the encapsulation of RPC over SSL. You receive your MAPI connection by using the RPC Proxy Service (usually installed on an Exchange Front End) and connecting to your OWA url.

I advise this as the best way to connect to Exchange over the Internet. Simplifying connection for users and allowing a more secure Exchange platform for an Exchange Hoster.


References

“Exchange Server static port mappings” http://support.microsoft.com/kb/270836

“Overview of Outlook Anywhere” http://technet.microsoft.com/en-us/library/bb123741.aspx

“How to configure RPC over HTTP in Exchange Server 2003” http://support.microsoft.com/kb/833401


Oliver Moazzezi

MVP - Exchange Server

Thursday, 26 February 2009

Outlook 2007 update available!

You can grab the update here: http://support.microsoft.com/?kbid=961752

A full list of changes for Outlook are here http://support.microsoft.com/?kbid=968009, they're included here:


General responsiveness
The overall responsiveness for Outlook 2007 SP2 is significantly improved over the responsiveness of Service Pack 1. Responsiveness can be loosely defined as the application's reaction time when you use the user interface (UI). A perfectly responsive application will always immediately begin performing the task that is requested even if that task takes a long time. For example, in Outlook this could be clicking to switch folders while you wait for a very large folder to load, and clicking the ToDo Bar to enter a task. Making Outlook noticeably more responsive was a big priority for this release.

Storage engine
The most important changes come from underlying optimizations in the local storage engine. Both Personal Folders files (PSTs) and Cached Exchange Stores (OSTs) are built upon the same underlying storage engine. In this article, PST refers to both technologies. We have improved the general reading and writing characteristics of the PST so that less is demanded from the disk to perform the same general operations in Outlook. For example, file flushing is optimized so that it interacts more efficiently with the operating system and disk write caches. We have also changed the way new data is written to the PST. Now, it is saved much closer together on the physical disk and requires less physical work from the drive. This speeds up the time that is required to write the same amount of data. A side effect of this data writing algorithm is that PSTs are approximately 20 percent larger than in previous releases. However, we have observed large gains in write performance and a reduction in overall writing to the disk. Whereas write optimizations have been the single biggest change in the storage engine, there are also other small changes that deliver additional benefits. For example, internal storage engine optimizations were made after analyzing the most common kinds of operations the storage engine performed during typical usage. We have also optimized the way internal "change notifications" are processed, especially when there are many of them. Specifically, when you add significant data to the PST, lots of notifications are triggered for various data structures to be updated to accommodate the new data. Because these notifications are faster and require less I/O, the raw performance of every small operation improves. This means significant savings over time.

User interface
In addition to optimizing the storage engine, Microsoft spent time and resources investigating and addressing some common sources of unresponsiveness in the Outlook application layer. We have seen that some of the most frustrating instances of unresponsiveness occur when Outlook is doing work unrelated to any user actions. Such situations are especially frustrating because the user cannot predict when they will occur or how long they will last. Two of the more common causes of Outlook unresponsiveness that are unrelated to user action were processing updates to the message list and processing updates to other elements in the main window in Outlook. Our engineering team undertook a complex effort to fundamentally change the methods in which such updates are processed to minimize their effect on Outlook responsiveness in SP2.Some other application layer changes that we made are for scenarios that may not affect all users. However, we believe that these scenarios are a significant source of dissatisfaction to the users who are affected. For example, when the reminders dialog box appears, the prior behavior was to process and write the changes to the store immediately when the user requested an operation such as dismiss or snooze. Now, those changes are queued so that responsiveness is immediately restored to the UI. Therefore, you can click Dismiss as fast as your mouse will allow, and when the last reminder goes away, the dialog box will immediately disappear. We also made some changes to the way rules are processed so that many client-side actions, such as moving mail from a specific distribution list to a separate PST file, leave the Outlook UI far more responsive.We have also made changes specifically targeted at customers who use POP and IMAP servers. For POP mail users, we now retrieve the newest mails first, which hopefully helps you get to your most important work faster. IMAP mail users will notice that downloading message bodies no longer stops Outlook from responding to additional user commands.

Starting Outlook
Our approach to optimizing the startup process is fairly straight-forward. We analyzed all the tasks Outlook queues and improved the boot time by removing a few operations that were considered unnecessary, and by better orchestrating the execution of the necessary tasks. The result is a noticeable positive improvement. Quantifying the exact improvement is difficult because most people's experiences vary widely based on several factors. These include the following:
Number of add-ins
Amount of memory on the computer
Speed of the hard disk drive
Number of other applications currently running
Size of the mailbox and size of additional stores mounted (overall optimizations in the PST also help here)
Number of customizations made to the UI that must be loaded

Essentially, we have seen Outlook starting about two times as fast in many of our tests and in our own experience running the builds for our daily mail use.

First startup experience
Immediately after you install the SP2 update, the first startup of Outlook will not be fast because Outlook must update internal PST data structures that are used in our optimizations. This is a one-time cost however, and affects just the initial startup. As soon as the data structures are updated, Outlook can then benefit from the improvements. We hope that, as soon as the upgrade process is complete, and you begin to see Outlook 2007 SP2, you see that the rewards were definitely worth the wait. There is a new upgrade dialog box with progress to show some optimizing work Outlook is doing to make everything faster on the disk.
Collapse this imageExpand this image
The responsiveness of Outlook will improve after this dialog box closes. If you choose to create a new profile and resynchronize your mail, the storage upgrade happens dynamically as new content is added to your new local data file. Therefore, there is no upgrade dialog box. However, some non-responsiveness that is associated with the first startup may occur. Again, after several minutes, Outlook responsiveness will improve.

Shutdown
Outlook had built-in logic that caused it to refuse to shut down when it detected that a third-party was using it for data access or otherwise was integrated with Outlook functionality. A side effect of this design was that, to the user, Outlook would frequently not exit for no apparent reason. If all storage providers support it, for SP2, we have optimized for the user's choice to shut Outlook down by stopping all server activity, flushing unsaved PST content to the disk, saving unpersisted preferences and settings, and then quickly exiting. Most notably, Outlook no longer waits for external references to be released. Note Outlook Live Connector (OLC) 12.1 does not support this faster shutdown. Therefore, Outlook must continue to use the slower shutdown method when OLC 12.1 is being used to make sure that data is not lost.The result is a consistently reliable shutdown, even during periods of heavy activity, such as server synchronization. There is more technical information (http://msdn.microsoft.com/en-us/library/dd239276.aspx) available for developers about how to update their applications to best integrate with this new shutdown model. Our goal is that Outlook shuts down quickly (in just a few seconds), reliably and consistently. Also, a new Outlook icon appears in the notification area after you close Outlook, but the Outlook.exe process is still running. As long as the Outlook.exe process is running, and the Outlook UI is unavailable, the
Collapse this imageExpand this image
Outlook icon appears in the notification area.

Folder/view switch
For folder switching and arrangement switching, we have developed a highly optimized, very compact new index of the folders' contents that is sorted by date. A date sort is the foundation of the most frequently used contents table arrangement. Being able to load a very small and always up-to-date version of this index in a short time is the backbone to a very fast folder switch experience in SP2. The new date index is much more effective, even with tens of thousands of items in a single folder.The result is that switching to even the largest folders takes mere seconds, although sometimes the first switch to the folder can take longer while we build up the indexes. This, again, is a one-time cost. Note Most of these gains are seen when you use Outlook in Cached Exchange Mode together with OSTs and PSTs. Online Mode users will continue to see their view performance dictated largely by server performance and network conditions.


Enjoy a speedier Outlook 2007,



Oliver Moazzezi

MVP - Exchange Server

Wednesday, 1 October 2008

Can't migrate accounts using Transporter Suite for Internet Mail









I was testing this in my lab, and of course used the default Administrator account. I kept getting the error of :

Warning:An item has failed property validation and will be ignored.
IdentifierName: Subject of message in inbox
Error details:Required property is empty.
Property:TargetServer..

I had created the correct impersonalisation permissions on the Client Access Servers and also added the following line into the EWS web.config file to allow mail to be imported over 3mb:

httpRuntime maxRequestLength="100000" / (in <>)

However I was still getting this error.

I then remembered reading an article on TechNet about the Administrator account not being able to log on via IMAP4 or POP3, as it is hard coded to be blocked by default.

I then created a 'migration' account user in AD, and gave that using Exchange Administrator permissions and the relevant impersonalisation permissions, and was able to succesfully migrate Internet email into Exchange using both POP3 and IMAP4.

You can download the Microsoft Transport Suite of tools here:

http://www.microsoft.com/Downloads/details.aspx?familyid=35FC4205-792B-4306-8E4B-0DE9CCE72172&displaylang=en


Oliver Moazzezi

MVP - Exchange Server