Experience with update service shows need for reliability, but support excelsI wouldn't say any of the update services have great features. The only real advantage I have for having Microsoft Windows Server Update Services is if I know or have been informed of a bad update that's causing software conflicts, I can stop it. But I do not depend on Microsoft Windows Server Update Services to keep my machines updated because the failure rates are too high. I have other tools for reporting and inventory capabilities. The inventory tool and the entire backend of Microsoft Windows Server Update Services is poorly coded. It's not very reliable, so you can tell when dealing with bad code, and it may work one day but may not work another. So I had to stop using it because I need something that's reliable, therefore I use other tools for that information. In a pinch, you can use Microsoft Windows Server Update Services tools, but for the most part, they're not reliable enough. I don't believe I've seen any improvement on bandwidth optimization or deployment speed from Microsoft Windows Server Update Services. In fact, the only real improvement comes directly from Microsoft because they stagger the updates. So that helps, but having Microsoft Windows Server Update Services on-premise does not provide any real benefit. Its pricing is just all-inclusive. I don't think about it that way. If somebody tried to sell me Microsoft Windows Server Update Services, I would probably reject it. It's a tool that we have, so we use it, but if I were to pay extra for it, I would say it's not worth it. Some of the main differences between Microsoft Windows Server Update Services and the other tools are that WSUS's backend is based on IIS, which is not a very reliable host method. You're going to have problems getting Microsoft Windows Server Update Services to run when you have a large organization. The speed of it is quite painfully slow, so there's not a lot you can do to get Microsoft Windows Server Update Services to work under stress. The other tools just work. I can tell you what services are running on each of my machines and can stop or restart services. I can inventory the software they have on them with multiple tools, so I know what software is on our machines. I don't have to rely on a tool that works when it wants to and requires so much maintenance to keep it going. Microsoft Windows Server Update Services is only to green check updates that I know are fine, but obviously, it could save me in a pinch if something went wrong.
