{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "slug": "dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope", "url": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/" }, "title": "Group recurring FSRM reports around one approved collection scope", "summary": "How should a recurring FSRM report task be scoped and its schedule maintained?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:15:43+00:00", "modified_at": "2026-09-08T18:20:22+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 185, "potentially_affected": "Administrators scheduling File Server Resource Manager storage reports.", "dse_recommendation": "Write a small task register containing each schedule, selected reports, report parameters, destination, and owner.", "primary_source": { "name": "Schedule a Set of Reports", "url": "https://learn.microsoft.com/en-us/windows-server/storage/fsrm/schedule-set-of-reports", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

An FSRM report task defines the reports, parameters, storage paths, frequency, and output formats for scheduled collection. Microsoft recommends putting multiple reports on the same schedule so collection occurs once. The bulk report-management action can change included reports and their parameters; schedules and delivery addresses must be changed within individual tasks. Microsoft documentation.

\n

Applicability

\n

Identify the storage question, recurring collection window, covered paths, and recipients. Separate reports that share a collection scope from requests that need different delivery or scheduling decisions.

\n

DSE recommendation

\n

Write a small task register containing each schedule, selected reports, report parameters, destination, and owner. Ask the storage owner to approve the collection window. When changing several tasks, explicitly review their individual schedules and addresses rather than assuming the bulk edit covered them.

\n

Verification

\n

Inspect the first scheduled run and compare the produced reports with the approved register. Confirm the timestamp, included paths, output formats, and recipient list. Record processing errors or missing reports, and revisit the schedule if the measured collection window conflicts with other agreed operations.

\n

Official references

\n

Microsoft Learn: Schedule a Set of Reports. Source reviewed September 8, 2026.

", "content_text": "Source facts\nAn FSRM report task defines the reports, parameters, storage paths, frequency, and output formats for scheduled collection. Microsoft recommends putting multiple reports on the same schedule so collection occurs once. The bulk report-management action can change included reports and their parameters; schedules and delivery addresses must be changed within individual tasks. Microsoft documentation.\nApplicability\nIdentify the storage question, recurring collection window, covered paths, and recipients. Separate reports that share a collection scope from requests that need different delivery or scheduling decisions.\nDSE recommendation\nWrite a small task register containing each schedule, selected reports, report parameters, destination, and owner. Ask the storage owner to approve the collection window. When changing several tasks, explicitly review their individual schedules and addresses rather than assuming the bulk edit covered them.\nVerification\nInspect the first scheduled run and compare the produced reports with the approved register. Confirm the timestamp, included paths, output formats, and recipient list. Record processing errors or missing reports, and revisit the schedule if the measured collection window conflicts with other agreed operations.\nOfficial references\nMicrosoft Learn: Schedule a Set of Reports. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nAn FSRM report task defines the reports, parameters, storage paths, frequency, and output formats for scheduled collection. Microsoft recommends putting multiple reports on the same schedule so collection occurs once. The bulk report-management action can change included reports and their parameters; schedules and delivery addresses must be changed within individual tasks. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/schedule-set-of-reports).\n\n## Applicability\n\nIdentify the storage question, recurring collection window, covered paths, and recipients. Separate reports that share a collection scope from requests that need different delivery or scheduling decisions.\n\n## DSE recommendation\n\nWrite a small task register containing each schedule, selected reports, report parameters, destination, and owner. Ask the storage owner to approve the collection window. When changing several tasks, explicitly review their individual schedules and addresses rather than assuming the bulk edit covered them.\n\n## Verification\n\nInspect the first scheduled run and compare the produced reports with the approved register. Confirm the timestamp, included paths, output formats, and recipient list. Record processing errors or missing reports, and revisit the schedule if the measured collection window conflicts with other agreed operations.\n\n## Official references\n\n[Microsoft Learn: Schedule a Set of Reports](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/schedule-set-of-reports). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "url": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Group recurring FSRM reports around one approved collection scope", "item": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "url": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/", "headline": "Group recurring FSRM reports around one approved collection scope", "description": "How should a recurring FSRM report task be scoped and its schedule maintained?", "abstract": "How should a recurring FSRM report task be scoped and its schedule maintained?", "articleBody": "Source facts\nAn FSRM report task defines the reports, parameters, storage paths, frequency, and output formats for scheduled collection. Microsoft recommends putting multiple reports on the same schedule so collection occurs once. The bulk report-management action can change included reports and their parameters; schedules and delivery addresses must be changed within individual tasks. Microsoft documentation.\nApplicability\nIdentify the storage question, recurring collection window, covered paths, and recipients. Separate reports that share a collection scope from requests that need different delivery or scheduling decisions.\nDSE recommendation\nWrite a small task register containing each schedule, selected reports, report parameters, destination, and owner. Ask the storage owner to approve the collection window. When changing several tasks, explicitly review their individual schedules and addresses rather than assuming the bulk edit covered them.\nVerification\nInspect the first scheduled run and compare the produced reports with the approved register. Confirm the timestamp, included paths, output formats, and recipient list. Record processing errors or missing reports, and revisit the schedule if the measured collection window conflicts with other agreed operations.\nOfficial references\nMicrosoft Learn: Schedule a Set of Reports. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:15:43+00:00", "dateModified": "2026-09-08T18:20:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-088-group-recurring-fsrm-reports-around-one-approved-collection-scope/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Group recurring FSRM reports around one approved collection scope" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 185, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Schedule a Set of Reports", "url": "https://learn.microsoft.com/en-us/windows-server/storage/fsrm/schedule-set-of-reports" } } ] } }