The initial setup for Microsoft Endpoint Configuration Manager is simple. However, the configuration and management are not simple.

Most of my clients are using the on-premise configuration. Cloud deployment is cumbersome because It requires lots of system communication to open from the cloud, and every client has to communicate with the cloud.

We follow the Microsoft best practices procedure and white papers for implementation. Which includes single and multiple server deployments.

The time it takes for deployment depends on the client's environment, such as the configuration and customization needed. However, the process can typically take two to three weeks to complete.

The initial setup was pretty standard. It was not complex. 

The timeline for setting up this system depends on the number of endpoints or end-users involved. For example, during my time at Walmart, where we were supporting around 350,000 endpoints and 8,000 servers, it took a few months to get the environment settled. In my current organization, which is focused on internal services, it only takes about a week, sometimes even just a couple of days. The process, though, remains quite similar. It can be done by a lot of people but requires support from teams. 

The setup process typically involves configuring prerequisites, setting up SQL Servers (especially for larger environments), and dealing with any network restrictions. Some networks have specific requirements and restrictions that need to be accommodated. As mentioned earlier, ensuring that your system can communicate with agents across the environment is crucial. In more basic terms, you'll need relays or distribution points in each data center or location. These distribution points help in routing and redistributing the data efficiently. The complexity of the setup mainly hinges on the number of offices and locations you're dealing with. Fortunately, the setup itself is straightforward and user-friendly, so understanding it doesn't require much time if you're familiar with the process.

The setup is extremely easy and I would rate it 10 out of 10. 

You need to have a database and have your server and drives configured in a certain way. You should know what your WAN links are, if you have WAN links, and the number of computers which will be used. In this sense, it is complex to set up because you need to know a lot of stuff going into it, and gathering that information can sometimes be difficult. If you are just talking about running the installer and typing in that information, that part of the process has always been easy.

Initial setup was complex. There's a lot that goes into it.

The initial setup is straightforward. We had a team of three people that configured and deployed Microsoft Endpoint Manager. 

We deploy this software in our endpoint computers, most of the staff computers and laptops, as well as 50% of the staff laptops that are signed out. We are also trying it on some mobile devices to see the results before rolling it out to all mobile devices. 

My understanding is that the installation is a two-day setup, however, I did not personally set it up, and therefore can't speak of the implementation or how easy or difficult it might have been.

The initial setup is not complex, and the deployment time can vary depending on the company's size and the deployment's specific needs. Moreover, the solution can be started quickly if you have a server and a schedule with the primary setting.

The maintenance of the solution depends on the scope of the company's usage. For example, a large company may need a tracking system deployment and a team of four engineers for maintenance.

Additionally, there is a need for fees in order to implement changes, and there may be a charge of 30-40% for a different scope.

I work in the lab. I design a solution before it's deployed in production. I wasn't involved in the actual deployment. Deploying things in the lab is different. It's a much smaller footprint.

The initial setup is a bit challenging. We have a relatively complex environment. It's a little bit more complicated than it might be for a smaller environment. It can be relatively straightforward, but there are some twists in our environment.

The initial setup is straightforward.

The initial setup of Microsoft Endpoint Configuration Manager is simple.

We did not face any challenges with the initial setup of Microsoft Endpoint Configuration Manager. The time it takes to do the deployment depends upon the size of the environment. Smaller deployments don't take more than a week and very large deployments can take up to three to six months.

It is a Microsoft product, and we have an efficient team that is managing the solution. We have a lot of people who have the knowledge of doing its setup. So, deployment is not an issue for us. If you know the product, it is quite easy. You just need the knowledge of the product.

From the beginning to the end, it took about six months. It was deployed on all PCs.

If the solution is being deployed by someone with experience, it can be done in about two hours. They're pretty good with hydration kits where you can configure all the prerequisites and all the components, and you're up and running in about two clicks. It's the customer and budget that dictates how complex or how involved a setup is. If they're only leveraging a couple of the core features of the product, it's pretty straightforward, but if they want to use more advanced functions and distribute that out and do low balancing and that sort of thing, it takes a little more time. Generally, clients allow us to integrate for them, we conduct a turnkey training solution, and then they take it over.

It's not easy to implement MECM at first because you are required to have some experience on how to deploy the database for MECM. At our company we already have people working in the data center who have lots of experience in deploying with VMs and virtualization (e.g. Hyper-V and VMware), but for me, implementing MECM was difficult.

It took us around six months to complete the entire implementation because our company has several remote locations which have to be served by the remote distribution server and distribution point servers, and after implementing each server, you have to test it extensively before you put it into production.

The initial setup is very straightforward. We have six users. 

The initial setup is straightforward because Microsoft is always user-friendly. They will share the parameters, like troubleshooting steps and the pre-request. They will send the database knowledge-base document to us. It will be a step-by-step procedure. There won't be any worrying or alarming issues with Microsoft. If we have any problems, we will raise a ticket with Microsoft, and the team from Microsoft will help us. We can implement this solution within two or three hours, depending on the bandwidth speed.

On a scale from one to five, I will give the initial setup a four.

The SCCM deployment difficulty level and time frame are dependent on how large the deployment is. If it is a large company then it can be complex. It can range in time from a couple of hours to a couple of days to a couple of weeks.

SCCM is an old on-premise solution. We're moving through to MECM and that is a cloud-based solution to do similar functionality, such as Intune. SCCM is used at its most. We will not increase the use of SCCM.

The initial setup takes planning and careful consideration. It will also take input from your networking team, as it will take some router configuration to get PXE booting working. The overall design of the SCCM servers needs to be considered as well, as you can't change the big picture structure later. You have to decide if you want only a primary site or if you want a central administration hub with primary sites reporting to it, so it will take planning to setup.

Configuring the groups, collections, boundaries, and server roles takes time as well. It will also take an understanding of the business's needs and will require IT helpdesk input to be most effective.

Configuring applications and settings takes a bit less time once you have the underlying infrastructure setup, but SCCM doesn't really help you discover install commands outside of MSI or APPX packages. To be fair, there's not much they can do, but a technician will need to be aware of that.

The tool's deployment is easy. It takes between five to 25 minutes to complete. 

I rate the product's ease of deployment a four out of ten. 

The initial setup is straightforward.

I rate the initial setup of Microsoft Endpoint Configuration Manager an eight out of ten.

The specifications for the SCCM and the organizational capacity can make the installation complex otherwise it can be easy.

We don't find the initial setup to be complex. We've done many implementations a this point, and we find it to be straightforward. Our team is very much experts at this point. They know all the processes and they go through everything step by step. 

In terms of how long it takes to deploy the solution, this question is very tricky. It's all dependant on the customers, and their environment as well as the customer's readiness to proceed. If it's a POC, where I don't have any dependencies on the customer side, that everything will be within the private network, isolated environment, I can handle a deployment within two days. We can install, configure, and make everything ready in that short amount of time simply because we don't have customer dependencies.

You do need to have the correct people in place to manage it once it's up and running. They need to be experienced and dedicated to the product.

The initial setup is straightforward. I give it an eight out of ten for ease.

The installation is not easy. As with most on-premise solutions, they are not easy to install. Microsoft documentation is complicated and goes on and on. It's a lot to try to assimilate the information. With a cloud solution, it makes it a bit easier. However, even with Microsoft Endpoint Configuration Manager being on-premise with Intune, it's still not straightforward. The time the implementation took for us to complete was a couple of weeks with a five-person team.

In recent times, a lot of companies have begun to move away from Microsoft Endpoint Configuration Manager. The endpoint configuration is very convoluted to implement. In most companies, you need to have a very large dedicated team to manage the solution on the back end. 

A lot of companies are looking to cost savings. With the advent of cloud solutions, companies have the opportunity to receive a lot of cost savings. There are a lot of ITSM tools that will do asset management for you, change management, converged asset management, and updates. There are other ways to configure updates and deployment. The solution is a bit convoluted and expensive.

We have had a deployment in our enterprise for more than five years. It's a relatively complex deployment due to the fact that we have a large organization.

I am one of the enterprise engineers. I make deployments happen at a new location and it may just be a matter of training the onsite technician at that new division on how to make use of it. We have an enterprise-grade deployment and we have divisional deployments where divisions can make use of it to still manage their in-house shops.

The initial setup was straightforward.

The deployment process is very simple. It's not difficult because it gives you a variety of features. You have to create a collection or a group, and you deploy it. It's very slow and dependent on the network. 

A single person can install and deploy this solution. If you have an application already created and tested, that's fine. If you do not have one, then you have to build the application and test it. If everything goes fine, you can simply deploy it to the list of people you want to target. I wouldn't say that you need many people, but it depends on your operation and how you manage your environment.

The deployment time depends on the location it's going to, the bandwidth, and more. You can configure a time for the application to replace the policy or when the machine will replace its policies in the configuration settings. Suppose I'm an administrator and deploying something on your device; your machine will not get turned on. I will go ahead and update the application evolution cycle and machine policies so that it happens automatically. Once the 30 minutes clock starts, it'll update, and once it refreshes, it will see something I sent, and it'll start downloading it. 

Downloading is always completely dependent on how fast your internet is. Once the package is downloaded, you can simply go ahead and install it. Small packages will take about an hour at most to deploy. For bigger packages, it's completely dependent on the internet because this tool does only one job. It's like a postman as it takes one thing from you and gives it to the other person.

There are periodic updates, and the maintenance is also done. The patch update service is critical and has a significant impact.

The initial setup was straightforward. It's a matter of downloading from Microsoft, updating on the console and deploying. The amount of staff required for deployment depends on the level of infrastructure. Before the deployment, you need to test the machines to check whether a particular patch is installed and updated properly on that machine and whether there are any bugs. Installation is a step-by-step process. We can do about 20,000 per week, so within five weeks the job can be done. If there are only 10,000 machines, deployment can be completed within a week. 

As someone who is quite familiar with IT, the initial setup was quite straightforward. It would definitely be complicated if you're not familiar with IT.

In terms of the current initial setup, the new version is a little bit more complex as you need to design a great architecture for the enterprise environment when we use a lot of virtual machines. For example, when you have more than 1,000 virtual machines, there needs to be a high level of consideration for the design of different components of the System Center.

In terms of deployment, if you have a good design, the process may take about a week. You need, I would guess, one week for installing and preparing the environment. However, you need to relay different instructions in order to install it. In total, the process would take around one, or, at a maximum, two weeks.

Our team consists of five members; one senior and four support engineers. Their job is to configure and maintain the active directory environment and the SCCM platform.

I did a lot of research before I set it up. I watched a lot of YouTube videos, talked to Microsoft, demos, etc. I did enough homework so that when we set it up it was pretty simple. You just have to understand the SCCM infrastructure and how it works. If you don't understand that it might be confusing when you first install it. You have to understand your primary site, your secondary site, your distribution points and how they work, so you know how to set it up correctly.

After that, installing it was easy. Just understanding what connects to what. What has to go first, what has to go second, what services you need installed and set up, and how to set them up. Once you do your research on that it is pretty simple. But if you go in blind, I can see how it could be rather difficult.

The complexity of setup depends many factors such as the number of sites or distribution points and whether they will be centrally administered. Proper planning and execution are important. 

Deployments of an ICCM server can take up to four weeks. 

The initial setup is easy. It's not overly complex. That said, anyone who's doing it needs to be a bit clever. It's not for people with little technological background. There is a bit of research required. You need to learn a bit about the product for effective deployment.

I have not done the initial setup alone, and I wouldn't recommend doing it for anybody who didn't know what they were doing, or that hadn't done it before, because you have to go through a certain learning process.

I have seen that a base installation complete can be done in three days, and I have also seen an environment with 1,000 workstations deployed in two weeks.

The initial setup of Microsoft Endpoint Configuration Manager was simple.

The installation requires a lot of knowledge and experience. The whole process took us three months.

The initial setup is straightforward. It's easy for us.

We have a team of four to deploy and maintain this solution.

The initial setup was straightforward and took around five hours. It was carried out by the two administrators in the company. We also have people on the team who are familiar with SCCM.

The initial setup for this solution is straightforward. It is a Microsoft-based product, and they usually have startup wizards. It is graphical, and the process of installation is self-explanatory. It is easy, even for a new user.

The initial setup, depending on whether it is a server and what tests have to be done, might take about two hours.

Once running, the time required for the deployment of updates varies depending on how many computers you are deploying to. If you have, say two thousand computers, then it will take approximately a week for all of them to be fully updated. This also depends on how regularly the computers are online. In cases where systems are frequently offline, it will take even longer. Once they come online, they get the deployment and update.

The first priority after installing the software is to gather all of the end-user devices. Make sure that they are all covered and up to date all of the time.

One IT administrator is enough to deploy and maintain this solution.

The initial setup is pretty straightforward.

Depending on the customer and their infrastructure, it could be easy. If it is a small infrastructure the installation could be quite quick. You could fire up SCCM, sent the probes, let them detect it, and put it in. 

For large infrastructures or complex networks, it can be more difficult. It can take as long as a day to get it all set up and running or it could even take a week.

One of the joys of SCCM is that one person could easily maintain it but we have two people from the service desk.

The first setup was quite complex but primarily due to wide capabilities of the product itself that need time to be customized.

I was not involved in the installation of this solution.

The initial setup was straightforward and took us about a week to deploy this solution. The strategy was simple. We just had to do it in the same plugin, and we actually did learn on the job each day.

It is easy to install and quick to deploy.

We have admins to maintain this solution.

It is easy.

I did the configuration of SCCM from scratch, however, I did not configure the VMware Workspace One as it was installed on cloud. I basically just did it for an evaluation to have a taste of VMware Workspace One.

Therefore, I don't know about the level of complexity or if it's easy or it's difficult in VMware Workspace One. In SCCM, however, there were some issues which I had to search and get assistance with and there were some issues that I resolved. I would describe it as somewhat complex. It was not so simple that anyone can do it.

For me took me three to four days to configure it and set it up in perfect working condition. That was mostly due to the fact that I took some time to research the issues I came into contact with.

The main production server is in our data center in Pakistan and production site server in Qatar and UAE, and their configuration is performed by a team in corporate office in Pakistan

The initial setup was straightforward. It was quick and it took a day. We didn't have any issues.

We are very knowledgeable about SCCM so for us it takes an hour or two, at the most, to set up. For other people, it may be complicated, but for us, setup is the least of our concerns.

The initial setup of Microsoft Endpoint Configuration Manager is straightforward. The time it takes for the process depends on the environment, typically it can take one day.

The installation was not too difficult.

The initial setup is complex.

You need more than one person to manage the environment.

It is not hard to deploy and manage, but you need some knowledge of what you want to do. SCCM is strictly based on the specific configuration of the network. Therefore, you need to know the network configuration and how to use Microsoft Active Directory. If you have made a bad choice at the beginning, it will be hard to roll back and redeploy it. It works well when the environment is well configured. It doesn't really work well when the corporate network is not as good as it should be.

The initial setup is not complex. I believe it is very straightforward. You can choose to do it manually or you can do it via an automation feature that is available to push everything for you. 

Depending upon how big your organization is, how the sites are spread across mainly on physical entities, on logical entities, the installation and the detection will not take much time. In most cases you can have it configured in five to ten minutes in order to detect once the reporting gets updated. That said, if there are different geographical locations, the entire process can take a day or so. 

It is straightforward. I am currently setting up a new version, and it is easy because we have the existing infrastructure.

The initial setup, for the most part, is not complex. It depends on the company's individual setup, however, it's quite straightforward if you know what you are doing.

Deployment typically takes about three months.

You only need about four staff members for deployment and maintenance. They are all systems specialists and engineers.

The setup was complex and I faced a lot of problems initially because I was new to the solution.

The initial setup was not easy. It takes about half an hour to install, and then it has to be configured. The deployment will take approximately six hours in total.

I would say it's a bit complex. There are prerequisites which you have to install first before installing SCCM. You need a server in place, a SQL database and some other software installed separately, for example, Management Studio.