Forum Discussion
WSUS DB Tables - Large Tables
Honestly, in your position, I'd just remove the feature and set it up again. Removing the feature does not remove the downloaded content, which helps minimise the impact if you're dealing with a branch office with mediocre connectivity.
The loose logical sequence of events would be:
- Remove the troublesome downstream replica from the upstream parent, then on the downstream replica;
- Remove WSUS features;
- Reboot (call me paranoid);
- Optional: Remove the remote SQL database (I never use WID if I can help it);
- Install the WSUS features;
- Use "wsusutil.exe postinstall" to ensure it's configured to re-use the existing content directory (see article linked below);
- Optional: In the same command, point it to a remote SQL host (again, just my preferred method);
- Once "postinstall" has finished, add it back as a downstream replica to the upstream parent;
- Once it's finished it's initial synchronisation - which is going to take a while, no doubt - run the usual "server clean-up" process using either the MMC, WSUS PowerShell module or wsusutil.exe;
- Prosper.
When I say "take a while" in step 9, I don't mean lots of downloading - though that may also happen if the approvals are significantly different. It takes WSUS a long time to set up the database (which includes pulling the relevant update metadata from the replica's parent), which is what I'm referring to.
If you have multiple content directories and are not sure which one is being used, check the registry under HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\ContentDir.
Article explaining "wsusutil postinstall" (and other stuff) here. The article's from Server 2012 R2, but I've seen no differences using Server 2019. (If it ain't broke, don't fix it)