# Treat an FSRM expiration task as a controlled file move

> What should be approved before an FSRM task expires matching files?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-056-treat-an-fsrm-expiration-task-as-a-controlled-file-move/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:15+00:00
- Modified: 2026-09-08T18:20:21+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What should be approved before an FSRM task expires matching files?

## Potentially affected

Use this review when designing an FSRM expiration rule.

## DSE recommendation

Have the data owner review examples that should match and examples that must remain in place.

## Article

## Source facts

Microsoft describes a file-expiration task as moving files that meet selected criteria into an expiration directory, where an administrator can later back up and delete them. A run creates a destination directory grouped by the server that performed the task. The new directory also reflects the task name and run time, while moved files retain their original directory structure. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-expiration-task).

## Applicability

Use this review when designing an FSRM expiration rule. Identify the source paths, selection criteria, data owner, and expiration location. Keep the move decision distinct from a later decision to delete retained files.

## DSE recommendation

Have the data owner review examples that should match and examples that must remain in place. Choose a limited pilot scope and confirm the destination can be administered by the intended personnel. Record how users will locate moved material and how an incorrect match will be returned through the approved process. Obtain separate retention and deletion decisions before scheduling subsequent handling.

## Verification

After the approved test run, reconcile the moved-file list with the selection examples. Check the destination grouping and retained directory structure, and confirm representative files are readable. Investigate both unexpected moves and expected files left behind. Preserve the rule, run time, and owner acceptance before enabling a recurring expiration schedule.

## Official references

[Microsoft Learn: Create a File Expiration Task](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-expiration-task). Source reviewed September 8, 2026.

## Primary reference

- Name: Create a File Expiration Task
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/fsrm/create-file-expiration-task
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Treat an FSRM expiration task as a controlled file move,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-056-treat-an-fsrm-expiration-task-as-a-controlled-file-move/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.