Microsoft Exchange Reviews

It is an email solution with all the capabilities similar to different email solutions. We basically use it for internal emails and for making reservations. We have some shared mailboxes to receive communication from general entities.

It has a feature that allows you to retain an email and recover it as an administrator. When you activate this feature, even if a user deletes an email, the email is still in the system, and we can retrieve it as an administrator. It is a very useful function. We turn this feature on for some of the mailboxes because we need to keep all the records.

I like the way emails are classified in this solution. It makes it really easy to take a look at the most important messages. This is a really good functionality. Some of the emails directly exchanged with you are marked as important and shown in one tab, and everything else is in another tab.

We usually don't have any issue with Exchange. It can be integrated with different solutions. 

Its search functionality can be better. It is currently not really easy. It has the capability to search your mailbox, but it has some restrictions in terms of the number of results that you can retrieve. You can only get around 250 results. If you want to do a deeper search, you need to use different functionalities of the product. The policy that we have for handling emails is that we do not delete emails at all. If I insert the text that I am searching for in the Search field, it only retrieves a limited number of emails. To search for an email from 2010, I need to use different search functions to find what I am looking for.

Microsoft can also improve its licensing for its products. Microsoft's licensing is not very easy to understand. It can sometimes be really complex to understand what you need to have in order to comply with Microsoft licensing.

I have been using Microsoft Exchange since I joined this company back in 2008.

Microsoft Exchange has been pretty stable. The problem we faced was because we forgot to delete some of the rules that were created automatically. The problem was on our side. 

We also have Exchange Online, and we have experienced an issue with it in the past. Microsoft had a huge outage about three or four months ago, and we didn't have any access to our email in the cloud. That's the only time we experienced a problem with Exchange Online.

We are a mid-size company with 350 employees. We haven't experienced any problems with scalability or faced a situation where we need to quickly increase the capacity of the system. The company has grown over the last ten years and has added around 100 employees. It has worked for us in terms of scalability, but I don't know if it works for companies bigger than ours.

We have all kinds of users. There is a mix of different functions that are using the system. Our core business is for operating power plants, so our employees are plant operators. Half of our users are plant operators, and we also have a mix of engineers, accountants, commercial staff, legal department, and HR department. 

We have not contacted their technical support. We found all the documentation on the Microsoft site very useful. 

I was not the one who implemented this solution. Based on my understanding from the technical department, installing it in an on-premises environment is easy. Creating or handling all the emails on the cloud is also really easy. The most complex process that we have done so far is migration. We have a hybrid environment with half of them on-premises and half of them on the essential line. Integrating these two environments was the most difficult task. You need to understand both environments to integrate them. We didn't have a lot of problems with this integration. It is a difficult task, but it is not impossible.

Its price is very affordable, and basically, it is the standard of the industry. We have the Exchange 365 subscription, which includes the usage of Exchange Online. I don't know the specific cost, but it is the retail price of Microsoft 365 E3 licenses.

Microsoft's licensing is not very easy to understand. Microsoft changes rules every other day, which makes it difficult for us to understand the licensing not only for Exchange but also for other products. It can sometimes be really complex to understand what you need to have in order to comply with Microsoft licensing.

Its technical implementation is quite good. It is stable and can be accessed through all kinds of devices. You can access it through a client for your mobile phones or computer. It performs pretty well. Microsoft is a market leader with a presence everywhere, which makes it easy to find support.

I would recommend this solution. I would advise others to also go for the entire suite of Office 365 along with Microsoft Exchange. I don't know if Exchange licenses are sold separately. If you are already using Microsoft tools, it makes sense to go for Microsoft Exchange because it has native integration with all those tools.

I would rate Microsoft Exchange a nine out of ten.

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 just use it to retrieve my data. I'm just mostly leveraging it to retrieve some archive data, so I haven't really used it on a more advanced level.

For example, I was changing my email, so I wanted to retrieve some data I had from the previous address. That was the only time I used Microsoft Exchange to retrieve my archive information. Aside from that, I don't think I've used it for any other use cases.

I haven't really used it for something advanced. Most of my use cases are just to retrieve my information. Microsoft Exchange is just a part of your Office package, so you just have it inbuilt. I really haven't used it much.

The initial setup is easy.

I've not really gone through the application. The only time I use it is when I want to retrieve particular emails that I had.

I really have issues with updates. When an update wants to come, it should just come maybe once or twice rather than having us deal with constant updating. If I have a company constantly updating me on additional features and everything, I get to the point that I just don't read the emails or classify them as junk. However, if I get an update maybe twice, I pay more attention. They need less frequent updates and reminders. 

I've been using the solution for a year now. 

I can't speak to the stability as I haven't used it too much. 

I haven't tested the scalability. Most of my applications that I just use for my own work. 

While it's used in the company, I just use it for my own personal purposes, such as retrieving email. 

I've never reached out to support. 

When I was using Exchange, I didn't know how to initially use it when I wanted to use it to get to my data. To find out, I checked YouTube, and I got an idea of how to use it. It wasn't a problem for me.

I have not used any other similar solution previously. 

It's straightforward to set up. If you have your Office package, everything is straightforward.

I did not need the assistance of a consultant or integrator during setup.

This is a company product. I'm not in charge of licensing. I'm not sure what it would cost. 

I'm not sure if I could recommend the solution as I haven't taken a deep dive into its functionality. I haven't done any advanced work with it. I've only ever retrieved my own data. 

I'd rate it five out of ten. I was able to achieve what I needed to, however, I haven't used it much. 

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.

I'm the CDO and we are resellers of Microsoft Exchange. 

I like the logistics and Microsoft protocol of reaching Outlook anywhere. It's a user-friendly product.

Load balancing is lacking. If you need to use it, it requires preparation of the Windows IIS services for load balancing. 

I've been working with this solution for close to five years. 

The solution is stable. 

You can add multiple lots and expand the solution so it is very scalable.

It depends on the customer's architecture but in general, the setup is quite straightforward. 

There are multiple competitors in the market and I think the price is a little bit high but it has many benefits. 

We've just stopped providing advice for on-premise products because customers are moving to cloud-based products which saves a lot of preparation time. 

That said, I rate this solution nine out of 10.