| Excerpt |
|---|
What services can PhysIT provide to Nick which he would value, and without getting in Nick's way? |
- Nick Szabo Jr <ns53>
Summary
In Nick's area, ChemIT PhysIT is responsible for IT support for:
...
Nick is responsible for everything else, including his own work office computer, the USB printer at the MatLab computers, and the instrument computers.
Details
Networking and phones
PhysIT provides technical and administrative support (coordinated with Nancy Searles in Physics) for all Cornell CIT networking and telephones in the area, with the exception of the Nick's office computer.
For Nick's office computer, he will administer the IP connections directly with CIT (AccessNet). Even for Nick's office computer, if networking or telephone service is not working, he will contact PhysIT, who shall determine the cause of the problem and request assistance from CIT Network and Communication Services (NCS) as necessary.
Active Directory ( a.k.a "The Domain" )
PhysIT, as part of our standard management, attaches computers to the Cornell Active Directory service provided by CIT. Computers are placed in the Arts and Sciences Division, Physics Department Subdivision. As a a result of this, names for computers and user accounts can be somewhat limited (per CIT's requirements as part of managing this shared campus resource).
Nick's office computers computer will not be connected to the centralized management/Cornell Active Directory services PhysIT uses, and as such will not gain from centralized management . While it shall not be on the Cornell Active Directory, Nick will keep PhysIT uses. Also, Nick's computer will not have an administrative account on the computer for PhysIT's use.
The specific networked devices
Specific computer(s) | IT support from PhysIT | IT support from Nick | Network, with notes | Other info | |||||
|---|---|---|---|---|---|---|---|---|---|
2 Library computers | Convert to public stand-up, lab kiosks. Continue running Win7. | Nick has Admin access to make changes directly, and is responsible for changes made. | Physics Admin | NO Deep Freeze (software used to prevent persistent changes made by user, often used for kiosks to make them more robust.) | |||||
2 MatLab computers | Convert to public stand-up, lab kiosks with MatLab, running Win7 (not WinXP) | Nick has Admin access to make changes directly, and is responsible for changes made. | Physics Admin | NO Deep Freeze (software used to prevent persistent changes made by user, often used for kiosks to make them more robust.) | |||||
1 Faculty room computer | Convert to a PhysIT staff computer. | Nick has Admin access to make changes directly, and is responsible for changes made. | Physics Admin | For faculty use, gated by physical and social means, not technical. | |||||
Printer in Library (networked, laser) | Primary support, including: Configuration and troubleshooting. | Determine when operational needs or hassles warrant replacing the printer. | Physics Admin | No improvements desired. | |||||
Nick's office computer | With On Nick's invitationrequest, we can recommend replacement hardware, procure hardware, initially set up OS and default applications, as PhyIT's schedule permits. PhysIT doing these things can save Nick time and aggravation. | Primary support, including: Initial image and configuration, troubleshooting, upgrading software, and restoration. Responsible for following IT policies in configuration and use. | AccessNet | To-do, PhysIT: Revert the recently purchased computer away from PhysIT's image. | |||||
Printer in Library (networked, laser) | Primary support, including: Configuration and troubleshooting. | Determine when operational needs or hassles warrant replacing the printer. | Physics Admin | No improvements desired. | Printer at MatLab station (USB, inkjet) | With On Nick's invitationrequest, we can recommend replacement hardware, procure hardware, , as PhyIT's schedule permits. PhysIT doing these things can save Nick time and aggravation. | Primary support, including: Configuration and troubleshooting. | n/a | No improvements desired |
Anything else in the lab, not listed above | n/a | All Nick :-) primary support provided by Nick. |
|
|
Notes
Notes
A few best practices include:
- All Daily use of computers a computer is always at the user-level, not as an Admin.
- Use the Admin account to elevate privileges within the user account or to temporarily login log in as Admin to make the necessary changes.
- Don't establish network shares.
- There are many, better options.
Helpful links
Spring 2014: Nick moved from his old wiki <http://pages.physics.cornell.edu/p510/>, which had been hosted by folks running the Physics Linux lab.