The setup is difficult because it requires specialists to create domains and activities. 

The initial setup is straightforward and there are no complaints. Exchange took time to be deployed. It requires extensive configuration and setting up servers and managing internal network access. It also includes opening internal network access and server configurations.

On the other hand, Microsoft 365 involves selecting a few options on the portal itself. It is comparatively straightforward and easier to set up.

Office 365 is deployed on the cloud and Exchange is deployed on-premises.

I rate the product's initial setup phase a five out of ten since it can be a challenging process.

The initial setup of the solution is okay. It depends on the level of knowledge of the people setting it up. I found it easy since I have past experience. It needs to be implemented with people with past experience. It is easy to upgrade.

The time it takes to deploy depends on the number of mailboxes. 

We have a team that handles deployment and maintenance. We manage the solution for ourselves and sometimes for our clients. 

The initial setup is moderately easy. It is neither easy nor difficult. It does require Active Directory to be set up properly. Setting it up is not difficult. It takes two days to set up an Exchange server.

The setup is easy. 

I barely had any issues with initial setup of Microsoft Exchange. It involves a few clicks on the initial setup dialogue and that's it.

The initial setup was straightforward and fast, taking only a few days. This swift migration to the cloud within days was particularly notable for a bank, demonstrating the efficiency and effectiveness of the deployment process.

The initial setup of Microsoft Exchange is not complicated. However, if you need to set it up to work in harmony with any other program, you need a very in-depth understanding of the platform. 

If you're using Microsoft 365, it's very easy to setup since Microsoft manages most of it. You simply configure your clients to connect to the Microsoft server using your credentials. 

For on-premises solutions, it's a bit more complex as you need to set up and configure servers. You also have to manage roles and permissions, which is not required for the cloud solution.

The setup time can vary. For a small environment, it can take a day or less, especially if you're using a cloud solution like Microsoft 365. However, for larger deployments, there's additional work involved in configuring and optimizing the system.

Many users prefer Microsoft 365 as a cloud solution, which is easy to set up. However, there are still users who opt for on-premises solutions, which require more setup and management. Some are transitioning from on-premises to the cloud for better flexibility and management.

The initial setup is very straightforward. It just took a minute. It is very easy. 

The initial setup is straightforward. There's really no problem with the setup of the latest Exchange servers and Exchange in general. We deployed in-house and didn't need any external partner to handle it.

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.

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.

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.

The installation of Microsoft Exchange is easy.

The solution isn’t exactly straightforward. It’s pretty complex. The configuration can be difficult. It takes a while to set up, and you need to have some advanced knowledge in order to implement it correctly.

Based on who you have that is doing the deployment, it could take up to about three days or even maybe up to a week. However, in terms of a deployment plan, we need to analyze in terms of what we do internally and what outcomes we're actually seeking, and put the project plan in place with some timelines.

Internally, you might need one to two people to handle the initial setup. We had two engineers.

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. 

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

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

The tool's deployment is simple. 

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.

The installation process was straightforward. There were not that many difficulties.

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. 

The product is easy to install and deploy. The development steps included creating DNS records, followed by synchronizing with the Active Directory and facilitating user logins.

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.

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. 

The initial setup of east to do for Microsoft Exchange.

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. 

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. 

It was a little bit complex to set up, so we had to get external help. 

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. 

Setup is straightforward for administrators if you understand networking services and the need for an active directory service. Exchange is a site-aware service, so you must have a good grip on active directory services. You need a deeper understanding of the networking layer, internet services, and broadband before you can manage it on your own as a system administrator. These are services that an experienced administrator can handle.

I was able to do it all on my own. I have robust experience in hardware, installation and maintenance, operating systems, networking, routing and switching, security as well as database administration, and a little bit of user support too. I can also support the exchanges from the client side of it. 

In terms of deployment and maintenance, I do need a support engineer just to help with the labor. I also need maybe other system engineers as a backup. Then there's the technical team. Okay. In a corporate environment, you have people to deal with management influence, IT governance, and all the business cases underneath all that. Then you have the administrative level, including the security admin, a Windows admin for the Java site, then you have the Exchange admin. On the support level, you have user support.

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.

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.

Most of the process is straightforward.

The setup was easy. When we first deployed Exchange, we had some guidance from Microsoft, but now our engineers use it effortlessly. 

The initial setup of Microsoft Exchange is straightforward. It did not take a lot of time.

We needed two people for the deployment and maintenance of Microsoft Exchange.

It depends on the organization. If it is an SME, it is going to be straightforward. If it is an enterprise, it is going to be complex.

The initial setup is straightforward for the small use cases. Each case is different, but for the most part, it's almost straightforward. 

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 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.

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.

The deployment could be easier. 

I believe the installation lasted a couple of hours. However, further integration takes time and this can vary with the additional features one wants, customization which is based on the ETA, the rules and one's desire to make the solution visible to others. 

Once the solution is wholly deployed, there is not much need for further intervention. 

It's easy to install and took about three to four hours.

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.

It's easy. Easy to use. Not complex.

Depending on the customer's requirements, it could be easy to install or it can be very complex.

If it's a new, fresh deployment, then it's very easy.

When migrating, we have to follow the restrictions of Microsoft and sometimes it can be really complex. It depends on customer scenarios.

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

The initial setup is very simple.

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

The installation is very easy.

I have myself and two others to maintain and deploy this solution.

When I joined the company, my laptop was pre-configured, so everything was already done.

The installation is simple for the clients.

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

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

Exchange isn't a very hard solution to implement, though the infrastructure can require some changes in advance. Deployment can take anywhere from a few months to a few years, depending on the size of the customer and the project.

The initial setup is straightforward.

The initial implementation of Microsoft Exchange is simple.

Not applicable.

It was easy to set it up.