Under attack? Emergency incident response, remote or on-site.Get help now →Call (360) 524-3477

FileCabinet CS Export Timing Out in Virtual Office? Why It Happens and What to Do

Exporting from FileCabinet CS inside Virtual Office CS is slower than it ought to be, and long exports have a habit of dying overnight. None of that is your imagination. Here’s what Thomson Reuters’ own documentation says causes it, and what you can do about it.

Why exports stall

The inactivity timeout

Thomson Reuters lists FileCabinet CS on the desktop at a 30-minute inactivity timeout (Thomson Reuters). The countdown starts from the last time you used the remote session window, and activity on your own computer doesn’t count (Thomson Reuters). Once it times out, a sign-in prompt appears and programs can look frozen until you authenticate again.

Nightly maintenance

Thomson Reuters’ Virtual Office migration guidance warns that long-running jobs can be interrupted by the nightly reboot around 4 a.m. Eastern. An export left running overnight may simply stop.

Slow copies to your own computer

Moving files out through the mapped local drive is slow. Thomson Reuters describes archiving to the local drive as “time consuming and prone to failure, and may result in lost data” (Thomson Reuters), and Microsoft lists local-drive performance in Azure Virtual Desktop as a known issue (Thomson Reuters troubleshooting guide).

Big exports are heavy

Thomson Reuters calls large exports resource-intensive and says it doesn’t recommend linking all drawers together to export them at once (Thomson Reuters).

Workarounds if you’re exporting it yourself

  1. Test first. Export a handful of drawers and time it before planning the rest.
  2. Work in batches you can finish in one sitting, and keep a simple log of which drawers are done.
  3. Keep the remote window active during long exports, since local activity doesn’t reset the timer.
  4. Avoid running across the 4 a.m. Eastern maintenance window.
  5. Export inside Virtual Office first, then copy out in fewer, larger chunks rather than thousands of small files over the local drive.
  6. For big batches, try “Export documents to PDF file as images,” which Thomson Reuters suggests for large exports, though the files can be bigger.
  7. Name files by Drawer ID so a half-finished batch can be sorted out later.

Why automation rarely saves the day

Virtual Office is a locked-down remote desktop, so automation tools can only press keys and match what’s on screen. In our case study, a firm’s drawer-by-drawer automated export failed every few hours and had to be restarted by hand.

The bulk export route

TekBryte’s bulk export doesn’t depend on Send to > File, so session timeouts and the nightly reboot stop mattering. For that same firm, 1,463 drawers came out in about three hours of unattended running, folders, annotations and drawer notes included, with each document proven identical.

Still want to do it yourself? Start with our step-by-step guide to exporting from FileCabinet CS.

Tired of babysitting exports?

Tell us how many drawers you have. We’ll answer within one business day with a fixed price.

TekBryte FileCabinet Recover iconExports run on TekBryte FileCabinet Recover, our own bulk-export software.

See FileCabinet CS bulk exportCall (360) 524-3477