...
- Self-supported computer: A computer not set-up by Chemistry IT. It cannot be on AD so it cannot be managed using Cornell's tools.
- IT-supported computer: A computer set-up and configured by Chemistry IT. It's on AD. May or may not be IT-managed.
- IT-patchedpartially-forced-rebootmanaged computer: An IT-supported computer also managed using Cornell's management tools, including Cornell-managed OS patching.
- System may For systems which cannot be forced rebooted.
- No forced rebooting, so Group member must invoke patching. If not once per month, must be documented as such.
- IT-patched-not-forced-rebootfully-managedcomputer: Default standard. An IT-supported computer also managed using Cornell's management tools, including Cornell-managed OS patching.
- For systems which cannot be forced rebooted.
- No forced rebooting, so Group member must invoke patching.
- Group-patched computer: A IT-supported computer the group pledges to patch on a regular schedule, including required restarts.
- For systems which cannot be forced rebooted. No forced rebooting, so Group member must invoke patching.
Patching behavior
| Service name | Windows OS patched | Forced reboot? | When? | Common MS apps patched | Common non-MS apps patched |
|---|---|---|---|---|---|
| A&S Central Patching | Yes | Yes | Thursday, 4pm, once per month. This Thursday is following Tuesday patch deployment by A&S IT, which is the Tuesday a week after "MS Patch Tuesday", which itself is once per month (2nd Tuesday of the month?). Except when MS skips or retracts patches in time. | Yes. List? | Some. List? |
| Researchers' needs: | Yes | No | When research group can, hopefully sooner than later. | Yes. List? | (Same as above) |
...