WSUSTER is a very nice tool, but it seems very sluggish in what it does. I've got a dual quad core 3.00 with 16GB of RAM running Server 2008 x64, and it takes for ever to do approvals and declines. I've noticed similar performance under 2003 x86 aswell.
Wsuster can't be made more efficient and it only uses the needed wsus api calls. Working with a local database speeds up the process or maybe running the cleanup wizard (wsus 3.0). The normal interface will properly have the same speed.
Dean Colpits wrote:
WSUSTER is a very nice tool, but it seems very sluggish in what it does. I've got a dual quad core 3.00 with 16GB of RAM running Server 2008 x64, and it takes for ever to do approvals and declines. I've noticed similar performance under 2003 x86 aswell.
The tool will try to connect to your local installed WSUS server. It uses the WSUS server API calls.
The code in the tool:
Try
UpdateServer = Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer
Catch ex As Exception
'MsgBox("Cannot connect to the WSUS Server", MsgBoxStyle.Critical, "WSUSTER Approval Tool Error"
Exit Sub
End Try
Superseded updates are appearing in the list (e.g. kb885250 superseded by kb957097). If both updates are checked, will only the most current update be installed?
Also, while the interface is simple enough, the Approvals section is confusing. As Alison, requested, is a user guide available?
