If you’ve been working with WSUS for a while then you’re probably already aware of http://www.wsuswiki.com but if not you should stop by and check it out. One of the cool things about the site is that all information provided on the site is written, validated and edited by users like you. Anyone can change any page or create new pages on this site!
One particular section I really like is the one on troubleshooting. For example, here are some of the sections you can find help on:
- Troubleshooting WSUS Installation – this section looks at troubleshooting the installation of WSUS.
- WSUS Post Installation Validation – some things to do when you first get WSUS up and running, prior to production.
- Troubleshooting WSUS In Production – here we look at errors that might occur in production.
- Troubleshooting Client Setup – looks at the problem with AU clients that do not register in the WSUS Admin console due to a client setup error.
- Common WSUS Errors – Listing of known WSUS error codes and how to address them.
- Troubleshooting Client Targeting – client targeting, an important area of WSUS, also might be an issue and there are some specific troubleshooting steps related to this area.
- Troubleshooting AU Updates With WSUS – here we look at issues with AU updates, once you have your WSUS server(s) in production, and the clients are connecting to the WSUS server.
- Troubleshooting WUS Office Update – this page examines issues around using WSUS to distribute Office updates.
- Troubleshooting Group Policy (GPO)
- Client Configuration Checks & Known Issues – Key configuration troubleshooting steps to check when investigating why WSUS clients may not be checking in. Also information on Two known issues.
- Office Updates and WSUS support – Troubleshooting update support through WSUS or Microsoft Update for Office XP or 2003 Administrative Install points
- Troubleshooting “FATAL: 0x80070005: ERROR:” – Troubleshooting when some clients fail to Install (not download) updates with a Handler FATAL: 0x80070005: ERROR: Remote update handler container process created (PID: 1180), but exited before signaling event
While you’re there, if you see some things you like or maybe some things you don’t, or even things you might like to see added, please let me know. If I get some extra bandwidth I’d love to take a shot at any of the suggestions you might have.
J.C. Hornbeck | Manageability Knowledge Engineer