content-delivery.xml 1 2027-01-04T08:00:00 08:00:00 17:00:00 480 2400 20 7 1 1 Standard 1 -1 1 0 2 1 08:00:0012:00:00 13:00:0017:00:00 3 1 08:00:0012:00:00 13:00:0017:00:00 4 1 08:00:0012:00:00 13:00:0017:00:00 5 1 08:00:0012:00:00 13:00:0017:00:00 6 1 08:00:0012:00:00 13:00:0017:00:00 7 0 1 1 Phase 0 — Analysis of the existing estate 1 1

1

2027-01-04T08:00:00 2027-02-03T17:00:00 2 2 C0.1 Validated endpoint count: Configuration Manager clients reconciled with Intune and the asset record, duplicates and stale records removed 1.1 2 2027-01-04T08:00:00 2027-01-15T17:00:00 PT80H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-0-3 3 3 C0.2 Distribution point inventory: every DP with its site, office, OS version, hardware age and warranty, PXE and Connected Cache roles, and content library size 1.2 2 2027-01-04T08:00:00 2027-01-15T17:00:00 PT80H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-0-3 4 4 C0.3 Circuit data per office: bandwidth, peak use, monthly cost and renewal date, from telecom contract records 1.3 2 2027-01-04T08:00:00 2027-01-22T17:00:00 PT120H0M0S 7 0 Network engineering Owner or approver: Network engineering Source: ../books/guides/dp-consolidation-implementation.md#step-0-1 5 5 C0.4 Packaging inventory: every application and package, its installer type, install count, active deployments and last change 1.4 2 2027-01-04T08:00:00 2027-01-22T17:00:00 PT120H0M0S 7 0 Packaging team Owner or approver: Packaging team Source: ../books/guides/dp-consolidation-implementation.md#step-0-3 6 6 C0.5 Funding ask decomposed: acquisition or five-year total cost of ownership, and every item beyond the distribution point itemized 1.5 2 2027-01-04T08:00:00 2027-01-08T17:00:00 PT40H0M0S 7 0 Budget officer Owner or approver: Budget officer Source: ../books/guides/dp-consolidation-implementation.md#step-2 7 7 C0.7 Content library measured on one DP; sizing run against 4,000 clients per DP with a draft hub design and office wave order 1.6 2 2027-01-25T08:00:00 2027-01-27T17:00:00 PT24H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-1-2 2 1 0 7 3 1 0 7 4 1 0 7 8 8 D-C1 Target distribution point count when co-management completes, and the fiscal year 1.7 2 2027-01-27T17:00:00 2027-01-27T17:00:00 PT0H0M0S 7 1 Executive sponsor and CIO Owner or approver: Executive sponsor and CIO Options: A dated target count from the validated endpoint count and Microsoft's 4,000-clients-per-DP limit (about 24 in the worked case); keep the current count (then say why the office count, not the client count, sizes it) If decided late: No refresh or consolidation can be sized, and the decision on the funding ask waits Source: ../books/guides/dp-consolidation-implementation.md#step-1-2 7 1 0 7 9 9 C0.6 Assessment worksheet completed from agency data, reviewed by the endpoint lead, ISSO and budget officer, and kept inside the boundary 1.8 2 2027-01-28T08:00:00 2027-02-03T17:00:00 PT40H0M0S 7 0 Content delivery project lead Owner or approver: Content delivery project lead Source: ../books/guides/dp-consolidation-implementation.md#step-2 5 1 0 7 6 1 0 7 7 1 0 7 10 10 CG0 Gate 0 — Inventory and decomposition complete 1.9 2 2027-02-03T17:00:00 2027-02-03T17:00:00 PT0H0M0S 7 1 Content delivery project lead and ISSO Owner or approver: Content delivery project lead and ISSO Criteria: Endpoint count validated and dated; every distribution point in the inventory and the system component inventory; circuit cost and renewal date recorded per office; packaging inventory complete; the ask stated as acquisition or five-year cost with scope itemized; a dated target DP count; the worksheet reviewed and stored inside the boundary Source: ../books/guides/dp-consolidation-implementation.md#step-0-4 9 1 0 7 8 1 0 7 11 11 Phase 1 — Decision on the funding ask, and Stage 1 in a test hierarchy 2 1

1

2027-02-04T08:00:00 2027-03-03T17:00:00 12 12 D-C2 Decision on the funding ask 2.1 2 2027-02-03T17:00:00 2027-02-03T17:00:00 PT0H0M0S 7 1 Executive sponsor and CIO Owner or approver: Executive sponsor and CIO Options: Refresh in place; consolidate to a hub tier (the guide's recommendation where the circuits allow); cloud-first with Connected Cache, keeping a hub tier only until the five gates close If decided late: Refresh money is committed by default, or the hub build can't start Source: ../books/guides/dp-consolidation-implementation.md#step-2 10 1 0 7 13 13 C1.1 Budget submission revised to the chosen option, the worked case's planning assumptions replaced by Phase 0 data, and its consistency with Intune-first stated 2.2 2 2027-02-04T08:00:00 2027-02-10T17:00:00 PT40H0M0S 7 0 Budget officer Owner or approver: Budget officer Source: ../books/guides/dp-consolidation-implementation.md#step-2 12 1 0 7 14 14 CG1 Gate 1 — Funding decision recorded 2.3 2 2027-02-10T17:00:00 2027-02-10T17:00:00 PT0H0M0S 7 1 Executive sponsor and CIO Owner or approver: Executive sponsor and CIO Criteria: Option chosen with the decision table and worksheet as its evidence; budget submission revised; target DP count and fiscal year recorded; the decision filed in the program's decision register Source: ../books/guides/dp-consolidation-implementation.md#step-2 13 1 0 7 15 15 C1.2 Stage 1: Lab 2 run end to end in a test hierarchy, every change applied and then backed out from its plan.csv 2.4 2 2027-02-11T08:00:00 2027-03-03T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#lab-2 14 1 0 7 16 16 D-C10 Stage 1 to Stage 2: go/no-go for production 2.5 2 2027-03-03T17:00:00 2027-03-03T17:00:00 PT0H0M0S 7 1 Content delivery project lead and ISSO Owner or approver: Content delivery project lead and ISSO Options: Go when Lab 2 ran end to end with its back-out, every cmdlet ran on the agency's Configuration Manager version, the inventory matched the console and the change board approved the production plan; no-go repeats Stage 1 If decided late: No production change can start, and the hub build waits Source: ../books/guides/dp-consolidation-implementation.md#go-no-go 15 1 0 7 17 17 Phase 2 — Hub content tier 3 1

1

2027-02-11T08:00:00 2027-05-05T17:00:00 18 18 D-C3 Hub sites and distribution points per hub 3.1 2 2027-02-10T17:00:00 2027-02-10T17:00:00 PT0H0M0S 7 1 Endpoint lead and network engineering lead Owner or approver: Endpoint lead and network engineering lead Options: Existing regional facilities inside the current boundary, two pull DPs each, with source DPs at the two data centers (the worked case: 12 sites, 24 DPs); more hubs where latency or headcount needs them If decided late: Hub servers can't be ordered or built Source: ../books/guides/dp-consolidation-implementation.md#step-1-1 14 1 0 7 4 1 0 7 19 19 C2.1 Hub DP servers built on Windows Server 2019 or later: IIS, BITS and Remote Differential Compression; CM-6 baseline applied and scanned; HTTPS with a PKI certificate; added to the inventory and the SSP 3.2 2 2027-02-11T08:00:00 2027-03-24T17:00:00 PT240H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-3-1 18 1 0 7 20 20 C2.2 Pull DPs added at each hub, sourcing from the data center DPs; one distribution point group per hub (New-DpcHubTier.ps1 -Apply) 3.3 2 2027-03-25T08:00:00 2027-04-14T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-3-2 19 1 0 7 16 1 0 7 21 21 C2.3 Content distributed to each hub group; distribution status clean; content validation run; inventory rerun 3.4 2 2027-04-15T08:00:00 2027-05-05T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-3-3 20 1 0 7 22 22 CG2 Gate 2 — Hub tier serving content 3.5 2 2027-05-05T17:00:00 2027-05-05T17:00:00 PT0H0M0S 7 1 Configuration Manager lead and ISSO Owner or approver: Configuration Manager lead and ISSO Criteria: Every hub DP in production, baselined, scanned and in the SSP; every package distributed to its region's group with no failures; load per DP under 3,200 clients (80% of the published 4,000); change records for every server Source: ../books/guides/dp-consolidation-implementation.md#step-3-3 21 1 0 7 23 23 Phase 3 — Peer caching and boundary groups 4 1

1

2027-02-04T08:00:00 2027-06-16T17:00:00 24 24 C3.1 Boundary groups for the pilot wave: hub DPs added, peer options set, the other hubs as timed fallback, never to the default site group (Set-DpcBoundaryGroups.ps1 -Apply) 4.1 2 2027-04-15T08:00:00 2027-05-05T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-4-2 20 1 0 7 25 25 D-C4 Client-to-client traffic on branch segments: TCP 8003, UDP 8004 and TCP 7680 4.2 2 2027-02-03T17:00:00 2027-02-03T17:00:00 PT0H0M0S 7 1 CISO Owner or approver: CISO Options: Allow within each office's subnet only; allow for named peer cache sources only; block, and size circuits for hub pulls If decided late: Peer cache and Delivery Optimization peering can't be configured, and the pilot measures nothing Source: ../books/guides/dp-consolidation-implementation.md#step-5 10 1 0 7 26 26 X-E14 Co-management on for the pilot collection (Endpoint plan E1.4) 4.3 2 2027-02-05T17:00:00 2027-02-05T17:00:00 PT0H0M0S 7 1 Endpoint engineering (Endpoint & Device Modernization plan) Owner or approver: Endpoint engineering (Endpoint & Device Modernization plan) If decided late: Pilot devices have no Intune channel for Delivery Optimization policy Source: endpoint-device.md 4 2027-02-05T17:00:00 27 27 C3.2 Peer cache sources chosen per pilot office (desktop chassis, disk, always on); client settings deployed; partial download on; BranchCache enabled 4.4 2 2027-05-06T08:00:00 2027-05-19T17:00:00 PT80H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-5-2 24 1 0 7 25 1 0 7 28 28 C3.3 Delivery Optimization through Intune: Group download mode with a group ID per office, or subnet restriction, for the pilot devices 4.5 2 2027-02-08T08:00:00 2027-02-19T17:00:00 PT80H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-5-3 25 1 0 7 26 1 0 7 29 29 C3.4 Pilot measurement at the pilot offices: bytes from peers, from the hub and from the office DP, for a month of deployments 4.6 2 2027-05-20T08:00:00 2027-06-16T17:00:00 PT160H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-5-4 27 1 0 7 28 1 0 7 22 1 0 7 30 30 CG3 Gate 3 — Pilot offices served from hubs and peers 4.7 2 2027-06-16T17:00:00 2027-06-16T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Criteria: Pilot offices' content served by the hub and peers, with the office DP in read-only fallback and serving under a threshold the endpoint lead sets; no deployment failure traced to content location; measurement report filed Source: ../books/guides/dp-consolidation-implementation.md#go-no-go 29 1 0 7 31 31 Phase 4 — Office waves 5 1

1

2027-06-02T08:00:00 2027-12-22T17:00:00 32 32 X-NG3 Pilot sites governed and evidenced on new transport (Network plan Gate 3) 5.1 2 2027-06-01T17:00:00 2027-06-01T17:00:00 PT0H0M0S 7 1 CISO (Network & Access Modernization plan) Owner or approver: CISO (Network & Access Modernization plan) If decided late: The pilot offices are still on their old circuits, and the first wave of DP retirements waits Source: network-access.md 4 2027-06-01T17:00:00 33 33 C4.1 Pilot wave: each office DP checked, drained, watched 30 days, removed with its site system; disks sanitized; inventory and SSP updated 5.2 2 2027-06-17T08:00:00 2027-07-07T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-6 30 1 0 7 32 1 0 7 34 34 D-C5 Wave plan: offices ordered by circuit readiness and renewal date 5.3 2 2027-06-16T17:00:00 2027-06-16T17:00:00 PT0H0M0S 7 1 Content delivery project lead Owner or approver: Content delivery project lead Options: By circuit readiness and renewal (the guide's order); by region (simpler, but waits on the slowest circuit in each) If decided late: Wave 2 can't be scheduled, and offices keep DPs they no longer need Source: ../books/guides/dp-consolidation-implementation.md#step-1-2 30 1 0 7 4 1 0 7 35 35 C4.2 Wave 2, about 25% of offices: boundary groups moved, peers enabled, office DPs read-only, then retired after 30 clean days 5.4 2 2027-07-08T08:00:00 2027-09-01T17:00:00 PT320H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-6 33 1 0 7 34 1 0 7 36 36 C4.3 Wave 3, about 60% of offices cumulative 5.5 2 2027-09-02T08:00:00 2027-10-27T17:00:00 PT320H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-6 35 1 0 7 37 37 C4.4 Wave 4, every remaining office, or a dated exception with its reason 5.6 2 2027-10-28T08:00:00 2027-12-22T17:00:00 PT320H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-6 36 1 0 7 38 38 CG4 Gate 4 — No branch distribution point left 5.7 2 2027-12-22T17:00:00 2027-12-22T17:00:00 PT0H0M0S 7 1 Executive sponsor and CIO Owner or approver: Executive sponsor and CIO Criteria: Every office DP retired or in the exception register with a date and reason; every retired server's media sanitized and its inventory and SSP entries closed; hub load per DP still under 80% of the published limit Source: ../books/guides/dp-consolidation-implementation.md#step-6-5 37 1 0 7 39 39 Phase 5 — Packaging on one standard 6 1

1

2027-01-25T08:00:00 2027-06-04T17:00:00 40 40 D-C6 Packaging standard 6.1 2 2027-01-22T17:00:00 2027-01-22T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Options: PSAppDeployToolkit as the standard wrapper, version pinned, for every app that isn't a clean MSI; vendor installers with Intune's PowerShell script installer only; a mix by app class If decided late: Repackaging can't start, and the client apps workload waits Source: ../books/guides/dp-consolidation-implementation.md#step-7 5 1 0 7 41 41 C5.1 Standard template: pinned toolkit version, signed scripts, one log path, exit codes mapped, detection rule pattern; held under change control 6.2 2 2027-01-25T08:00:00 2027-02-05T17:00:00 PT80H0M0S 7 0 Packaging team Owner or approver: Packaging team Source: ../books/guides/dp-consolidation-implementation.md#step-7-2 40 1 0 7 42 42 C5.2 Catalog rationalized: apps nobody installs retired, duplicate versions removed, an owner for every app kept 6.3 2 2027-01-25T08:00:00 2027-02-12T17:00:00 PT120H0M0S 7 0 Packaging team Owner or approver: Packaging team Source: ../books/guides/dp-consolidation-implementation.md#step-7-1 5 1 0 7 43 43 C5.3 Most-installed apps repackaged on the template; each tested from Configuration Manager and as an .intunewin from Intune 6.4 2 2027-02-15T08:00:00 2027-04-09T17:00:00 PT320H0M0S 7 0 Packaging team Owner or approver: Packaging team Source: ../books/guides/dp-consolidation-implementation.md#step-7-5 41 1 0 7 42 1 0 7 44 44 C5.4 Rest of the catalog repackaged or retired 6.5 2 2027-04-12T08:00:00 2027-06-04T17:00:00 PT320H0M0S 7 0 Packaging team Owner or approver: Packaging team Source: ../books/guides/dp-consolidation-implementation.md#step-7-5 43 1 0 7 45 45 CG5 Gate 5 — Catalog on the standard wrapper 6.6 2 2027-06-04T17:00:00 2027-06-04T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Criteria: Every kept app has an owner, a package on the template, a tested detection rule and a change record; the same package installs from either tool; retired apps removed from both Source: ../books/guides/dp-consolidation-implementation.md#step-7-1 44 1 0 7 46 46 Phase 6 — Content workloads to Intune 7 1

1

2027-02-15T08:00:00 2027-08-20T17:00:00 47 47 C6.1 Client apps and Office Click-to-Run apps workloads: Pilot Intune, then Intune; apps published as Win32 apps from the standard packages 7.1 2 2027-04-12T08:00:00 2027-05-07T17:00:00 PT160H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-8-1 43 1 0 7 26 1 0 7 48 48 C6.2 Configuration Manager required and available deployments withdrawn as each app moves; the count reported weekly 7.2 2 2027-06-07T08:00:00 2027-07-16T17:00:00 PT240H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-8-2 47 1 0 7 44 1 0 7 49 49 X-EG3 Workloads cut over, including Windows Update policies and device configuration (Endpoint plan Gate 3) 7.3 2 2027-07-30T17:00:00 2027-07-30T17:00:00 PT0H0M0S 7 1 Endpoint engineering (Endpoint & Device Modernization plan) Owner or approver: Endpoint engineering (Endpoint & Device Modernization plan) If decided late: Update content still comes from Configuration Manager, and retirement gate 2 can't close Source: endpoint-device.md 4 2027-07-30T17:00:00 50 50 C6.3 Configuration Manager software-update client setting turned off for every device on the Windows Update workload 7.4 2 2027-08-02T08:00:00 2027-08-06T17:00:00 PT40H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-8-3 49 1 0 7 51 51 X-E15 Intune-first intake with Autopilot registration (Endpoint plan E1.5) 7.5 2 2027-02-12T17:00:00 2027-02-12T17:00:00 PT0H0M0S 7 1 Endpoint engineering (Endpoint & Device Modernization plan) Owner or approver: Endpoint engineering (Endpoint & Device Modernization plan) If decided late: There's no Autopilot path to move bare-metal provisioning onto Source: endpoint-device.md 4 2027-02-12T17:00:00 52 52 D-C7 OS provisioning for existing devices 7.6 2 2027-02-12T17:00:00 2027-02-12T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Options: Windows Autopilot for every rebuild, with reset where it applies; keep task sequences for a named exception class on a hub DP until it can move If decided late: Imaging keeps a PXE distribution point alive, and retirement gate 3 stays open Source: ../books/guides/dp-consolidation-implementation.md#step-8-4 51 1 0 7 3 1 0 7 53 53 C6.4 Bare-metal provisioning moved from task sequences to Autopilot; PXE turned off on every DP 7.7 2 2027-02-15T08:00:00 2027-03-26T17:00:00 PT240H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-8-4 52 1 0 7 54 54 C6.5 Compliance and Endpoint Protection evidence sourced from Intune and Defender, not the Configuration Manager site database; ISSO confirms 7.8 2 2027-08-02T08:00:00 2027-08-20T17:00:00 PT120H0M0S 7 0 ISSO Owner or approver: ISSO Source: ../books/guides/dp-consolidation-implementation.md#step-8-5 49 1 0 7 55 55 Phase 7 — Connected Cache at the hubs 8 1

1

2027-05-06T08:00:00 2027-07-02T17:00:00 56 56 D-C8 Connected Cache form and placement 8.1 2 2027-05-05T17:00:00 2027-05-05T17:00:00 PT0H0M0S 7 1 Endpoint lead and ISSO Owner or approver: Endpoint lead and ISSO Options: Connected Cache for Enterprise and Education on its own host at each hub, its Azure resource placed in the boundary analysis; the Configuration Manager-integrated cache on a hub DP with no other roles (then retirement gate 4 binds it); none, where measured circuits carry cloud content If decided late: Cloud content keeps crossing every hub circuit, and gate 4 has no plan Source: ../books/guides/dp-consolidation-implementation.md#step-9 22 1 0 7 57 57 C7.1 Cache hosts built at the hubs on a supported OS, nothing else on port 80; Delivery Optimization pointed at each office's hub cache 8.2 2 2027-05-10T08:00:00 2027-06-11T17:00:00 PT200H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-9-1 56 1 0 7 47 1 0 7 58 58 C7.2 Cache hit rate measured; Win32 app, update and Microsoft 365 Apps content confirmed served from the hubs 8.3 2 2027-06-14T08:00:00 2027-06-25T17:00:00 PT80H0M0S 7 0 Endpoint engineering Owner or approver: Endpoint engineering Source: ../books/guides/dp-consolidation-implementation.md#step-9-2 57 1 0 7 59 59 C7.3 Connected Cache turned off on any DP hardware once the hub cache serves that office 8.4 2 2027-06-28T08:00:00 2027-07-02T17:00:00 PT40H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-9-3 58 1 0 7 60 60 Phase 8 — The five retirement gates 9 1

1

2027-03-29T08:00:00 2028-01-19T17:00:00 61 61 RG1 Retirement gate 1 — App content 9.1 2 2027-07-16T17:00:00 2027-07-16T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Criteria: Client apps and Office Click-to-Run workloads on Intune for the whole validated population, and no required or available deployment still published from Configuration Manager Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 48 1 0 7 62 62 RG2 Retirement gate 2 — Update content 9.2 2 2027-08-06T17:00:00 2027-08-06T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Criteria: Windows Update policies and device configuration workloads on Intune, and Configuration Manager's software-update client setting off for those devices Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 50 1 0 7 63 63 RG3 Retirement gate 3 — OS provisioning 9.3 2 2027-03-26T17:00:00 2027-03-26T17:00:00 PT0H0M0S 7 1 Endpoint lead Owner or approver: Endpoint lead Criteria: Bare-metal provisioning on Autopilot; no task sequence or PXE service still in use Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 53 1 0 7 64 64 RG4 Retirement gate 4 — Caching role 9.4 2 2027-07-02T17:00:00 2027-07-02T17:00:00 PT0H0M0S 7 1 Endpoint lead and ISSO Owner or approver: Endpoint lead and ISSO Criteria: No Connected Cache instance runs on distribution-point hardware, or none is needed on the measured circuits Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 59 1 0 7 65 65 RG5 Retirement gate 5 — Compliance evidence 9.5 2 2027-08-20T17:00:00 2027-08-20T17:00:00 PT0H0M0S 7 1 ISSO Owner or approver: ISSO Criteria: Compliance and Endpoint Protection reporting no longer cite the Configuration Manager site database as their evidence source Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 54 1 0 7 66 66 D-C9 Retire the hub distribution point tier 9.6 2 2027-12-22T17:00:00 2027-12-22T17:00:00 PT0H0M0S 7 1 Executive sponsor and CIO Owner or approver: Executive sponsor and CIO Options: Retire it in the week the last gate closes; keep it while any gate is open. Never on a date alone If decided late: Twenty-odd servers stay in the boundary to be patched, scanned and accredited for no workload Source: ../books/guides/dp-consolidation-implementation.md#step-10-1 61 1 0 7 62 1 0 7 63 1 0 7 64 1 0 7 65 1 0 7 38 1 0 7 45 1 0 7 67 67 C8.1 Hub and source DPs drained and removed with their site systems (Invoke-DpcOfficeRetirement.ps1 -GatesPath); media sanitized; inventory and SSP entries closed 9.7 2 2027-12-23T08:00:00 2028-01-12T17:00:00 PT120H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-10-2 66 1 0 7 68 68 C8.2 Cleanup: distribution point groups removed, boundary group site-system references cleared, peer cache client settings and deployments retired; no DP role left in the hierarchy 9.8 2 2028-01-13T08:00:00 2028-01-19T17:00:00 PT40H0M0S 7 0 Configuration Manager team Owner or approver: Configuration Manager team Source: ../books/guides/dp-consolidation-implementation.md#step-10-3 67 1 0 7 69 69 CG8 Gate 8 — Last distribution point retired, site roles cleaned up, evidence complete 9.9 2 2028-01-19T17:00:00 2028-01-19T17:00:00 PT0H0M0S 7 1 CISO and ISSO Owner or approver: CISO and ISSO Criteria: All five retirement gates closed in a gates run; no distribution point role left in Get-CMSiteRole; every DP's decommission record, sanitization record and SSP change filed; the content delivery evidence set in the guide's requirements table complete Source: ../books/guides/dp-consolidation-implementation.md#step-10-3 68 1 0 7 70 70 X-G3 Program G3 — Rollout Complete 9.10 2 2027-09-10T17:00:00 2027-09-10T17:00:00 PT0H0M0S 7 1 Executive sponsor and steering committee (program) Owner or approver: Executive sponsor and steering committee (program) Source: program-master-schedule.md 4 2027-09-10T17:00:00