Branch offices with slow connections. The classic scenario: A location is connected to headquarters only via a slow or expensive WAN connection. The cache server stores frequently accessed RFS2 data (catalogs, setup, previews, WebApp assets) locally, so that only the initial access places a load on the WAN.

Many clients per location. The more users access the same catalog data, the more effective the shared cache becomes—the first access fills the cache, and all subsequent accesses benefit from it.

Reduces the load on the central AppServer. Recurring file and preview requests are handled at the local site and never even reach the AppServer.