Microsoft Windows Server Update Services Review

Stable with good patching and good internal updating


What is our primary use case?

We primarily use the solution for internal updates. What happened is that one of our equipment items had a problem with a new Windows update and so we have to uninstall this update. We were looking for ways to do it centrally. There were some Lenovo boxes that were restarting automatically and we had to take out these updates.

What is most valuable?

The most important aspect is that we can centrally deploy the updates that are necessary for the organization. It's important. The solution is great for internal updates.

The solution has very good patches. They recently released one for Chrome, which was quite helpful.

We've found the stability to be pretty good.

What needs improvement?

It's not always easy to set up.

Their Local Group Policy works well for the Microsoft environment, however, we need it or other software as well. We've realized that we have to pay. We have to buy extra items in order to access this catalog of different updates.

The reporting is not as practical as I would like it to be. It's something that I would like them to improve in future releases.

It would be nice if there were more alerts to let us know what is missing. It would be nice if there was an integration with the main server and with the active directory so that I can receive the necessary alerts. It would be good to know which equipment is connected to the directory and which are behind schedule with updates. 

For how long have I used the solution?

I just started using the solution this year, and therefore I've only used it for the last couple of months. However, in this office, they have been using it thing for a couple of years, at least. 

What do I think about the stability of the solution?

The solution is quite stable. It's reliable. There are no bugs or glitches. It doesn't crash or freeze. As long as it can help us manage the data, it's good. 

What do I think about the scalability of the solution?

I cannot speak to the scalability. I have never tried to scale the solution.

How are customer service and technical support?

I've never been in touch with technical support. I cannot speak to how helpful or responsive they are.

How was the initial setup?

The initial setup isn't easy to set up. However, it's not necessarily always hard, either. It has a moderate amount of difficulty.

In our case, we had remote offices to set up in different cities. We have not yet implemented interconnection between these offices. Each office has its own server, its own Windows environment. We have this implemented in our central office, and I would like it across all of our remote offices as well. I'm not sure how long that will take. I'm just beginning to dive into that.

What other advice do I have?

We are just a customer and an end-user.

I'm not sure of which version of the solution we're using.

I'd advise new potential users to implement the product and to regularly check on it. We have some equipment that is not being updated. That's on us. It's necessary, however, to implement constant evaluations for which equipment is actually connected to the solution.

I'd rate the solution at an eight out of ten overall. We're mostly quite happy with the product.

Which deployment model are you using for this solution?

On-premises
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Microsoft Windows Server Update Services reviews from users
Find out what your peers are saying about Microsoft, HCL, Quest Software and others in Patch Management. Updated: June 2021.
522,281 professionals have used our research since 2012.
Add a Comment
ITCS user
Guest