Phish, you say you can hack the install to get it to run on a non server based platform? Does that violate the EULA? Any comments from someone who has looked into this? Software compliance is a priority where this could be deployed.
I beleive it does violate the EULA. They require 2K or 2k3 Server. I just happened to find a way to hack it up a bit. see this thread

On my home network, I installed it on a multipurpose server. (file/print/AD/dns/wus)
I only have a handfull of workstations on my home network though.

On bigger networks, I installed on a dedicated server.

We're using per seat licensing though... not per server... so I already had the licenses.
I'm no licensing expert... but per seat should cover it. I hope.

As far as the rollback feature... I just deploy to test boxes first. If all is well, then I deploy to the rest of the boxes. If you're only rolling back your test boxes (which shouldn't be that many?) then you shouldn't have too many problems. I took 2 workstations from each department, so I only have about 14 test workstations.

I was considering sharing this with a backup server since patch peak times are pretty much scheduled and could be run on a weekend and not interfere with the backup flow.
One thing I noticed is that no matter what you have for your install schedule... the workstations will download as soon as the update is approved. It will then install at the scheduled time.

Here is review from windowsecurity.
http://www.windowsecurity.com/articl...es-Review.html

here is some more wus material
http://wus.editme.com/WhatIsWUS