How to successfully migrate from Novell GroupWise to Microsoft Exchange?

If you require migrating from your existing Novell GroupWise platform to Microsoft Exchange,then the first very important thing you need to do is a proper planning.

What a migration plan must include?

• The first thing you need to evaluate is you current exiting system. You need to formulate a complete assessment of your current infrastructure.

• After that decide what your objective is and enlist all the challenges that you are going to face during this migration process.

• The final thing you need to decide is “how to gain those objectives and perform an efficient migration”. This would include planning and finalizing all your pre migration and post migration requirements

Common issues while planning GroupWise to Exchange migration:

• The plan must be strategic, logical and easily implementable. Each phase of the migration process and the requirements must be clearly defined. 
• Proper resource requirement analysis, resource scheduling and their management should be done.
• This is not always true that the plan with which you begin will be the same as the migration process goes on. You need to a timely measurement of what’s going on and then may also require monitoring and updating your plan in accordance with the ongoing series of migration events.
• You must keep justifying and testing each phase of migration as the process on. So that if any issue occurs in between you could easily fix that.
• You would require training the administrators and the users so that they can adapt themselves with the changes in technology and user interface.
• You must retain all your previous data after migration. Any kind of data loss is simply intolerable and cannot be born.

How to migrate from GroupWise to Exchange?

The Exchange version before 2007 contained connectors for migration from GroupWise. But these tools are unavailable in later versions of exchange.

Exchange 2003 provides following tools for co-existence/integration with GroupWise:

• Connector for Novell GroupWise: This tool enables GroupWise and Exchange directories to be synchronized so that they can have a consistent address book. Using this connector the Exchange mails can be routed to the GroupWise system.
• Calendar Connector: It facilitates the users to view scheduling information for GroupWise and Exchange both.
• Migration Wizard: This let the users migrate from the GroupWise mailboxes to Exchange

As these tools aren’t present in Exchange 2007 so, if you want to run Exchange 2007 in co-existence/integration with GroupWise during migration then first you need to install Exchange 2003 into the organization. Thus the systems Exchange 2007 and GroupWise system can be run in co existence via the Connector for GroupWise and Calendar Connectors.

The most important step in GroupWise to Exchange migration is “selection of a GroupWise to Exchange migration tool”.

Now, you have two options either you can use the native Exchange 2003 Migration Wizard or get some third party GroupWise to Exchange migration software to make the migration process a lot easier and want to save time..

There are several features that the native migration wizard doesn’t support. 

Some of them are given below:

• Address book and contacts cannot be migrated by the native migration wizard.
• You cannot migrate proxy access using the native migration wizard.
• Shared folder permissions, Archives, GroupWise Distribution Lists and membership, Rules cannot be migrated by the native migration wizard.

So in order to get these requirements fulfilled, you will require a third party GroupWise to Exchange migrator.
 

The third party GroupWise to Exchange migrator also provides several other features that make them more preferable than the native Exchange Migration Wizard.

Some prominent features of a GroupWise to Exchange migrator are:

• It provides an easy to use and interactive interface.
• It let you easily migrate from the GroupWise mailboxes to exchange. You can also convert the GroupWise mailboxes to .pst, .eml and .msg formats.
• It also supports newer GroupWise, Outlook and Exchange versions.
• Let you perform an easy and quick GroupWise to Exchange migration.
• Let you successfully accomplish a risk free, reliable and real time migration without causing any loss to data and mailbox integrity.
• Let you perform selective mailbox migration i.e. you can select one or more mailboxes to be migrated.Also you can choose particular mailboxes as well as particular folders to be migrated from GroupWise to Exchange
• Let you preview the migrated items before actual migration.

So, if the native Exchange migration wizard is able to fulfill your requirements then you can opt for it. But if you want to avail the advanced features of a third party GroupWise to Exchange migrator then choose some software that best suited your needs. You can find a huge list of such software online. Most of the software are available with free demo, you can run the demo versions and can verify their Output. Just do some research about the available software and finally choose the one that best suits your needs and budget.

Read more

Various Issues during Notes to Exchange migration:

Lotus Notes and exchange both are one of the most commonly used email platforms. We can find many organizations migrating from Notes to Exchange. There can be various reasons due to which an organization decides to migrate from existing email platform to a new one. The most common reason for this is specific features available in Exchange that are not present in Lotus Notes.

Common reasons for Notes to Exchange migration:

• As per user experience, most of the users explain Exchange Server as reliable, flexible and cost effective email platform. It provides a bunch of interactive features for easy email collaboration and communication.
• Exchange provides the unified messaging feature which isn’t present in Lotus Notes. In case of Notes the additional functionality needs to be installed separately.
• Exchange provides voicemail to OWA integration functionality. It also supports SATA hard drives. Exchange provides a better look and GUI that also dominates over Notes. Though, Notes provides some new features such as: auto email address completion, vCard support, and mashing up the calendars but still most users found Exchange more impressive.
• As Exchange is best compatible with Windows based operating systems so, Most of the non-technical users find it an easy to use
• Existing Organization is being merged with another organization then there comes a need to create a common email environment. This forces the Lotus notes users to migrate to Exchange in order to bring uniformity.
• Exchange offers various data protection policies for mobile data security. It also let you access mail data, SMS text messages, voice mail, and save IM conversations using a truly universal inbox. Though, it provides only basic mobile experience to users as compared to Notes.

The above described are some common factors leading to Notes to Exchange migration. However, there are other comparative points between Notes and Exchange that forces users/organization to migrate from Notes to Exchange. To know more check out my previous article, “http://recover-email.blogspot.in/2013/07/why-to-migrate-from-lotus-notes-to.html”

Notes to Exchange migration:

Migrating from one platform to another is never an easy task. In the beginning the process seems easier but later on when its actually executed then organizations have to face several issues at various stages. Maintenance of the new platform after migration sometimes also turns a headache for the organization and users. 

So, before migrating from one email platform to another a proper strategic planning must be done and should be implemented with enough technical expertise and knowledge. Some organizations prefer to upgrade their existing notes application instead of migrating to a new platform.

Common Issues occurring during Notes to Exchange migration process:

• Sometimes the organizations decide to migrate from Notes to Exchange but they don’t have an exact idea about Tools, risks, cost and manpower required for the migration process. They simply make an estimate with the help of consultants and other experts to assist and manage the migration process for them. But later on, as the process goes on their estimates proves to be wrong, everything run out of boundaries set before starting the migration process.
• Domino administrator needs to get training about Exchange, its functioning and maintenance. That of course, a huge amount and time needs to be invested.
• It is quite obvious that as you are going to migrate, you will require more hardware and equipments. A truckload of hardware is to be brought. That is one more factor adding to the migration budget.
• End users training will be required for those who have migrated from Notes mail to Outlook. For those users who are not familiar with the working of new client, the learning curve will be more and extra training cost needs to be invested. This would lead to fall in productivity and increase in budget.
• Organizations are going to face several migration issues/risks at various stages of the migration process. Risk mitigation process consumes a lot of resources thus, adversely affecting the productivity. This also increases the pre-decided time span for the migration process to be completed.
• Migrating from the Notes mailboxes to Exchange is the most important step of the whole migration process. An Efficient Notes to Exchange migration tool should be used so that the notes mailboxes can be easily migrated without causing any further issue.  Sometimes some organizations choose to leave the existing notes mailbox data as it is without migrating it to Exchange. And then start with scratch on the new exchange server mailboxes.
• As the administrator and the user continues to use the new email platform. Obviously, they are going to face problems and their queries need a timely resolution. All this leads to an increased need for desktop support.
• With the continuation of the migration process, you would come to know that you are actually investing more than what you have decided prior to the migration process. The result is increased investment, more resource consumption, elapsed time and an ongoing clumsy migration process.
• After the migration is over, testing is required to ensure that all the data has been migrated properly and the newly installed applications and hardware is working properly or not.

If you are thinking to migrate from Notes to Exchange, first go through pros and cons of each, the comparative analysis of applications, the risks and cost involved in migration process etc. The next thing you need to do is to make a strategic plan for migration and then deploy it carefully. If the things are not planned properly, it can lead to disaster.

To know more visit: “How to migrate from Notes to Exchange?”

Read more

Common PowerShell Virtual Directory issues with Exchange Management tools:

The error “500 – Internal Server Error” is a common error that you can have to face while working with Exchange 2010 Server.

This problem occurs:

• When you start the Exchange Management
• Attempt to connect the Exchange 2010 Server remotely using PowerShell

This problem indicates that “There is a problem with the resource you are looking for, and it cannot be displayed.”

You can also face any of the following errors:
 

 

OR

 

OR

 
 

OR

The above errors are caused if the PowerShell virtual directory configuration settings aren’t done properly on the server.

Resolution method:

If the above issue has been occurred on the systems due to Exchange Server Analyzer Tool then apply the following resolution method to fix the issue.

Exchange Server Analyzer Tool: This tools is available as a free download: http://go.microsoft.com/fwlink/?linkid=34707.

It is used to analyze the server data such as: information related to configuration issues, potential problems, and non default product settings. These reports are prepared automatically by the tool and help you analyze the data in a better way.

When you run Exchange Management Tools in Exchange Server 2010, then there are chances that you can have to face the above error or other related issues. If you use the Microsoft Exchange Server Best Practices Analyzer tool that it checks the PowerShell Virtual Directory configuration and other related settings and thus, you can prevent the above issue.
 

Firstly, verify the following components by using the Analyzer tool 

• Locate and verify that the kerbauth.dll file exists at the location specified in the applicationHost.config file.
• The PowerShell Virtual Directory should be using port 80 and its bound to 'Default Web Site'
• In IIS, check that the “Require SSL” option for the PowerShell Virtual Directory has been configured or not.
• The location of the kerbauth.dll file must be C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll and specified there as a Native Module
• If some the components described haven’t been configured properly then user have to face the error “500 – Internal Server Error” while using the Exchange Management Tools.

Kerberos authentication is used by PowerShell for verifying a remote computer connection.
 

A native module is used by the IIS for applying Kerberos authentication check on a remote server. First it loads the module in the virtual directory. While using Exchange Management Tools, in the following two scenarios you can cause an error:

•    kerbauth.dll has been used as a Managed module instead of as a native module
•    or if the module file has been loaded at website level
 

In the above mentioned scenarios the following error message will be prompted:

To resolve the Kerberos configuration issues, follow the given steps:

1.    Run Internet Information Services (IIS) Manager.
2.    Go to Connections> Default Web Site> PowerShell.
3.    Go to the /PowerShell Home pane, double-click Modules and ensure that Kerbauth is a native module
4.    Next, ensure that the path of Kerbauth.dll file is correct.
Location of the file is C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll.
5.    The kerbauth.dll should not be loaded at website level, to check it follow the given steps:

•    Go to Connections > Modules
•    Double click Modules.  Select the option to Configure Native Modules in the Actions pane.
•    Kerbauth module should be registered as a native module. If you couldn’t find Kerbauth in the Configure Native Modules dialog box, you need to register it.
•    To register it, simply open Register Native Module dialog box, enter the details (i.e.  name and path) of the Kerbauth module.  Click OK.
•    To disable Kerbauh Deselct the checkbox corresponding to Kerbauth.
•    Click OK.

The ExchangeInstallPath variable should be added at the System Properties> Environment variables otherwise, following error will prompt while using Exchange Management Tools:

 

To resolve this issue, follow these steps:

•    Go to System Properties> Environment variables> System variables.
•    Add ExchangeInstallPath variable with value C:\Program Files\Microsoft\Exchange Server\V14\
•    After setting the ExchangeInstallPath variable, you need to check the path of PowerShell Virtual Directory in IIS
•    Start IIS. Expand “Default Web Site”> “PowerShell”
•    Go to Actions > Basic Setting> Edit Application. Ensure that the mentioned path for PowerShell Virtual Directory is correct or not. It must be as follows: C:\Program Files\Microsoft\Exchange Server\v14\ClientAccess\Powershell
•    Click OK and exit

If the Require SSL option for PowerShell Virtual Directory has been set Exchange then the following error will occur:

 

Management Tools connects over port 80. The reason behind the error is that if the Require SSL Exchange Management Tools tries to connect on port 443 instead of on port 80 option. 

Follow the given steps to fix the issue:

1.    Open IIS Manager.
2.    Go to Connections > Default Web Site> PowerShell. Open SSL Settings page.
3.    Unckeck the checkbox Require SSL.
4.    Finally click Apply to implement the changes.

I hope the article will prove helpful for those who are facing any of the above errors. Comments and feedback are welcome!

Read more