Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Where remote staff should save files: local PC, hosted share or application store

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Remote staff lose work when they save to the local laptop only, when non-persistent sessions or pool reset policy discards data that never reached backed-up storage, or when administrators wipe a session without a saved copy. Folder redirection (editorial summary: redirecting profile folders such as Documents to network storage when you deploy Group Policy that way) does not inherently clear those paths on every sign-out—whether files survive depends on pool type, logout policy, redirect targets, and backup scope. A one-page save standard should name where each file type belongs: hosted share, application database, or approved customer-controlled storage—not “wherever Explorer defaults.”

Why it matters

Confused users blame hosting when files vanish after a PC refresh. Compliance-minded owners need custody on systems they back up and can hand over on exit. File location is a productivity and portability decision tied to backup scope, not a personal habit.

How it works

Processing happens on the RD Session Host; saves either remain on host-side storage (profiles, redirected folders, shares mounted to the session) or traverse redirection to the client. Microsoft’s RDS roles article links to planning guidance for secure data storage on session hosts, and describes collections of shared session hosts where multiple users sign in with non-administrative accounts.

User Profile Disks (UPDs), folder redirection, and FSLogix profile containers are distinct designs for keeping user data on supported storage rather than only on a disposable session image. FSLogix places profiles in VHD-based containers on administrator-chosen storage; UPDs follow deployment paths described in Microsoft’s secure data storage planning article. The right choice depends on persistence, backup scope, and whether pools are non-persistent. Folder redirection does not inherently wipe files on sign-out—loss risk comes from your temporary-profile, non-persistent pool, reset, and backup policy, not from the redirection feature name alone (editorial framing where Microsoft’s cited pages discuss UPDs/FSLogix more than every redirection edge case).

Redirects that map Documents to the laptop help locally but may bypass hosted backup if IT only protects server volumes. Saves inside the LOB database are application-owned and may ignore Explorer paths entirely.

Labelled example — engineering drawings: Save to \\hosted-files\projects\ mapped in session; nightly backup scope includes that share; local Downloads forbidden for masters.

Labelled example — temp spreadsheets: Allowed on a persistent profile container if your design uses FSLogix or UPDs; risky on non-persistent pools without redirect rules.

What to choose and why

Location Survives device loss? Typical use
Hosted SMB share / app store Yes, when backed up Authoritative business files
Persistent profile / UPD / FSLogix Yes, for profile content Roaming user settings and documents in profile scope
Local PC / redirected client drive Only if PC backed up Low-risk drafts with policy
LOB database attachment Depends on app backup System of record

Publish a one-page save standard: default path per department, banned paths, and how to recover from autosave. Align with printing and disconnect guidance so staff know unsaved buffers die on reset.

Risks and limits

Folder redirection and UPD deployment steps vary by Windows Server version; FSLogix has its own prerequisites. No save-path configuration was tested in a lab for this article.

Sources

Related reading

Learning notes

  1. The authoritative copy should live where backup and exit planning already focus.
  2. Local saves feel convenient and fail on device refresh.
  3. Application “Save” may not mean a file share path users recognise.
  4. Standards must be one page, not a 40-slide security deck.
  5. Session persistence ≠ file persistence unless storage design says so.