What to do when your WSUSContent folder - in SBS2008 grows too large – not working
http://blogs.technet.com/b/gborger/archive/2009/02/27/what-to-do-when-your-wsuscontent-folder-grows-too-large.aspx
I was provided with this link by Microsoft when I have issues moving the repository to another drive. In the past year, the repository grew to over 162 GB’s from only 78 GB less than one year ago.
- So I followed the procedures in the above link.
- It's been several days now and no synchronization has taken place and the empty folder is still empty.
- At this point I'm not sure if I'm supposed to kick off a manual synchronization.
Any help would be appreciated
I was provided with this link by Microsoft when I have issues moving the repository to another drive. In the past year, the repository grew to over 162 GB’s from only 78 GB less than one year ago.
- So I followed the procedures in the above link.
- It's been several days now and no synchronization has taken place and the empty folder is still empty.
- At this point I'm not sure if I'm supposed to kick off a manual synchronization.
Any help would be appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When you say "Re-Approve" updates. is that after I pick and choose what to sync up?
I'm sure it will take the database quite some time to rebuild in addition to the "repository" folder.
any of the SBS2008 rebuilds I 've performed, I immediately install all updates and then use the wizard to move the repository folder over to another drive and off the C-Drive of the server.
I am not experienced with approving updates. Something I need to learn how to do
I'm sure it will take the database quite some time to rebuild in addition to the "repository" folder.
any of the SBS2008 rebuilds I 've performed, I immediately install all updates and then use the wizard to move the repository folder over to another drive and off the C-Drive of the server.
I am not experienced with approving updates. Something I need to learn how to do
You approve the updates with the SBS console.
It will approve some of them for you, but others it will require you to approve them.
However the crucial bit is that it only shows you the updates that are needed by the clients.
Moving forwards, if you add a new machine to the network, I would patch it before you add it to the domain.
Simon.
It will approve some of them for you, but others it will require you to approve them.
However the crucial bit is that it only shows you the updates that are needed by the clients.
Moving forwards, if you add a new machine to the network, I would patch it before you add it to the domain.
Simon.
ASKER
I do use the console for all approvals. I only assumed that there will hundreds and that's not really a good option to approve thru the console.
I agree about new workstations added to the domain. I full update them prior to adding them to the domain
I agree about new workstations added to the domain. I full update them prior to adding them to the domain
If everything was patched, then the approvals list will be small, because it will only be required updates.
Simon.
Simon.
ASKER
great, I'll include the PowerShell script Microsoft provided to perform a full clean uninstall. I'll let you know how that goes.
ASKER
the power shell script only worked if I left the WSUS folder on the c-drive as the default install
- ended up uninstalling and reinstalling. it wasn't very straight forward. Microsoft had issues doing so after I got stuck on the install
- I also found that if you detour away from the original wsus default settings, the sbs2008 console wont communicate with the wsus server.
- ended up uninstalling and reinstalling. it wasn't very straight forward. Microsoft had issues doing so after I got stuck on the install
- I also found that if you detour away from the original wsus default settings, the sbs2008 console wont communicate with the wsus server.
ASKER