백서

어떠한 문제라도 극복 가능하고 Lotus Notes 및 Domino에서 매끄러운 마이그레이션을 할 수 있도록 돕는 7가지의 단계와 최고 실천 사례를 배웁니다.

자세한 정보 »

데이터시트
ZeroIMPACT Notes에서 Exchange 및 Exchange Online으로의 마이그레이션 방법을 확인해 보십시오.
자세한 정보 »

Notes Migrator for Exchange

Microsoft Exchange로의 ZeroIMPACT Lotus Notes 마이그레이션 경험

Notes Migrator for Exchange는 복잡성 제거, 마이그레이션 가속화, 데이터 손실 및 다운타임 위험 완화를 통해 Lotus Notes 마이그레이션 프로젝트가 성공적으로 실시될 수 있도록 해줍니다.

이메일, 일정, 작업, 개인 주소록, 아카이브, 정기 회의, 첨부 파일 등의 마이그레이션을 최단시간 내에 신속하고 정확하게 실시할 수 있습니다.

Notes Migrator for Exchange를 사용하시면 다음을 할 수 있습니다.

  • 다중 메일박스를 동시에 마이그레이션
  • Outlook 메일박스 생성 및 메일 라우팅 등의 관리 업무 자동화
  • 호스팅된 플랫폼으로 데이터 직접 전환
  • 각 사용자 메일박스의 무결성을 유지하여 정확하고 간결한 마이그레이션

Notes Migrator에는 Migrator for Sametime 이 포함되어 있어 Lotus Sametime에서 Microsoft Lync로 간단하게 전환할 수 있도록 도와줍니다.

기능

  • 신속한 완료 - 각 워크스테이션의 여러 메일박스를 동시에 이전하여 마이그레이션을 신속하게 완료하고 여러 마이그레이션 콘솔을 설치하여 확장성을 높일 수 있습니다.
  • 완벽한 제어 - 각 마이그레이션 작업에 대해 일관된 결과를 보장하고, 세부적인 결과 보고서를 사용하여 필요할 때 조치를 취할 수 있도록 하기 위해 템플릿을 사용하는 직관적인 중앙 콘솔에서 마이그레이션 프로젝트를 모니터할 수 있습니다.
  • 일정 예약 - 관리 작업 자동화를 통해 마이그레이션에 투입되는 인력을 절감할 수 있으며 네트워크 대역폭과 운영에 미치는 영향이 가장 작은 시간대로 마이그레이션 작업 일정을 예약할 수 있습니다.
  • 셀프 서비스 데스크탑 마이그레이터 - 최종 사용자나 관리자가 로컬 및 서버 데이터를 Exchange, 개인 아카이브 또는 PST로 손쉽게 마이그레이션할 수 있습니다.
  • 신속한 클라우드 - 중간 데이터 센터를 거치지 않고 Notes 데이터를 직접 Office 365 또는 호스팅 Exchange로 마이그레이션할 수 있기 때문에 데이터 손실 위험을 완화하고 신속하고 보안성 있는 마이그레이션을 완료할 수 있습니다.
  • 먼저 파악 후 수행 - 사용자 Notes 및 Domino 환경의 사전 마이그레이션 평가를 수행하여 사용자 프로젝트를 계획하고 위험을 최소화합니다.

Sys Reqs

System Requirements

Notes Migrator for Exchange requires the installation and configuration of multiple components on various machines. The admin's migration server in particular will host an unusual combination of tools developed by different vendors, and the combination can cause compatibility problems on some machines. Be sure to see the more detailed System Requirements in the NME Pre-Migration Planning Guide or Quick-Start Guide for tips to get multiple applications from different vendors to cooperate when installed together on an admin workstation.

All machines: Must have network access.

Lotus Domino Server(s)

Supported Domino source environments (all ranges inclusive):

  • Notes 9.0.0
  • Notes 8.5.0–8.5.3, and 8.0.0–8.0.2
  • Notes 7.0.0–7.0.4
  • Notes 6.x and 5.x

Microsoft Exchange Server and Active Directory

Exchange Versions Supported:

  • 2013
  • 2010 (RTM, SP1, SP2 or SP3)
  • 2007 (SP3)
  • MS Office 365, Live@Edu or BPOS-S

If migrating to Office 365 via MS DirSync: The local Active Directory server must have Exchange 2010 SP1 schema extensions.

SQL Server

Access to a Microsoft SQL Server is required, installed on the admin's migration server or on a separate server, with a minimum of 20GB free disk space.

  • You may use an existing (installed) Microsoft SQL Server version 2012, 2008 or 2008 Express or 2008 R2, 2005 or 2005 Express, or 2000, or you can download and install a free copy from Microsoft from the link provided in the NME AutoRun installer.
  • Note that NME running with SQL Server 2008 requires the SQL 2005 Native Client on the admin's workstation to communicate with SQL. The SQL 2008 Native Client is not supported at this time.
  • For best performance of NME's Directory Export Wizard, particularly for sites with a large number of groups or domains, Quest recommends a full-featured (non-Express) edition of SQL Server.

SQL Server Command Line Query Tool also must be installed on the NME admin migration server. You can download it free from the same link provided in the NME Autorun for the Microsoft SQL 2005 Native Client Edition.

Migration Server Requirements (computer running NME admin components)

Supported Operating Systems:

  • Supported for migration to Exchange 2013/2010 or Office 365:
    • Win Server 2003, x86 or x64: SP2 or R2
    • Win Vista, x86 or x64: SP1 or SP2
    • Win Server 2008 or 2008 R2, x86 or x64
    • Win Server 2012 or 2012 R2, x64
    • Win 7 or Win 8, x86 or x64
  • Supported for migration to Exchange 2007:
    • Win Server 2003, x86 (only): RTM, SP1, SP2 or R2
    • Win Vista, x86 (only): RTM, SP1 or SP2
    • Win Server 2008 or 2008 R2, x86 (only)
    • Win Server 2012 R2, x64
  • Exchange BlackBerry: Requirements documented separately below.

Important: NME requires the English-language edition OS/PowerShell on the admin workstation.

Migration server hardware:

  • Must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange.
  • May be a virtual machine, but a dedicated "actual" machine will likely yield better performance.
  • Minimum hardware requirements:
    • 2 GHz dual-core processor, 4GB memory, 20GB free disk space.

Recommendations for improved performance, especially for high-volume migrations:

  • 2 GHz quad-core processor, 8GB memory, 1 Gbps NIC.
  • 1 Gbps or faster network connections among all migration workstations and the Exchange and Domino servers.

Also required for ALL destination Exchange versions, including Office 365:

  • Windows Installer 4.5 (downloadable from this Microsoft link).
  • .Net Framework 4.0.
  • Lotus Notes must be installed in single-user mode and configured. The Notes client version must be in the range 8.5.0–8.5.3 or 8.0.0–8.0.2 or 5.0.11–7.0.4 (all ranges inclusive), and must be able to open all the NSF files that you want to migrate. The client version should therefore match or be higher than the Domino server version.
  • The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange "server" MAPI.
  • 32-bit edition (only) of Outlook 2013, 2010 or 2007, which must be set as the default mail client. If migrating to Exchange 2013 or Office 365, the required Outlook client must conform to Microsoft's requirements for Exchange 2013 or Office 365, respectively.

Also required for Exchange 2013, 2010 and Office 365 (only):

  • Windows PowerShell 2.0, which is installed by default with Windows 7 or Windows Server 2008 R2. For other Windows versions, PowerShell 2.0 is downloadable as part of Windows Management Framework at this Microsoft link. If you are running Windows 7, Windows Server 2008 R2, or Windows Server 2012 then you can use PowerShell 4.0 instead of PowerShell 2.0.

Also required for Exchange 2007 (only):

  • Exchange 2007 SP3 Management Tools (32-bit version), which in turn requires: .Net Framework 2.0, Microsoft Management Console (MMC), and Windows PowerShell 2.0. The 32-bit version of Exchange 2007 Management Tools is available (at this writing) at this Microsoft link, and see also Microsoft's installation instructions.
  • .Net Framework 3.5 SP1 (in addition to the 2.0 and 4.0 required, as noted above).

Also required for Admin Account Pooling feature (Admin Guide chapter 14):

  • Installation of Microsoft Office 365 cmdlets, which in turn require Windows 7 or Win Server 2008 R2.
  • Windows PowerShell 2.0 (installed by default with either supported OS), .Net Framework 3.5 SP1 (in addition to the 4.0 required, as noted above).
  • MSOL Sign-in Assistant, x86 or x64.

On End-User Desktops (if running the SSDM)

Operating Systems Supported

32- or 64-bit edition of any of:


• Windows 8 or 8.1
• Windows 7
• Windows Server 2012
• Windows Vista (Business, Enterprise or Ultimate Edition)
• Windows 2003

Or the 32-bit edition (only) of: Windows XP SP2 or SP3 (Professional Edition)

Required Outlook Client

32-bit edition (only) of
Outlook 2013, 2010, 2007 or 2003.

Note: If migrating to Exchange 2013 or Office 365, the required Outlook client must conform to Microsoft's requirements for Exchange 2013 or Office 365, respectively.

Required Notes Client

Must be running a Lotus Notes client. Unicode support requires one of these versions:


• 8.5.0–8.5.3 (inclusive)
• 8.0.0–8.0.2 (inclusive)
• 5.0.11–7.0.4 (inclusive)

Also required on SSDM end-user desktops:

  • Microsoft .Net Framework version 2.0 must be installed on each end user's workstation.
  • If end users will run the SSDM application from a network share (rather than from each user's own local copy): Each user's workstation must also have either .Net 3.5 SP1 (or later) installed, or a Code Access Security (CAS) policy granting full trust to SSDM in the network share. (See Before Running the SSDM in chapter 4 of the NME Scenarios Guide for instructions to set the required CAS policy.)
  • The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange "server" MAPI.
  • Prior to running the SSDM: Any antivirus software must be configured to not scan the Quest program files directory or %temp% directory, or may simply be turned off, but may be restored after the program runs. If an antivirus scan misinterprets an NME temporary file as a threat, it will try to "clean" the file, which will generate an error when the SSDM program call fails.
  • The computer may be a virtual machine, but a dedicated "actual" machine will likely yield better performance.

Requirements for Migration from Domino BlackBerry to Exchange BlackBerry

Supported Sources: Notes BlackBerry Enterprise Server 4.1.x or 5.0.x

Supported Targets: Exchange BlackBerry Enterprise Server 10.x or 5.0.x

Required on the admin migration server:

  • Operating System: Must be Windows 7 SP1, or Win Server 2008 R2.
  • Windows Powershell 3.0, and Windows Management Framework 3.0.
  • BlackBerry Enterprise Server Resource Kit, a version compatible with the BlackBerry servers. BES 10 requires BES Resource Kit version 6.x. If Domino and Exchange BlackBerry servers are different versions, both must be installed on the migration server.

Required on the Migration Webservice endpoint for BlackBerry migration:

  • Exchange BlackBerry Enterprise Server 10.x or 5.0.x
  • Operating System: Must be Windows 7 SP1, or Win Server 2008 R2.
  • Microsoft IIS 7 or later, with a web application pool running .Net 3.5 SP1 and 4.0. But note: The WebDav component of IIS must be removed by the OS server manager or it will interfere with NME's BES web service requests.
  • Must be reachable from all migration servers.

Server Hosting the SSDM Scheduling Utility Web Service

ASP.net version 2.0 must be installed.

Required Accounts & Permissions

Important: In addition to the hardware and software requirements specified above, NME features require the configuration of admin accounts for access to directory and user data in both Notes and Exchange. For these additional configuration requirements, be sure to see the more detailed System Requirements in the NME Pre-Migration Planning Guide or Quick-Start Guide.

동영상

Docs

사례 연구

Biocon Turns to Quest to Migrate 1,300 Users from Lotus Notes to Exchange Global Ministry Uses Quest Tool to Ensure Seamless Migration to Microsoft Exchange Online Howard Regional Health System Finds Quest Tools are the Remedy for E-Mail Archiving and Migration LP Displays Uses Quest's Solution to Save Millions, Reduce Deployment Time and Unify Its Global Messaging in Migration from Notes to Exchange Server 2007 Notes Migrator for Exchange Serves McDonald’s Deutschland with a Fast and Complete Migration Old Dominion University Completes its Migration Weeks Ahead of the Deadline, Thanks to Quest Notes Migrator for Exchange OTP Bank migrates to Exchange with Dell Software Quest Answers Vodafone's Call for a Seamless Exchange Migration Quest Delivers a Seamless Migration from Notes to Exchange for Top Italian Retailer Sogegross Quest Email Migration and Provisioning Tools Save UK Utility Hundreds of Hours Quest Ensures that Willis' Exchange Migration is Fast, Seamless, with Minimal Risk of Failure Quest Helps Coca-Cola Bottling Co. Consolidated Reduce Its Notes-to-Exchange Migration Timeline by 33 Percent Quest Notes Migrator for Exchange Provides Lend Lease with a Smooth Migration to Exchange Quest Software Quenches Punch Taverns’ Thirst for a Simplified, Minimal-Impact and Reliable Exchange Migration Quest's Spotlight Answers Vodafone's Call for Oracle Performance Improvement, Delivers 500 Percent ROI SK C&C Chooses Quest to Simplify Its Migration from Notes to Exchange Server 2007 STATS ChipPAC Ltd. Completes Merger With Ease, Thanks to Microsoft Swedish Television Station Seamlessly Moves from Lotus Notes to Exchange 2010 with Quest Migration Tool The City of San Mateo Jump Starts Stalled Migration with Notes Migrator for Exchange The Red Cross in Sweden Accurately Migrates 700 Notes Accounts to BPOS in One Weekend with No Disruption to Users The University of Nebraska-Omaha migrates email with no disruption Wiltshire Council enjoys seamless migration to Exchange With Quest's Notes Migrator for Exchange, Brulant Migrates Through An Acquisition 상단으로 돌아가기