WSUS 3.0 is out and available for a free download. I must say this upgrade can only be classed as amusing. We originally used to use the old hfnetcheck command line tools to download our updates so when SUS came out we were quick to jump at the chance and with each new iteration it has been getting better and better.
The first thing you will notice is the new interface that uses MMC, why they didn't do this to start with I will never know. It works and with the download of the reporting pack it does some nice pretty stuff with pie charts.
So last week we thought we would upgrade and upgrade we did, all seemed to go OK and hey presto! we could connect with our new MMC tool (at the loss of the website). So there I am checking through the logs on the DC's after our new Win2k3 addition and what do I find but errors on not being able to contact the WSUS server.
To cut a long story short I am now an expert on WSUS error codes after several hours of Googling said codes. It appears that although the default website was stopped in IIS and not used the upgrade had put part of the new WSUS 3.0 by default into the default website (leaving the v2.0 piece in the WSUS site we created originally) so now it seems like our WSUS install is currently on 2 sites. Anyone care to explain why this happened?
The upshot is due to the default site being stopped all the clients couldn't connect to update the client part and throwing errors and basically failing miserably. Having started the site up I await the 3pm update to see if the clients are playing ball again.
Although we have a nice MMC tool now (you will have to go around isntalling it on any PC's you want to use for WSUS admin) they have removed the website which although a tad on the slow side was handy for checking things out from client PC's. Oh well the price of progress.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment