Troubleshooting Lync Server 2010 Meeting Content Viewer: Common Issues & Fixes

Optimizing Performance — Lync Server 2010 Meeting Content Viewer: Best Practices

1. Use the latest Meeting Content Viewer build

• Install the June 2012 cumulative update (DMViewer.msi) or later to pick up bug fixes and performance improvements.

2. Put the tool on a well‑spec’d analysis/administration workstation

• CPU: quad-core or better.
• RAM: 8–16 GB.
• Fast local disk (SSD) for temporary extraction of archived content.

3. Reduce archive file size before opening

• Open only the necessary conference archive (.ucca/.cab) or export smaller time windows instead of entire pools.
• If you manage archiving, configure Archiving to split by size or time to limit single-file sizes.

4. Use a current supported OS and up‑to‑date .NET

• Run the viewer on a supported Windows build with the latest Windows updates and an appropriate .NET Framework version the tool expects (follow Microsoft KB guidance).

5. Disable unnecessary UI features and background apps

• Close other heavy apps (browsers, VM instances, indexing) while analyzing large meeting archives.
• Turn off automatic antivirus real‑time scanning for the viewer’s working folder (or add exclusions) to avoid I/O stalls.

6. Work with extracted content when possible

• Extract archive contents to a local folder and point the viewer at extracted files to avoid repeated decompression overhead.

7. Monitor and tune I/O and memory

• Use Task Manager/Resource Monitor to verify the viewer isn’t memory‑starved; increase workstation RAM if you see heavy paging.
• If disk I/O is the bottleneck, move archives to an SSD or faster storage.

8. Use network considerations for remote archives

• Copy large archives locally before opening instead of opening over slow WAN links.
• If unavoidable, ensure a stable, high‑throughput link and consider SMB tuning or file transfer acceleration tools.

9. Limit concurrency

• Avoid running multiple instances of Meeting Content Viewer on the same machine against large archives at once; stagger analysis to reduce contention.

10. Log and report reproducible performance issues

• Capture the viewer’s logs (and system resource snapshots) when you hit performance problems and apply the cumulative updates or submit to Microsoft with the reproduction steps.

If you want, I can produce a short checklist you can paste into runbooks for admins.