EDITORS NOTE
MIGRATING TO
OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365 AND
EXCHANGE
REMEDIATION AND
TRANSITIONING TO
OFFICE 365 SERVICES
EDITORS
NOTE
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
OFFICE 365
TRANSITION
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
STARTING POINT
OFFICE 365
TRANSITION
MIGRATION PLANNING
OFFICE 365
TRANSITION
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
If your organization uses many public folders, then you need to understand whether you
can migrate to another platform, such as SharePoint. Another option may be to move the
functions to shared mailboxes. Public folder
co-existence is available but ideally avoided.
Third-party systems are often the Achilles
heel of mail migrations because they may need
upgrades either before or after a migration.
These include unified messaging integration
with an IP-PBX, anti-spam systems, journaling and archive systems, fax software, signature
software or client-side add-ins.
Client versions are equally important. As
of early 2015, a fully patched Office 2007
client was the practical bare minimum for connection to Office 365. A fully patched copy
of Office 2010 works well, and Office 2013 or
higher provides the best experience and all
new features.
You will also need to understand the mobile
estate thats in use within the organization,
including ActiveSync clients and mobile device
management products. Mobile devices will
often need reconfigurationand possibly
replacementat the time of migration.
A hybrid migration
A third-party migration
OFFICE 365
TRANSITION
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
A staged migrationanother
migration, but copies data with Outlook Anywhere. A staged migration is a one-shot migration per user. After each batch, single users are
visited and the client is reconfigured.
IMAP migrations are great for open source
mail servers, such as UW-IMAPD, Dovecot and
other similar systems that provide a rudimentary experience. Like staged migrations, a batch
is created and mail is copied in a single run.
When a third-party tool is not available, IMAP
can be used to migrate mail from other thirdparty systems that support the technology,
such as Lotus Notes.
If youre using a third-party archiving or
journal system like Symantec Enterprise Vault,
then a third-party archive migration tool is
often required. Archive migration tools from
companies including BitTitan, Transvault,
SimplyMigrate, Archive360 and QuadroTech
take some of the pain out of extracting data
from the source archive and loading it into
Office 365. In addition, these tools often clean
up the short cut stub data to ensure that the
mailbox is clean and functional for the user.
Steve Goodman
MUST-KNOW
APPS
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
With an increasing number of available apps for Office 365, it can be difficult for
organizations to determine which ones should
be deployed and used in conjunction with the
software. The answer varies, but Exchange
administrators must know which apps are
used and how they work with their organizations systems. If your organization uses
cloud services such as Office 365 or Azure
Rights Management, take the time to research
the apps that are likely to be of value in your
organization.
Email and Microsoft Office are likely the first
two applications that come to mind. Most end
users cant operate without email, so a mail app
that connects to an Exchange Online mailbox is
something many consider essential. For Windows Phone users, Outlook Mobile is already
included and allows for Exchange ActiveSync
connectivity to Exchange Online. Microsoft
offers an Outlook Web App (OWA) for Office
MUST-KNOW
APPS
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
OFFICE 365
SERVICES
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
OFFICE 365
SERVICES
IMPLEMENTATION STEPS
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
10
For organizations that require true single signon or integration with on-premises multifactor authentication systems, Active Directory
Federation Services (ADFS), a component of
Windows 2012 R2, is used in conjunction with
Windows 2012 Web Application Proxy in the
DMZ. ADFS can then be federated with Office
365, meaning all password requests are redirected to on-premises ADFS servers.
When migrating email, the implementation steps depend on the specific migration
approach.
A hybrid environment will need either an
Exchange 2010 Client Access and Hub Transport server or Exchange 2013 Client Access
and Mailbox serverif neither are currently
installed in an Internet-facing site. This
does mean that enabling hybrid for Exchange
2010/2013 is simple, but enabling hybrid
for older organizations is similar to the first
steps of an Exchange migration. Assuming
OFFICE 365
SERVICES
ENABLING SERVICES
HOME
EDITORS NOTE
MIGRATING TO OFFICE 365
MUST-KNOW APPS
FOR OFFICE 365
AND EXCHANGE
REMEDIATION AND
TRANSITIONING
TO OFFICE 365 SERVICES
11
After configuration of base services and associated basic testing has been performed, other
required services should be enabled. Office 365
Multi-Factor Authentication is provided with
SKUs such as E3 and ensures that a physical
device and password are required. Office 365
Mobile Device Management, which is based
on Microsoft InTune, is also worthy of consideration. Office 365 MDM can monitor email
profiles and Office 365 applications on mobile
devices.
The actual transition, after thorough testing,
should be straightforward. After basic testing, a technical pilot with users typically from
the IT and Office 365 project team should be
conducted. Obvious issues need to be identified and corrected at this stage. In conjunction
with wider communications planning, the pilot
ABOUT
THE
AUTHORS
HOME
EDITORS NOTE
NEIL HOBSON is
STAY CONNECTED!
Follow @ExchangeTT today.
12