Microsoft Exchange Reviews

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 use the solution mainly for emails and arranging schedules, calendars, et cetera.

It is enterprise-friendly, and many organizations use it.

The product can scale.

It’s stable and reliable.

The solution could be more user-friendly. It could always be more scalable and have a better UI.

I’ve used the solution for many, many years.

The solution is stable and reliable. There are no bugs or glitches, and it doesn’t crash or freeze.

It is a scalable product. You can expand it.

I can’t say how many people in our organization use it.

We have our own internal support if we run into technical issues. I’ve never dealt with their technical support services.

We did not use a different solution previously.

I wasn’t a part of the installation. I can’t speak to how it goes.

Our IT handles the licensing process. I don’t have visibility into pricing.

We use an enterprise version.

I’d recommend the solution eight out of ten.

So I'm part of the team that does migration from the old version to the new version. I've done updates on all the versions up to 18.

On-premises Microsoft Exchange is good because it protects data privacy. It depends on the client because clients want to share their mailing communication with anyone, like vendors and all. So it's purchasing like on-premises server exchange email. So if they are okay with storing data to Online Exchange and all Office 365, they're buying that one. So it depends on the client's needs entirely. 

Microsoft could improve on Exchange's hybrid deployment or HCW. They need to improve on that because I was having many issues with HCW in our environment at times. And there are certain things I'm not clear about, like eDiscovery on our on-premises level. There were some features that I liked, such as Unified Messaging and Advance Search, but Microsoft removed them in 2019.

I've been working with Microsoft Exchange off and on for several years. It's not something I use daily. I work with it when I'm brought in to provide migration or implementation services. 

Microsoft Exchange's stability all depends on the environment. So when we are configuring and implementing, we're optimizing everything for performance. I've been working for 10 years in that field, so if anyone changes a configuration, we take into consideration the impact it will have on the stability. 

Microsoft Exchange is scalable, but it depends on the company and how much they're willing to pay. Scalability is only limited by the price.

When I'm migrating or implementing, and I have an issue, I check out a few things, like which applications are running. I also check the network security to discover all the basic stuff like server performance. Then, I suggest how many people are required to address these technical issues and at what level. I escalated to Microsoft two or three times. That was what the client needed, so we contacted Microsoft and got an LSA for that.

Installing and configuring Microsoft Exchange is a little bit complex. Initial installation takes around 45 minutes to 30 minutes. Then we have to do some configuration. The basic configuration takes one to two days, depending on the environment. When we are implementing in a hybrid environment, we need to make some manual adjustments. For example, there was an issue with creating multiple databases during one implementation, like active and passive copy. That was not transferring and working in that scenario. 

Often we're working with a company that has already deployed. That's where we need to understand our workflow and main flow. For example, say there is a company that already deployed version 10, and we need to upgrade to 16 or 19. So we would have to understand their needs, like if there is a hybrid configuration or some other existing requirement. 

There are different pricing tiers, and I don't remember all the costs for that. For Office 365, it depends on the license price per mailbox user. And for the on-premises version, there is a scale license. Overall, it's about average for the market. The on-premises license is a bit more costly because there is a requirement for OS-level licensing. And we offer a standard edition, so it is a little more straightforward to figure out the cost. We can also go for enterprise pricing. It depends on what the client needs.

I rate Microsoft Exchange eight out of 10. 

It is to run our mail server.

It's really just been the same for a decade now. I don't think they've really updated anything in a long time.

I like that we can still use it on-premise. Then, we don't have to pay the extra subscription fees for the cloud.

It integrates with anything really, to be honest, besides other Microsoft products.

There are AI-based features, but we don't use it.

We don't use Exchange for a lot of stuff, so there's not a lot to improve.

The interface could look a little more nicer, but other than that, it's fine. 

I have been using it for more than ten years. 

I haven't had to scale it at all. We've been running about the same amount of people for a long time.

It is used by around 100 end users. Just one person is required to maintain it for a hundred users, so we outsource that to an MSP.

They're helpful and easy to deal with.

We bought it years ago.  

I would recommend Microsoft Exchange to others because it's pretty easy to manage. However, it is costly, so it depends on how much you want to pay.

Overall, I would rate it a nine out of ten.

Exchange is an email solution. 

Exchange's best feature is single sign-on access using the Microsoft Identity framework. 

The security features could be improved. There should be a better policy management system. 

I have used Exchange for the last 12 years.

Exchange is 100% stable.

Exchange is 100% scalable. More than 100 of my customers use Microsoft Exchange, and some of the larger ones have more than 10,000 users.

We are a service provider, so we provide the first and second tiers of support. If we cannot solve the issue, we escalate to Microsoft premier support. My clients are happy with the Microsoft team. 

When I started using Microsoft Exchange, I found it to be complex. It's much easier now that I understand the architecture. Microsoft Exchange can be deployed on-premises, but it is also excellent as a cloud solution. 

The deployment time depends on the customer. A greenfield deployment typically takes around two weeks. It might take one or two months if you need to migrate accounts and data. 

I rate Microsoft Exchange 10 out of 10. I always recommended customers go with the Microsoft email solution, either on-premises Exchange or Microsoft Office 365. You can also go for the hybrid. I suggest Microsoft 365 or Microsoft Exchange for their collaboration and communication solutions.

Speaker 2:

We primarily use the solution for emails and calendars and things like that.

It is a stable solution.

The solution is scalable.

For me, the solution is very user-friendly. I've used it a long time and I know where everything is. 

For me it's sufficient. I don't see much that can be improved.

I'm not sure if the security is enough. That said, for my purposes, it's fine. However, I am aware there are always new vulnerabilities and security threats to worry about.

For new users, it might take them some time to get used to the product.

I've used the solution for as long as I've worked with the company I'm at now. It's been a few years at this point. 

We have found the solution to be stable. There are no bugs or glitches. The performance is good. We don't worry about it crashing or freezing. 

The solution has been scalable so far. We have no problems expanding it.

In our company, we have several thousand people that use the solution.

I have never called technical support myself. Therefore, I cannot speak to how helpful or responsive they are. We have our own internal team that handles everything.

I was not personally involved in the installation process. I cannot speak to how easy or difficult the setup would have been.

I'm not sure how many support personnel we require for deployment and maintenance. 

I don't handle the licensing aspect of the solution. I cannot speak to any costs involved. 

I'm just a partner so not like I'm an administrator of IT.

It's my understanding that the solution we work with is a company installation and is not on the cloud, however, I'm not 100% sure.

I'm not sure which version of the solution we're on. I don't know the version number off-hand. 

I'd rate the solution at a nine out of ten overall. we've been very pleased with its capabilities. 

I would recommend the solution to other users and companies. 

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.