WSUS Question

phillracer · 11th July 2007

Hi all,

Just a question I understand that WSUS only works with computers that are connected to a domain.

I work at a computer shop and we have many computers that come in for updates and we do several builds every day. I am looking for a fast solution that allows me to update all these computers without having to join them to our domain.

I look forward to your replies :-)

MOROZCO · 19th July 2007

I dont think it matters if they are on the domain or not, if they can reach your WSUS server from the inside or outside it should work. They will have to change their reg settings to point to that server, so basically instead of using a RSOP just hack the registry

phillracer · 1st August 2007

Thanks for your reply. Is there any other way to do it without altering the registry? I would really like it to be as automated and simple as possible. E.g. Have a software update server and then we have a application that allows the client to connect to that server download and install the updates and at the end of it the client can take the computer home and continue doing updates normally via the Windows Update Website.

It would be good if we could just point the browser to the server but I have had a go and it appears each client needs to be a part of the local domain.

Do you have any more suggestions you can provide or know of a piece of software which may assist me to do this? If not does anyone know of a WSUS specialist that may be able to help me with this issue.

Thanks for your reply so far

**ReggieB** · 2nd August 2007

I've seen good reviews of GFi Languard.

**Bursley** · 2nd August 2007

I don't believe that WSUS would suite your needs as it requires domain clients, and preferably a group policy to point systems to the WSUS server instead of Windows update.
In addition to that, it only supports Windows 2000, XP Pro, Vista, and Windows server editions. Meaning that most home users can't be updated via WSUS because Windows Home edition don't support attaching to the domain.
Other patch management systems are available, such as those from CA, or Symantec that may be able to help you. Patch management is becoming big business, and managing patches to home users is just now starting to grow.
In most cases, a patch manager would require some kind of client installed on the host to inventory the patches that are necessary. This client could just be temporary for the purposes of your service.
Perhaps something easier may help in the mean time.
Setup a caching proxy server, and cache the contents of Windows Update. Then when users access Windows update via your Internet connection, they would download the patches directly from the cache. You can configure a Squid proxy server to handle this.

phillracer · 16th August 2007

Hi all,

Thanks for your suggestions. At this stage I have gone with the caching proxy server. This seems to allow me to deploy updates to clients quite fast.

Thanks Bursley and thanks to all the other members for your input

Jowl · 10th September 2007

Hi,

I'm new to the forum but it sounds like AutoPatcher would(have) been perfect for you. It was a single download (per OS) that would install all M$ updates and a selection of 3rd party tweaks/plug-ins if requried.

Sadly Microsoft have now move to try and 'shut down' autopatcher (despite knowing about it for 4 years) - however, I am sure it will continue. There was nothing dodgy about it just an easy way to update multiple machines.