Exchange

image.png

Review MigrationWiz

0

Because I’m doing more and more Office 365 migrations I was looking for a solution to automate this proces. I was looking for a tool that could automatically migrate mailboxen, contacts, public folders etc. Ofcourse using PST-files is one way to do it, but when you are migrating lots of data (Gb and/or users) this could take some time. I’ve heard the name BitTitan several times their product MigrationWiz seems to good to be true. I decided to ask them for a trial license to test the product.

MigrationWiz doesn’t require any special software, this because it’s all webbased. Just go to the website and login. After logging in you see the following :

image

First you have to create a connector. A connector is the link between your old en your new environment. Setting up a connector is an easy thing to do :

image

In the above picture you can any source configuration you are using, you can choose the same options in the target. So you can use MigrationWiz for the fallback scenario also.

You can also specify what to migrate :

image

Ofcourse you can migrate emails, but also calenders, contacts but also the rules(!) I particularly like that option because I created many rules to move incoming mails to their folders and their is no other easy way to export/import those.

After creating your first connector you can find it in the manage connector section :

image

In this view you can easily edit the connector, view statistics and see the mailboxes you are about to migrate.

After creating the connector you can add the mailboxes you wish to create. Their are several ways to do that. First you can manually add them :

image

You don’t have to have each user’s password. You can select one migration account which has access to all the exchange accounts.

Another way is to do a bulk import :

image

As you can see in the above screen, everything is fairly easily and their is little room for mistakes. It would be nice although if you could select the mailboxes from a list that MigrationWiz provides but that option isn’t (yet?) available.

After adding the mailbox(es) you can start the migration with the option buttons :

image

The first button is to start the migration, the second gives you the details, you can change the settings of delete the mailbox from MigrationWiz (not Exchange!)

After starting the migration you can see the progress in detail :

image

image

image

 

image

 

At this point you just have to wait for the mailboxes to complete. :-)

Other thing I think are worth mentioning :

Migration Skydrive / Google Drive data :

image

Migration Public Folders :

image

It’s also possible to export all your exchange data to PST for back-up or legal reasons :

image

Conclusion

I’m very enthousiastic about MigrationWiz and I think I will testdrive their other products also. Migration maildata is easy and works as it supposed to. Some minor improvements would be nice like the option to select the mailboxes instead of importing them with one of the bulk options. I also noticed that the impact on the source exchange system is noticeable, but you can tweak the options. So look out for importing all your exchange data during daytime without looking into the tweak options.

Do you have any questions? Leave a comment!

 Functionality  
 Stability  
 Support  

Do you like this review? Please vote!

 

image.png

Exchange Service Packs (overview)

0

For some reason I was looking for a quick overview with all the Exchange Service Packs available.

image

Check the link out here. I also noticed that Michel de Rooij has a line-up also check it out : http://eightwone.com/references/versions-builds-dates/

Messages stuck in Exchange 2010 queue (resolved)

0

Today a collegae of mine ran into a problem with Exchange 2010. Messages both internally/externally were not delivered. We noticed that the Exchange server was using 100% CPU resources.  After some investigation we noticed that the submission queue was building up.

We decided to suspend the queue, exporting the messages. Then deleting the queue and recreating it. Finally we imported the exported messages. We used the following steps :

First open the Exchange Management Shell

Show all Exchange queues

get-queue

Suspend all messages in this queue

get-queue exchangeserver#submission | get-message | suspend-message

Export all suspended messages

$array = @(Get-Message -Queue "ExchangeServer\submission" -ResultSize unlimited) 
$array | ForEach-Object {$i++;Export-Message $_.Identity | AssembleMessage -Path ("c:\Mailqueue\"+ $i +".eml")}

 

[image%255B2%255D.png]

Stop the MsexchangeTransport service

Stop-Service MsExchangeTransport

Now rename the queue directory, the default directory is

[image%255B26%255D.png]

Startthe MsexchangeTransport service

Start-Service MsExchangeTransport

Solved : All Exchange 2010 services disabled after update

0

Today I ran into a problem after updating Exchange 2010. After a reboot (which took ages!) I noticed that all the services were disabled. After some troubleshooting I found out that the problem had something to do with an installed update. My resolution (and was planned) was to install the latest servicepack (SP3). There is one drawback, the services are disabled and Exchange SP3 setup is unable to stop/start them.

I used this powershell command to set the service to manual :

Get-Service MSEx* | Set-Service -Startuptype manual

During the install I had to execute this command 2 times, the SP3 setup worked fine and after that the services were automatically started.

image.png

Link : all Exchange Servicepack’s and RU’s

0

I ran into this great wiki article from Microsoft from where you can find and download (!) all the Exchange 2003/2007/2010/2013 servicepack’s and fixes. You can also check all the build versions.

image

You can find the link here.

Update : a co-worker attended me of the continued list of the link above here

schema001.png

Exchange 2010/2013 : Unable to find schema master

0

Some time ago I ran into an error while installing Exchange. It seems this problem also occurs when upgrading/installing an Exchange Server service pack. This is how to fix this problem :

First go to the (root) domain controller and register the schema extension :

regsvr32 schmmgmt.dll

Now load the plugin by starting mmc and adding the extension

Now right-click the Active Directory Schema en select Change Active Directory Domain Controller. (Choose the domain controller you wish to transfer the schema role to)

schema001

Hit ok when you receive the read-only warning.

Now select Change Schema Master and hit Change.

schema002

adsi001.png

Exchange 2003/2010 cross forest routing problem solved

0

For a customer I ran into a strange problem. While doing a cross forest mailbox migration I noticed that mails were queuing up and were not delivered. It took some troubleshooting untill I found the solution. First I noticed that newly created users received email for several domains without any problems. Migrated users didn’t receive any external email.

I opened the user’s properties with ADSIEDIT and I noticed the old email addresses on the targetaddress field. I decided to delete the values and re-register those email addresses using the Exchange console. The user concerned received external email immediately .

adsi001

Because it’s a cross forest migration we are using ADMT for the user migration. It’s possible to exclude this value and doing so will prohibit to these old values being migrated to the new domain.

adsi002

PF_error.png

Exchange 2010 move database error WMI exception occurred..

0

Today I tried to move a database to a different drive and I ran into the following problem :

PF_error

After some investigation I noticed a large amount of log files. After enabling circular logging and dismount and mounting the database everything went fine! Disable circular logging afterwards and make sure your backup solution is running working and flushes the logfiles correctly.

SMTP01.png

Howto : Split SMTP domain Exchange 2003 and … (2010, Zimbra etc)

1

This is how to create a split SMTP domain using Exchange 2003 and another SMTP program like Exchange, Zimbra or something like that.

Step 1. Make sure you’re MX-record is already point to your Exchange 2003 mailserver and that part is working.

Step 2. Add the new domain name to the Recipient Policies:

 

SMTP01

Make sure the “This Exchange…” is not selected! (That’s important)

SMTP02

Now create a new SMTP connector :

SMTP03

Fill the IP-adres in brackets [] and select an Exchange 2003 server using Add.

SMTP04

Goto Address space, add the new split SMTP domain and select the Allow Messages to be relayed option.

At this point the mail which can’t be delivered at the Exchange 2003 is being forwarded to the IP adres specified. At this point you have to make a receive connector (Exchange 2010 for example) or something else.

InlineRepresentatione3d27700302c4a0c825f364546784bd2.jpg

How to : Publish ActiveSync using TMG 2010

0

A follower of my blog asked me how to publish Activesync using TMG. I thought I already write a blogpost about it, but couldn’t find it. So I wrote another post. See the screendumps for some explanation.

In my case I had to adjust (enable) basic authentication :

IIS rights

  • Sponsors

  • Trilead
Go to Top