...
| (1A) CU AD | (1B) CM client | CIT Central Patching | A&S Central Patching | Chemistry Central Patching | A la carte patching (CM) | A la carte patching: (GP) | A la carte installs (CM) | A la carte installs (GP) | |
|---|---|---|---|---|---|---|---|---|---|
| What service gets you or does: | Gets you CM client automatically (forced install) | Enables all other CM services, and depends on CU AD. | Patching ONLY if application already on system. A bundle. On CIT's schedule. | Patching ONLY if application already on system. A bundle. On A&S IT's schedule. | Patching ONLY if application already on system. | Patching ONLY if application already on system. | |||
| STATUS | Need? | Not exist: Need? Possible? | |||||||
| Pros of service: | Usernames are NetID and NetID passwords. Enables all other Chemistry IT management tools, including CM-related ones. | Enables other things, by default is passive. | |||||||
| Cons of service: | Enforced password strength. | Reports some hardware (applications?) data to CIT's servers (viewable by?) | Forced reboots | Our schedule | |||||
| How used in Chemistry It uses in supporting Research: | All supported Windows able to get on AD get this. | Thus, supported Windows able to get on AD get this. | Java patching | Java intalls. |
Patching schedule
CU's default
A&S IT's default
Chemestry research Option 1:
Chemestry research Option 1:
Why use CM patching for non-forced reboot?
NOT pre-download.
Yes: Points to CIT's patching. WUS server: MS and non-MS patching. Ex: Flash. 10-space for non-Proxied apps.
Snap-shot of a la carte patching targets:
...