| Excerpt |
|---|
Motivations for, and barriers to, using Cornell's MS Configuration Manager (CM) more powerful tools and capabilities, such as application updating. Especially within Research. |
| Children Display | ||||||
|---|---|---|---|---|---|---|
|
See also
...
Resources
Interesting CM/Casper/Encryption stats CIT website
...
- CM on all Windows within CU AD is OK as long as nothing else is automatically done to those computers via CM simply because the are on CM. No MS patching, no Flexera, etc!
- See: CM -related servicesquestion/expectations/understandings
We can roll out CM within Research ONLY IF we have the option, per computer, to pick and choose CM capabilities to best meet that research computer's business need.
- KEY requirement: Do not force use of MS updates (OS, Office, etc.) on a computer simply to benefit from other CM services such as CM SCEP or CM Firefox.
- Many research computers, especially those attached to instruments, must only be updated and restarted by the user, and not forced on them.
- See: CM -related servicesquestion/expectations/understandings
Table tracking concerns, questions, and progress
...