I have been using WSUS to deploy patches to multiple servers and our last successful WSUS's synchronization was in Oct 2012. However, in Nov 2012, I had created a zero-byte .cab file after running the command, WSUSutil.exe export. Till now, I have tried the following methods as follows, but to no avail:
- Re-index and defragment WSUS 3.0 databases.
- Run the Server Cleanup Wizard to clean up the WSUS database.
It seems that the problem occurs due to the generated temp files, which was more than 2GB during the export process (Note: The .cab file format has a 2GB limitation).
According to Microsoft TechNet, it seems that many administrators like me are still without a solution to this problem. As such, I really look forward to Microsoft's official reply in the WSUS Website and resolution to this problem.