Microsoft Exchange Reviews

I use this solution for my email and calendar. 

Because of this solution we have better integration with other Microsoft Office solutions. 

It's user-friendly. 

The solution needs a lot of resources to run efficiently. It would be nice if it used less resources to run on-premise.

I have been working with this solution for about five years. 

We have not had any problems with the stability of the solution. I would give it a nine out of ten. 

The solution is scalable. There are about 70 users working with it on a daily basis in our organization. 

Previously, we used Scalix. We switched to Microsoft Exchange for easier integration and better stability. 

It was a little bit complex to set up, so we had to get external help. 

A third-party did the deployment, and it took about two days. 

This is a time-saving solution. 

This solution is expensive. On a scale of one to ten, where one is the worst and ten is the best, I would rate it a four. 

Overall, I rate this solution as a seven out of ten. 

Exchange is an email solution. It is widely used in our organization.

Exchange is a robust system that is well suited for an enterprise environment. It's always up, and we hardly face any technical issues. Exchange has a web interface and integrates perfectly with Microsoft Outlook. This web interface can be easily used to change the passwords from the domain controllers. 

Microsoft needs to make some modifications to meet the current needs of the environment. For example, they need to add more cell service features because people work from home during the pandemic, and certain elements should be available as a mobile service.

I've been using Exchange for many years now. 

Microsoft Exchange is highly stable.

You can scale it horizontally by adding several servers behind the load balancer if you want. We have more than 20,000 users.

We contacted Microsoft about an issue a while back, but it was so long ago, I can't remember what the problem was.

Installing Microsoft Exchange is straightforward. The conversion takes time, but the installation itself takes less than two hours. The total deployment time depends on what you want to do, i.e., how many servers you want to configure, the structure of your domain controllers, etc. We have four team members for deployment and maintenance. 

We have an enterprise agreement with a five-year contract.

I rate Microsoft Exchange eight out of 10. Exchange has a cloud solution also, so depending on the count of users, you can decide whether to use the on-premise or cloud version.

We use Microsoft Exchange mostly for corporate communication services—setting up an email box, calendar, setting appointments, etc. My organization is a very big organization. The user base is not less than 15 people. When I worked with Exchange at Starcomms on the corporate organization, we had more than 1,000. When I was at another company, we had a user base that is more than 60.

Exchange 2003 was a more closed environment, but they improved on it in 2010. The availability group settings are better, so it has inherent scalability. In 2010, they added several sensible rules.

They could continue to improve the consolidation and integration of mailbox services to make them more flexible, easier to deploy, and more manageable.

I've used it for a couple of years. I've used Exchange 2003, 2007, 2012, and 2015.

It's scalable.

When we've had issues that are beyond our ability to resolve, we've contacted Microsoft. Once we had a deep phishing outbreak that involved a lot of phishing emails, so I had to contact them and then work together to figure out how to stem that thing.

Setup is straightforward for administrators if you understand networking services and the need for an active directory service. Exchange is a site-aware service, so you must have a good grip on active directory services. You need a deeper understanding of the networking layer, internet services, and broadband before you can manage it on your own as a system administrator. These are services that an experienced administrator can handle.

I was able to do it all on my own. I have robust experience in hardware, installation and maintenance, operating systems, networking, routing and switching, security as well as database administration, and a little bit of user support too. I can also support the exchanges from the client side of it. 

In terms of deployment and maintenance, I do need a support engineer just to help with the labor. I also need maybe other system engineers as a backup. Then there's the technical team. Okay. In a corporate environment, you have people to deal with management influence, IT governance, and all the business cases underneath all that. Then you have the administrative level, including the security admin, a Windows admin for the Java site, then you have the Exchange admin. On the support level, you have user support.

When I was working in another company, it was Enterprise volume licensing.

Microsoft Exchange is the leader in corporate communication. It has been quite a good service. I rate it nine out of 10.

The most valuable feature of Microsoft Exchange is its ease of use.

It is important to have the updated version for scalability.

I have been using Microsoft Exchange for approximately four years.

The solution is stable.

The scalability of Microsoft Exchange is good.

There is not a lot of support needed from the vendor. We can provide the training for the customers.

The solution can be complex depending on the environment. Additionally, it depends on the other solutions or authentication needed.

The time it takes to deploy Microsoft Exchange depends on the customer's environment. However, with a consultant, it can be done in a reasonable timeframe.

The steps that are taken for the implementations depend if we have to do any duplication or if it is a new installation. If it is a new installation it is easy.

A minimum of three technical staff is needed for the implementation of Microsoft Exchange.

There are different prices depending on the customer's use cases and amount of users. The price of the solution could improve.

I rate Microsoft Exchange a ten out of ten.

I am using Microsoft Exchange for emails. For example, here's my email address, call me, or email me and I'll email you. I don't use it for any marketing emails.

I find the desktop version of Microsoft Exchange looks better than the online version. You can make it a white background. You might be able to make the online background white, but I have no idea how to do that. I know how to do it only on the desktop version

The desktop version of Microsoft Exchange receives emails a little slower than the online version. 

I have used Microsoft Exchange within the last 12 months.

The stability of the solution is good.

I haven't run into any scalability problems. However, I've run into several large multinational companies that I know do run into issues, and they have to merge two separate something together.

Microsoft support is very good. I did recently have an issue the other day.  The solution was asking me for my password, and I put it in and it didn't recognize it, and I was getting really frustrated. I called Microsoft support, spoke to a person, they had me download a tool,- for data checking, and it fixed it. Whatever it did, it fixed the problem. I had a good experience. 

They are responsive and helpful, if you're only one user and not their biggest customer, they still give you good support.

I have implemented the solution for my system and it is easy. I have not done so for a company. I just download it and run it, that is all.

I have Outlook 365 Professional, and Exchange comes in the bundle with other solutions, such as Word and OneDrive. I pay for the use of the bundle monthly and I can imagine if you are a company with many licenses the pricing model would be a lot different.

I do not see Microsoft having any competition in the market. They appear to be dominating.

I rate Microsoft Exchange a ten out of ten.

Our entire organization uses Microsoft Exchange. We are using Microsoft Exchange 2016. The solution is deployed on-premises.

This solution has improved the collaboration between our organization and our partners and contractors.

The most valuable features are that you can exchange information, tasks, attachments, and enhance the process in a short amount of time.

The security for the email technology could be improved.

For the next release, there are some features on the cloud-based Exchange that aren't included on-prem. It would be great if these features were made available in the next release. For instance, integration between Exchange and its on-prem calendar is not available for the on-prem solution.

I have been using this solution for more than 15 years.

I think Exchange is one of the most stable products from Microsoft.

The product is scalable.

Technical support is good. We're covered with the technical support maintenance agreement with Microsoft.

Most of the process is straightforward.

We used a consultant for deployment. We are working directly with Microsoft partnerships.

We renew the product license with Microsoft every three years.  The cost is included within a bundle of services. It's an enterprise agreement with Microsoft.

I would rate this solution 10 out of 10. It has enhanced the process of exchanging information between our organization and others.

I recommend this solution for others to use the auto implement. It's a good product. You can use this product through cloud, and it will be more valuable than on-prem deployment.

I mainly use Exchange for exchanging emails.

The best features are that Exchange is very customer-friendly, its interface is self-explanatory, it doesn't hang, and it keeps evolving.

An improvement would be to combine Exchange and Teams so that emails, calls, and chats can be integrated into one window.

I've been using this solution for a few years.

Exchange is stable.

I would recommend Exchange to those considering using it, and I'd rate it nine out of ten.

Exchange's interface is good. All of our engineers like it and are accustomed to using it.

The main problem with Microsoft products is that we're constantly required to install patches and fixes. In fact, Microsoft frequently publishes, which is in itself a guarantee of quality, security updates especially for the OS that we are forced to apply. The problem is, this causes us to do a lot of testing before we go into production to make sure that our systems continue to function properly.

I've worked as an administrator of Microsoft Exchange for five years.

We haven't identified any serious problems with Exchange.

We have always used Exchange. That's a strategic choice for our company. We are confident in Microsoft because their support is always there for us.

The setup was easy. When we first deployed Exchange, we had some guidance from Microsoft, but now our engineers use it effortlessly. 

I rate Microsoft Exchange eight out of 10. I hope Microsoft will continue to support the on-premises versions of their products because they are increasingly orienting themselves toward Exchange in the cloud. Unfortunately, cloud services are unavailable here in Nigeria.