## Chapter 19 — End of servicing is not today's pass ### Lesson map Lesson 19. Map, example, EX065. ```mermaid flowchart TD T["Today's later reading: 12 of 12"] --> N["A predicate can still pass today"] E["Vendor servicing ends later"] --> F["updates<=14d fails on every later month"] F --> B["Replacement is a trustee decision"] M["A management service"] --> U["Not deployed; fleet is still twelve"] ``` A future failure of the update predicate is not a failure of today's conjunction. ### Logical drawing ```text FB07 at the first run four zeros and a lock bit of 1 remaining items replace the oldest laptop consider a free management service if the fleet grows past twelve not printed an end-of-servicing date a Windows version a product name for the service ``` ### Learning outcomes After this chapter, you should be able to: 1. Explain why the end of vendor servicing defeats the update predicate regardless of effort. 2. Keep `FB07` as the kind of device in that note without back-dating a version. 3. Leave the management service undeployed. ### 19.1 A lifecycle limit sits outside the checklist's effort. Chapter 4 leaves two items for the trustees. One is replacing the oldest laptop, which will soon stop receiving updates. The other is considering a free device-management service if the food bank grows beyond twelve laptops. `FB07` is named as the kind of device the first item covers: at the start it failed four of the five checks and passed only the screen lock. Once that laptop stops receiving updates, `updates<=14d` fails on every later monthly run, whatever Leah does with the checklist. The failure will be a vendor lifecycle fact, not evidence that the routine was skipped. No end date is printed. No Windows version is printed. A reader cannot honestly write a year, a build number, or a product edition. Nappa and colleagues showed that shared code can delay patching across products. The citation supports a limit: "updates are current" on the operating system is not a survey of every library inside every application. The food bank has no component inventory and no vulnerability identifiers. Do not copy a rate from that paper into Fenwick's note. The browser and the PDF reader remain the only additional software chapter 1 names, and neither has a version here. The management service is the second remaining item, and it is not in use. Chapter 2 says twelve laptops do not justify a management system yet. Chapter 4 does not say the fleet grew. The printed checklist is still the method. Enrolling the laptops in a product, naming that product, or claiming a remote compliance percentage would close an item the trustees have only been asked to consider. Today's later reading of 12 of 12, if the prose is believed on its own terms, still does not make `FB07`'s hardware new, and it does not record Secure Boot, a firmware measurement, or a management enrollment. Replacement stays a budget decision. The quick check cannot spend the money. ### 19.2 Worked example | Statement | Time it belongs to | Decision | |---|---|---| | "FB07 failed four checks at the start and passed the lock." | First matrix | May stay | | "When servicing ends, the update bit fails every month." | Future, undated | May stay as a limit | | "Servicing ends in March." | No date is printed | Refuse | | "The management service already covers twelve laptops." | It is not deployed | Refuse | > **Synthetic case.** No Windows version and no product name are added. ### Errors and limits A pass today on `updates<=14d` is silent about a lifecycle date the file never stored. ### Apply - **EX065 — Today or later?** FB07 is the kind of laptop that will fail the update check after servicing ends. A classmate prints a Windows version, an end date, and a deployed management service. What remains true? *Rubric:* 3 = FB07's first-run pattern stays four failures plus the lock; the end of servicing stays undated and without a version; the management service stays a consideration for a fleet still at twelve; 12 of 12 does not enroll a device or renew the hardware;; 2 = the date and the product stay unprinted;; 1 = one item;; 0 = none. ### Continue studying — lesson 19 (chapter 19 of 20) [← Chapter 18](#ch-18) · [Course chapter index](../SUBJECTS.md) · [Chapter 20 →](#ch-20) Continue to the next authored lesson. ## Worked answers **EX065.** FB07's first run stays four failures plus the lock. Servicing stays undated and without a version. The management service stays undeployed on a fleet of twelve. Today's pass does not renew the hardware.