SBS2008 SP2, all current patches.
Tiny system, so no significant advantage in storing all the updates on the server. But the big disadvantage of storing them locally is 46GB of disk space, which I very much need to clear. The plan was to (1) Set WSUS to have clients obtain updates from MS and (2) Run the cleanup wizard to clear the update cache.
Now, maybe that's a valid plan and maybe it isn't, but regardless...
I clicked OK in step (1) 3 days ago, and ever since, Windows Internal Database has been monopolizing one of 4 CPUs, and has expanded to 1.5GB of RAM. Should I be concerned, or is this expected and I just need to wait it out?
