We have been successfully migrating our Notes users from the primary Notes server to the primary Exchange server using the migration wizard that ships with Exchange. However, we have another Notes server in a remote office on our WAN (one domain) and have installed a second Exchange server to replace the secondary Notes server. The Notes connector is running on the primary exchange server.
We have migrated a few users from Notes2 to Exchange2 by first taking them from Notes2 to Notes1 to Exchage1 to Exchange2. I know this sounds silly but Exchange2 was for a short while in the same closet as Exchange1. So our current setup is Notes1 & Exchange1 in one closet, Notes2 & Exchange2 in another remote closet.
What I want to do is move users directly from Notes2 to Exchange2 avoiding the WAN yet leave the Notes connector on Exchange1. In fact, to speed the conversions up I would like to run them at the same time on both ends of the WAN.
My boss thinks the connector might be a problem and wants to build a test environment. I can't see why the connector would be an issue. Before I have to print more copies of my resume, can anyone shed light on this...will this work?
A+, N+, MCP
We have migrated a few users from Notes2 to Exchange2 by first taking them from Notes2 to Notes1 to Exchage1 to Exchange2. I know this sounds silly but Exchange2 was for a short while in the same closet as Exchange1. So our current setup is Notes1 & Exchange1 in one closet, Notes2 & Exchange2 in another remote closet.
What I want to do is move users directly from Notes2 to Exchange2 avoiding the WAN yet leave the Notes connector on Exchange1. In fact, to speed the conversions up I would like to run them at the same time on both ends of the WAN.
My boss thinks the connector might be a problem and wants to build a test environment. I can't see why the connector would be an issue. Before I have to print more copies of my resume, can anyone shed light on this...will this work?
A+, N+, MCP