4 out of 5.0, Reviewed Oct 17, 2016
Overall great experience during implementing this. However had an internal Exchange expert to help with the migration from on prem to cloud
understand the limitations and or archiving options to make sure it fits your goals as a company.
Uptime and scalability
Seems to failover to other servers in the cloud and cause problems randomly and at times without notice.
We utilized MS resources through our EA when applicable, however, having more documentation on pitfalls when implementing would be helpful.
More training internal
overall MS is timely in responses, however, we have an EA in place with support.
3 out of 5.0, Reviewed Sep 23, 2016
It was a quick and dirty implementation due to resource shortage. Did not take some user requirement into consideration and thus had many problems when first deployed.
Need to take time to analyze and requirement
Standard product that many companies use
Not very user-friendly
Need to work more with SME from the vendor
Need to take end user requirement into consideration.
The support is ok
4 out of 5.0, Reviewed Aug 17, 2016
The migration required a considerable amount of upfront analysis and testing to determine the most appropriate forward approach with UPN/Login, how to handle distribution groups and shared mailboxes, as many of these elements were linked to business processes. But the migration was successful, albeit slower than anticipated. Now the challenge is to decommision the on-premise instance with out negative impact to business process or IT operations
Modernize your AD structure first, if you want to more quickly migrate to O365 Exchange. Examine the gaps between the on-premise and the cloud offering to determine if these pose challenges to the organization.
Differences between the on-premise features and the cloud features.
Stayed engaged to the end, and offered more experience.
Find a partner that had experience with legacy AD infrastructure and BPM integrations.
4 out of 5.0, Reviewed Jul 21, 2016
The biggest challenge has been the learning curve with the new solution.
Plan, plan, plan.
It gets the job done for less cost.
Not as well polished as other products.
Point to more online resources to find solutions.
Dedicate more staff to the implementation.
It works, but there are third party solutions that are easier to use.
Depends on how much you want to spend.
It takes much longer than it should
4 out of 5.0, Reviewed Jul 21, 2016
Works fairly well now but had to overcome hurdles.
If migrating from 2010 - know your PowerShell.
Most people understand how to use it
Price, upgrading headaches.
Document procedure for upgrading better.
Move everything to 2016.
Not that great of support unless you really pay for it.
for such a big company and developed product, they dont make it easy to upgrade
5 out of 5.0, Reviewed Jul 14, 2016
Didn't experience too many issues and had money left over in the migration budget.
Setup a test environment and test all of your applications for compatibility.
High Availability and fail-over capabilities.
Provide more in-depth training.
Eliminate and stop the creation of all PST files.
5 out of 5.0, Reviewed May 12, 2016
Since implementing, we have found this version to be very stable and capable. Very satisfied.
Communicate well with your users as to why this upgrade is necessary, and what the benefit will be to them.
Allocate larger mailbox size quota per user.
Premiere support costs too much. Not using Premiere increases response time by Microsoft to unacceptable levels.
3 out of 5.0, Reviewed May 11, 2016
Numerous quirks and problems running in the hybrid mode that Microsoft was unprepared and unable to deal with. Required bringing in 3rd party vendor.
Talk to more existing customers, migration is somewhat painful.
Scalability, reliability, predictable costs.
Microsoft support surprised by quirkiness, unprepared to support hybrid migration.
Be more prepared, have more answers.
Add 3rd party vendor from beginning.
Microsoft unprepared to address quirky hybrid multi-domain problems.
Micosoft unprepared for quirky problems found in hybrid setup.
4 out of 5.0, Reviewed Apr 27, 2016
An out-of-control Groupwise installation posed many issues when migrating to Exchange and instilling some policy. 3rd party tools were helpful but there were many victories. The application behaved as advertised but the path was rocky.
Review success of 3rd party tools to be sure they relate to your case.
Redundancy of databases and managability.
More native migration options.
Instill usage policies before migrations to manage the tasks and prepare the users.
Multiple forest situation resulted in some lost functionality.
Premier Microsoft support performed as expected.
3rd party contractor had lapses in expertise and communication.
4 out of 5.0, Reviewed Apr 12, 2016
Had a very good resource to engage with us and guide us.
Do your homework and leverage the right partner.
Architecture and covering DR.
Can't think of anything.
A huge success.