We use it to share information and collaborate with each other, even when we're working remotely.
We exchange files and documents, and we also use it to store recordings and other information from meetings with our customers.
We use it to share information and collaborate with each other, even when we're working remotely.
We exchange files and documents, and we also use it to store recordings and other information from meetings with our customers.
There are some bad days or hard ways when it's tough to connect with people who don't have MS Teams products. But this is only a hard situation when we need to communicate with people outside MS Teams.
So the connectivity could be improved.
Another area of improvement is the sharing of files, the sharing part of Teams. How I can easily share information files or video files with the colleagues I'm working with? So, this is an area for valuable improvement.
Another area of improvement is support. It should be faster and more clear, and more human.
I have been using this solution for the last five years. We use the latest version.
I would rate the stability a seven out of ten. There are hard days.
It is very easy to scale. Just add on licensing and keep working the same way.
There are around eight end users in our company. It's suitable for our current level. We're a small company, so it's quite okay.
I don't have the best impression of customer service and support. It should be faster and more clear, and more human. The support team deep dives into thousands of documentation pages, making problem-solving time-consuming without human interaction.
Neutral
The initial setup is very straightforward. It just took a minute. It is very easy.
The deployment is a plug-and-play process. You simply need to access the administrator platform, set up the configurations easily, and share enrollment links with people. It's a very easy process.
The deployment was done in-house. However, you need an IT-oriented person, an IT manager with knowledge of Microsoft.
The license can be both monthly or yearly. It is not expensive.
It's a useful tool for remote work and communication. Start slow and educate yourself. Learn about the solution and give it a try.
Overall, I would rate the solution a nine out of ten.
We primarily use the solution for e-mail. That's pretty much what Exchange is built for, and it's very good at what it's built for.
If you want to have an email system that works quite well and that allows you to be able to give easy access to everything from emails to checking calendars, that's basically 365.
It is stable.
It can scale.
Technical support is largely helpful.
The only thing that could be improved is the pricing. They could make it more competitive. The price is a lot. That said, the product works, which means you're kind of caught between two realities. You want to pay for something that works. You just don't want to pay too much. If they could get it to be more affordable, then they will have a greater uptake in users. All the people that are using G Suite, the free version, would likely actually move over to 365.
I've been using the solution for over 15 years.
This is a very stable product. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable, and the performance is good.
I'm happy with the scalability.
We have about ten people using the solution in our company; however, our customers that we support number in the thousands.
If we do get additional people, we will increase usage.
I've used Microsoft tech support quite a bit across various applications that they have available. Technical support is not bad. Once or twice you get a unique issue that's going to be difficult until you find someone that knows absolutely everything. However, for the most part, technical support is okay. It could be far worse.
The setups vary in level of difficulty. I've worked with both simple and complex setups.
I'm not sure exactly how long it takes to deploy. The time would depend on the size of the implementation.
I can handle the initial setup myself.
The solution could be less expensive.
We can do monthly payments if we like; however, usually, we do a yearly subscription.
We've used on-premises and cloud deployments. In on-premises, we're likely one version behind. On the cloud, we are using the latest version.
I'd recommend the solution to others. Whenever, for example, I find someone using Google, I move them over to Exchange.
I would rate the product eight 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.
Microsoft Exchange is a user-friendly product that is easy to manage and configure.
Some users encounter stability issues. I connect with the support team through my local partner, which takes time.
I have been using the product for ten years.
I rate the product's stability a seven out of ten.
I rate Microsoft Exchange's scalability a nine out of ten. My company has around 4000 users.
The tool's deployment is simple.
I rate Microsoft Exchange's pricing a six out of ten.
I rate the tool a seven out of ten.
We use the solution in our company for emails, calendars, requests, and tasks.
The exchange of emails is its most valuable feature.
I'm a user for the time being. I'm not an administrator who is managing the server. I was an administrator fifteen years ago. But today, I'm just a simple user using the solution for emails.
We had an antivirus like Sophos to secure our network. In terms of Microsoft Exchange, I think maybe what can be done is to make it more user-friendly. Also, Microsoft should make it more like a web version.
I have been using Microsoft Exchange for a very long time. Currently, we are on the cloud version.
It is a very stable tool.
It is a very scalable tool. In my last company, the solution had more than five thousand users. Now, thirty users use the solution. Considering the upcoming year, there are no plans to increase its usage.
I am not seeking any help from technical support because we speak with our own technical staff.
As a user, we don't get involved in the setup process. We need to connect it using the email address. It takes a minute to deploy it. I can do the deployment by myself.
Since my company is on Microsoft Cloud, we pay for the licenses per user. Compared to volume licensing, I would say the present licensing cost is not expensive.
I recommend others planning to use the solution to use it. I rate the overall solution a ten out of ten.
We primarily use the solution for email and passing on information between the company's user base.
The exchange functionalities are good. It helps ensure information is accessible and can move between people in the company. The exchange of email is very easy.
The integration is very good.
The Microsoft visuals are very helpful.
We're able to work on SQL servers with no issues.
I can't say there are any missing features.
I'd like the archiving process to be faster.
They could offer better performance and enhancements throughout the product.
I've been using Microsoft for 15 years.
The solution is stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable. I'd rate the overall stability eight out of ten.
It is a scalable product. A company would have no issues if it needed to expand.
The solution is mainly used by all end-users. Everyone in the company has it. That's about 1,500 users.
I have never reached out to technical support.
I have never worked with other similar products.
Others work on the deployment and configuration process. I did not take part in the implementation process.
I have five colleagues that handle all aspects of Microsoft maintenance, including any needed maintenance for Exchange. One is an admin on Exchange. The others handle other Microsoft products.
I am using the latest version of the solution.
I'm an end-user. As an end-user, the solution works well to the point I don't really know it's there. My company is a Microsoft customer.
I'd rate the solution eight out of ten.
Microsoft Exchange is the main mail server of Microsoft. It's a popular mail server, so a common use case for Microsoft Exchange is for small, medium, and enterprise-scale businesses. It's a mail solution, voicemail solution, live calendar solution, etc.
What I love about Microsoft Exchange is the good integration since 2013, particularly its integration with the calendar and other software such as Zoom, TeamViewer, AnyDesk, etc.
After 2022, users of Microsoft Exchange have to migrate mailboxes to Microsoft Exchange Online, and what I'd like to improve is for Microsoft to publish more on-premise versions for customers using Microsoft Exchange. Having more security is another room for improvement in the solution, particularly for mailboxes that develop the Exchange Edge rule to protect internal mailboxes.
What I'd like to see from Microsoft Exchange in the future is for Microsoft to still update the latest, existing version which is 2022. I'd like Microsoft to still push more cumulative updates for Microsoft Exchange 2022.
I've been using Microsoft Exchange for two years.
I'm impressed with Microsoft Exchange, and I'm rating it five out of five, stability-wise.
Microsoft Exchange is a scalable solution.
Setting up Microsoft Exchange from 2016 to 2022 in an SMB environment is straightforward because Microsoft combined all the cache, hubs, and mailboxes into one server. For large enterprises, the initial setup for Microsoft Exchange isn't as straightforward because large enterprises require more sophisticated setups.
How long it takes to deploy Microsoft Exchange depends on the size of the environment. For example, if I'm going to implement the solution in a small or medium-sized customer environment, then the deployment would take approximately one to two days, but if I'm implementing Microsoft Exchange for a more complex environment that has a minimum of 10 mailboxes and multiple sites, the deployment alone can take up to one week.
My team is responsible for deploying Microsoft Exchange for customers, so the implementation is in-house. I lead the deployment team.
The ROI you get from Microsoft Exchange can be very, very broad in terms of values. The solution, particularly the on-premise version, can save you additional costs compared to deploying it on the cloud, but the downside is the maintenance cost, and during new releases or updates, you may want to schedule the downtime in advance.
I don't have enough information about the licensing costs of Microsoft Exchange, but I do know that you need two types of licenses to run it. You need the product key and the client access key to activate Microsoft Exchange. This means that apart from the standard Microsoft Exchange licensing fees, you have to pay additional costs.
I'm working in a professional service company that's implementing Microsoft Exchange on-premises for customers. I implemented the solution on-premises in 2016, 2019, and 2022. In 2016, I also performed a migration from Microsoft Exchange to Microsoft Exchange Online.
My current company has between fifty to one hundred users of Microsoft Exchange, but in terms of the number of clients my team has implemented the solution for on-premises, it's potentially five thousand.
Deploying Microsoft Exchange for SMB would require just two people, but deploying it for enterprise-scale businesses would require a minimum of three people. Maintaining Microsoft Exchange requires five to seven people for SMBs, and up to twelve in enterprise environments because maintaining the solution isn't as easy.
My advice to anyone looking into implementing or using Microsoft Exchange is the same advice I give to my team every day, which is to be more aware of new information found on the internet in terms of troubleshooting Microsoft Exchange problems. You should also keep on training about sophisticated setups for the solution because you deal with aggressive customers, so I encourage my team to learn about Microsoft Exchange designs, troubleshooting mechanisms, etc.
I'm rating Microsoft Exchange as nine out of ten.
My company is an implementer and consultant for Microsoft Exchange, not a reseller or retailer. The customer is responsible for purchasing the Microsoft Exchange license.
We are using Microsoft Exchange mainly for the email system for my company and other companies I work for.
One of the most valuable features of Microsoft Exchange is its security.
I have been using Microsoft Exchange for seven years.
Microsoft Exchange is highly stable. However, after receiving some updates it can be unstable.
The scalability of Microsoft Exchange is good but it depends on the license.
We have approximately 4,000 users using the solution.
We had to contact support from Microsoft when there was a critical update that we needed to have which fixed some issues we were having.
I rate the support from Microsoft Exchange a five out of five.
The initial setup of Microsoft Exchange is complex. It contains a lot of components that have to be configured perfectly together. After the installation, it works well. It took us two weeks to migrate from one release to another.
I did the implementation of Microsoft Exchange in my company. We have a team of three people that do the maintenance and support for the solution.
Microsoft Exchange itself does not require a license, but users who will have mailboxes will require a license. It depends on the number of users to choose which license. If you exceed 2,000 mailboxes, it's preferable to get the enterprise license.
Many people when they upgrade their mailing system choose Microsoft Exchange.
I rate Microsoft Exchange a ten out of ten.