Microsoft Exchange Reviews

At the moment, our primary use case is mostly for mailing, but in the near future we will be more focused on collaboration, as well.

There is nothing special that I like with Exchange. They made a system that works in business. It is quite normal that companies use Exchange.

In terms of what should be improved, they should probably move to a cloud option like Office 365. We would like to get this functionality without the need to deploy complex hardware and software solutions. This should be the next thing, making Exchange more related to Office products, which are more cloud-oriented, less on-premise or desktop-oriented solutions, like the direction Google is strongly moving towards.

I have been using Microsoft Exchange for about five years.

In terms of stability, if you are a user or if you have a number of users, especially a big number of users, there will occasionally be some bugs in the product. That is a normal situation.

In terms of current users, I think we have about 3,000 or 4,000.

They are not dedicated solely to the Exchange. They are also supporting other software technology solutions.

My experience with tech support is that they are mostly good enough.

The initial setup is quite a straightforward process. I don't think it is a very complicated solution. Plenty of things could be more complex, but the ordinary, general settings are quite simple.

My personal preference would be a Google solution. It is not a big difference. My advice to anyone considering Microsoft Exchange would be, stay with your product because switching to another product can be costly and a complicated task.

On a scale from 1 to 10, I would rate Microsoft Exchange a 6.

It may be that some nice features are missing.

We mostly used Exchange for sending emails and for document management. We also used Exchange to get information from a user's profile but we didn't use Exchange for filing.

Personally, I'd say Outlook is a good feature. We used it for scheduling appointments, for storage and archiving, so we could easily find old mail and documents, even ECF documents. A lot of people like using Outlook as a personal archive. 

When we started using Exchange on the cloud, we had a lot of initial problems relating to our main database and we also experienced issues with the accidental deletion of inboxes, amongst other things. In fact, many of the files we had moved to the cloud had disappeared. There also seems to be a problem with the retention of information. For example, if you delete something, you may have a problem restoring the entirety of the inbox, so if somebody leaves and you want to backup your data, you need to download it to your local servers. This is a big area for improvement. 

Currently, we are using Office 365, but we used Exchange for more than 20 years.

As I mentioned earlier, we have a very big database which can lead to some problems. Due to the algorithm, we tend to experience a lot of issues restoring and fixing problems. For example, we would have to retrieve all of the mail from our database and load it into a new database. We only had that problem in the beginning because of the algorithm, not because of Exchange. Now, we manage to serve almost 99% of the information. 

We get our support through a third party. We have an Enterprise Agreement with Microsft but we don't receive customer service directly from them. Our third party company receives support from Microsoft, and when we have a problem, we deal with them; however, I've only used them once or twice. Other than that, my own systems engineer solves our problems.

 As we had more than 40 users, we had four or five people who handled maintenance.

The initial setup was complex. When we set up Exchange on one server, it was very simple. Keep in mind, you need to be an expert to install the Exchange server because of all of the connections, the TLS-ing, connecting to the internet and ISP; it just wasn't simple at all. 

Microsoft may tell you that deployment is as easy as " a click of the mouse", but this is not the case. 

If done at the same time, deployment takes roughly five hours. After that, if we are migrating from an older version of Exchange to a newer version, it takes a very long time. In other words, migration takes much, much longer than the initial installation, which takes roughly four to five hours. When it's working, it's very stable; however, this was not the case 15 years ago, but in the last 10 years, it's been okay. When we experience a problem, it is strictly due to the algorithm. 

It depends on what the user's needs are. A lot of people can now use Gmail or they can use Exchange on Office 365 with a license, there are a lot more options available nowadays. If you're thinking about installing Exchange on-premise, on behalf of a client, a lot of people have now moved to the cloud, to Azure or something similar. If a client asked me to purchase a 365 license, including the Exchange server, I might decline. If they want to hold meetings or something similar, I'd suggest that they use a professional service like Gmail for businesses. It's a much cheaper option because a lot of people that work with Microsoft office end up buying one or two 365 licenses which include Exchange, so they use it. 

Because I have a lot of experience using Exchange, I would rate it between eight and nine out of ten. It's not a perfect ten, but for our purposes, it was perfect.  

I use the product to send emails and communicate with users and clients.

Communication is the most valuable feature of the solution. It's a good solution. We can use it without any problem. It's useful for every company, whether small or large.

The support needs to be more knowledgeable. The support's answers are sometimes wrong, and they do not solve our problems. We have to find a workaround when we do not receive the solution.

I have been using the solution for three years.

The solution’s stability is fine. We face some bugs sometimes. I rate the stability a nine out of ten.

The scalability is fine. In our organization, 1000 employees use the solution.

We need two technical people, two managers, and seven first-level support employees to deploy the solution.

We pay a yearly license fee for the solution. The product is quite cheap.

Overall, I rate the solution a ten on ten.

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 use Microsoft Exchange for professional emails, and the collaboration tools, such as Teams, and SharePoint.  

The most valuable feature of Microsoft Exchange is the collaboration tools.

Microsoft Exchange could improve security. They can elevate a lot of security features.

I have been using Microsoft Exchange for approximately 10 years.

Microsoft Exchange is stable.

I have not used the support.

I would recommend this solution to others.

I rate Microsoft Exchange an eight out of ten.

I primarily use Microsoft Exchange as a messaging platform.

Microsoft Exchange's most valuable feature is that it's old-fashioned communication, meaning it's good for people who aren't able to work comfortably in a cloud environment.

I've been using Microsoft Exchange since 1996.

Microsoft Exchange is very stable - I'm very satisfied with its availability and reliability.

Microsoft Exchange's scalability is very good, with load balancing and failover switching features.

We use Microsoft Premier Support and are very satisfied with it. However, sometimes we don't get support quickly enough - for example, if there's some global hacker attack, we don't get served as quickly. The skills of the technical staff can also vary, and Microsoft could perhaps improve their training.

The initial setup is really straightforward so long as you meet all the prerequisites. However, in some scenarios, you only have selected privileges and limited control over parts of the installation, which means you may have to ask Microsoft for help if something goes wrong. 

Microsoft's licensing structure is too complex, but its prices are affordable, though not cheap.

I would rate Microsoft Exchange as ten out of ten.

I use it for email, contacts, and calendar.

The latest versions have gotten much better about balancing the load on the backend.

Currently, its administration is too cumbersome. It's unwieldy. It's slow. It consumes too many resources. Configuration needs to be much more streamlined and administratively automated.

In terms of additional features, on the administration side, I would like them to incorporate a security console to focus on all of the security aspects in one place.

It has been in use for 10 to 15 years.

I would rate it a six out of ten. It's very cumbersome. It's not lean by any means.

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.