*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
- Pertinent Incident Numbers:
- INC000001186777 Physics Instruct - Met with Alan G. (Aug. 2, 2014)
- INC000001709453 Physics Instruct - Image Testing computer hard drives "just in case". (June 30 - July 7, 2016)
- INC000001883883 Physics Instruct - Testing Ctr increase robustness (Feb. 10, 2017)
- Primarily to ensure Physics IT staff image the hard drives sooner than later.
- P123. A OneNote page started. Of any value beyond what we put here, in the wiki?
Status and next steps
2017-03-09
Imaged systems now contained within an encrypted file, placed on a thumb drive, to give to Craig for safe-keeping.
Was: 2/10/17: Image all three systems in case of hard drive failure. Might protect against other likelihoods, too.
- KEY STEP: Carefully document where (storage device) with images are stored.
- Consider: Test restore of image to new hardware to see outcome. Will that work? (Alas, still Win7 not Win10. Still FM Pro v11, not v15.)
2017-03-01
Request from Craig for recommended action.
2017-02-23
Discovered that Brightworks is not available to do this work. (Was: 2/15/17, Oliver contacted Brightworks to see if they might be engaged with this work: Ticket#95300/Physics Testing Center, ensuring robustness in its setup.)
2017-02-10
Oliver and Nick Taylor <nwt2> created this list following failing TC1 this week.
High-level recommendations
Recreate current system on 3 new computers with current operating system and versions of applications.
- Contemporary software ensures longer-term support.
- Contemporary operating system ensures easier use of new hardware.
- Successfully recreating system ensures complete understanding of system, enabling correcting problems or improving the system more quickly and with less risk.
Current system generally works well so serves as a good model. There may be desired changes. Recommended strategy is to recreate current system and use that learning to inform possible improvements. Ideas for improvements:
Improve FMPro scripts (if I understood Nick's idea correctly).
Have FMPro DB run on a dedicated system such that the two scanning systems are then identical to each other, making them even easier to support.
Next steps
Nick Taylor Nick Taylor (Testing Lab) to do:
Tech-related work (in priority order)
...
- Establish clear procedures for staff to follow if a particular computer or printer is not working.
- Question Nick was going to discuss with Alan: Is it worth have a weekly "snapshot" on a USB drive in Alan's office, which would be more "off site"? Worth the added risk?
Status reports
2017-03-09
Imaged systems now contained within an encrypted file, placed on a thumb drive, to give to Craig for safe-keeping.
Was: 2/10/17: Image all three systems in case of hard drive failure. Might protect against other likelihoods, too.
- KEY STEP: Carefully document where (storage device) with images are stored.
- Consider: Test restore of image to new hardware to see outcome. Will that work? (Alas, still Win7 not Win10. Still FM Pro v11, not v15.)
2017-03-01
Request from Craig for recommended action.
2017-02-23
Discovered that Brightworks is not available to do this work. (Was: 2/15/17, Oliver contacted Brightworks to see if they might be engaged with this work: Ticket#95300/Physics Testing Center, ensuring robustness in its setup.)
2017-02-10
Oliver and Nick Taylor <nwt2> created to-do lists following failing TC1 this week. Either in "Next steps" or "Status reports" (both, above), depending on completion level.
Past "Next steps"
8/27/15
- Completed 7/7/2016, all 2 systems, INC000001709453. Was:
- To do: Image TC-01 and TC-02 to files. When shall we do this, this semester? Alan had discussed maybe removing grade info before doing this.
- Not completed:
- To do: Get file synchronization to work. (What I said last time: I think I'm close to getting that to work across all 3 systems, so we'll see if I'm accurate on that count.)
...