Microsoft Exchange Reviews

We use the solution for all communication exchanged with our team, customers, and all other internet exchanges. Additionally, it was used as a formal way of communication.

The backup and archiving features are valuable, it is user friendly too.

They could improve on the search function, it takes too much time.

I have been using the solution for five years.

It is a reliable solution.

We have approximately 20,000 users using the solution.

The installation was straightforward and it was supported by the IT team.

I was satisfied with the usage of Microsoft Exchange, I would recommend the solution.

I rate Microsoft Exchange an eight out of ten.

We use it just for email. 

It is easy to set up.

It doesn't work very well on a virtual machine. We had to move it around. There are also issues when you try to move it between computers.

I have been using Microsoft Exchange for around ten years.

Its stability is not so great. We can't move mailboxes because of a corrupt file or random issues, which causes headaches.

We didn't have any need to scale it. We have got the same number of people in our company. We have 20 users at the moment. They are accountants and engineers at the job sites.

We don't really use them. We use a local IT company for any major issue.

We've had the same solution for a long time. 

The setup program is straightforward, but there are hiccups when you try to move it between computers. You come across different issues.

Its price is okay.

I would rate Microsoft Exchange a seven out of ten. 

Our primary use is for email and communication. We also implement this product for our customers.

In the version we have, I would like to see better communication between the end device and the Exchange server.

We have been using Microsoft Exchange for the last 15 years.

We use Exchange on a daily basis and most of the time, it is stable.

Exchange is very easy to scale and we have approximately 1,000 users.

If we have an issue where a support ticket is escalated to level three then we will contact the vendor. The technical support is good and we haven't had any issues.

I have not personally worked with other similar solutions.

The initial setup is very simple.

We are a partner and deploy this product on our own. There is four or five staff who are system administrators.

We provide level one and level two technical support for our customers.

With respect to pricing, this product is somewhere in the middle. Everything is included in the standard licensing fees.

This is a good product but our version is reaching end-of-life. I would recommend using the most recent version of Exchange.

I would rate this solution a nine out of ten.

It is very well integrated with other Microsoft programs, teams, and so on. They work well together. 

It's not always the finest solution in terms of integration with products that are not from Microsoft. It integrates very well with Microsoft products but not with third-party products. 

I have been using Microsoft Exchange for approximately five years.

It is stable. 

It is scalable. Around 100 users in our company are using it. 

I don't have any experience with technical support.

It was easy to set it up.

It's working very well. There is no problem, but the price is not the best.

It is a good product. Only the price and integration can be improved. 

I would rate Microsoft Exchange a nine out of ten.

I primarily use the solution for work email.

It's so much of a part of what I do every day that I don't give it a lot of thought. It just works, for the most part, until it doesn't, in which case I call tech support.

Exchange can be a little finicky, sometimes, or flakey. Last week, for example, I had gone into my calendar to check on some briefings that I had established, and then went back into my inbox, and suddenly the view had changed. I had no idea what it was that I had done, and I couldn't figure out how to get that view back. I took a productivity hit as a result of that, trying to fix it, due to the fact that it just wasn't what I wanted. It wasn't what I was used to working with. Two different tech support people had to work with me in order to get the view back to what I wanted just so I could be productive.

The fact that I messed around trying to get that view back, and could not figure it out for myself, and it took two different tech support people to help me get back to what I had before, is an area of improvement. I have no idea what it was that I did that caused the view to change. All I was doing is going from the calendar back to the inbox, and it was somehow different. It may have been a UI bug. I'm unsure.

The second tech person that was working with me to try to get the view back the way I wanted it, told me one time his cat walked across his keyboard and it totally screwed things up for him. He had no idea what had happened, and he had to go back and re-set up a lot of configurations. That tells me there must be something wrong in the design, if small things can happen to set it off like that.

I've probably been using the solution, on different jobs, for about 20 years at this point.

I believe the solution is quite stable.  I don't recall it crashing on me, for example. That would be a big, "Oh my God, what do I do?" situation due to the fact that I rely on it so heavily. It's a workhorse for me.

Just that fluke occurrence recently around the views changing, and how the information was presented in the inbox, that's maybe a stability issue as well as a UI issue.

Everybody in our company uses the solution, however, we're pretty small. There are only 20 of us. I'm not sure how it scales, as we wouldn't need it to.

I don't work with Microsoft Exchange for technical support. I worked with a company that does tech support for us. In terms of judging Microsoft's services, I wouldn't be able to give any feedback.

I don't recall the initial setup being complex. When I joined this company three years ago, the tech support folks set it all up and I don't remember it being particularly painful.

I have no idea what the licensing costs are on the solution.

I'm unsure as to which version of the solution I'm working with at this time.

I've been using Exchange forever as an end-user, however, I don't know much about the technical aspects of it. I just use it a lot. For me, it's always worked quite well, and because of that, I haven't' given anything about it much thought.

When it works, it's a beautiful thing. When it doesn't, you want to tear your hair out. Sometimes that's the price that we pay for the automation that we get.

I'd rate the solution overall eight out of ten.

This solution helps us collaborate with other members of the organization.

It helps us with basic needs such as email. It is also extremely helpful for us to collaborate with other Microsoft products such as: Office and Active Directory.

I think that improvements should be made in creating greater abilities for Microsoft Exchange in terms of Reasearch and Development.

It is a product that is simple to manage, and easy to use. 

The primary use case is sending and responding to email.

Our primary use is protection of email. Email is the primary mode of communication. With Exchange, the user can access it anywhere on mobile or laptop. It becomes easy for them to communicate with their vendors and consumers. So that is why we chose Exchange.

It is easy to use and we can allow many users because now our users are scattered  They over a wide area. We can use it from anywhere. That is the main benefit for us.

In terms of probability, every now and then there are changes coming and going. The changes are not that frequent because every month they got updates back, so that is an issue.

We always have a higher variability configuration ready and we've got two mailbox servers, so even if one goes down, we can use it, we can still access our mail. As far as variability in internet we've never had any major issues.

We have not had scalability concerns. We had already planned for scalability and everything, and when we started we were only ten user accounts but we got thousand users so we planned for a thousand users so we never had any issue. We still have room for expansion so it's not an issue for us.

We previously used Google gmail. But,we have a lot of expertise with Exchange. And the thing with Google, or any dormant solution, is that we are a semi-dormant algorithm and we can't have our data out on the cloud.

It was a straightforward implementation. We just had five or six servers off Exchange and never had any issues. It was a very straightforward thing for us, we just made sure that we found it well and we went by the phases and a small issues moving from the old version of Exchange to the new version of Exchange, but it was small DNA. No major issues along the way.

VNA redundancy has grown in the data, VNA data variability has grown, even in case VNA found the server goes down, and users can still access their email. So basically everything is good. The feature VNA almost as good as having your own Outlook, although it's better VNA.

It helps because it's easier for the employees to exchange emails. Instead of their using their personal emails, at least now they are using the company email.

One thing I like about it is the support. Microsoft is very good at providing support. I also like that it integrates well with calendar, scheduling, etc. It's easy for employees to make meetings and plan their agendas.

It requires a lot of maintenance. I think the cloud solution would be better and easier to manage as well.

Deployment should become a bit easier, the process is a bit complicated. You have to have done it one or two times before you get it right. The first time you do it, it won't be perfect. There are a lot of complications compared to Gmail For Business, which is a bit easier when it comes to configuration.

It is very stable. But at certain times you find that fixes and patches which they release can mess things up. But so far, I haven't come across any major issue.

The support is there with the number of people using it. It's very easy to get solutions when you're stuck. Somewhere, someone is going through the same problems. They're willing to help you with the solution.

At the time I joined the organization, they didn't have an email solution in-house. Employees were using their personal emails. Some of were using Yahoo!, some were using Gmail. If someone left the company, they would take with them the emails they had received from clients. We needed an in-house email solution like Exchange so that if someone leaves we are able to keep the emails.

To me, the most important criteria when selecting a vendor are maintenance and support. Features also matter. Then I look at the pricing. Is it too costly, is the organization going to be able to afford it? So cost plays a major role. When I go to the Director and say I want to buy this solution, the main thing he will look at is the pricing. He will ask, "Why are you getting these features, it's very expensive. Why aren't you going with this other option, it's cheaper?" But again, if the support is great and the pricing is a bit higher it's worth it.

The installation was simple and straightforward. We didn't have any hiccups. It went fine.

They are flexible when it comes to pricing, unlike most of the other vendors I have dealt with.

If you don't really mind the cost then go for Microsoft. You can never go wrong with them, their solutions are very good. They're stable. They're all tested, so when you start you know it has already been tested. There are many people using it, it's comfortable, it's stable. You won't have any hiccups. I would recommend it.

One thing I've been doing is, before I deploy it to a production environment, I always create a "lab" where I try it out and make sure everything is working properly.