You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Ideas and choices related to provisioning IT support for Lou Hand to meet his needs cost-effectively.

Summary

Option 1 (presumed preferred):

PhysIT is responsible for IT support for Lou Hand's single, primary computer.

  • (Any printers, especially if networked?)

Lou Hand is responsible for IT support of peripherals, and mobile devices, and any additional computers.

Option 2:

Lou Hand is responsible for IT support for his own primary computer and all other technology devices.

Details

Networking and phones

For either Option 1 or Option 2, above:

PhysIT provides technical and administrative support (coordinated with Nancy Searles in Physics) for all Cornell CIT networking and telephones in Lou's office.

Management tools, including Active Directory ( a.k.a "The Domain" )

If Option 1, above:

PhysIT will configure computer's anti-virus software to report to PhysIT's anti-virus console.

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).

This change would occur if PhysIT must re-do the computer's OS, or if that computer is replaced with another computer.

If Option 2, above:

Lou's computer will not be connected to the centralized management/Cornell Active Directory services, and as such will not gain from centralized management PhysIT uses. Also, Nick's computer will not have an administrative account for PhysIT's use.

The specific networked devices

Specific computer(s)

IT support from PhysIT

IT support from Lou

Network, with notes

Other info

Option 1

Continue running MacOS 10.8, "as is", until computer has a problem not readily resolved without a clean install.
Clean install by PhysIT.
Primary support, including: Initial image and configuration, troubleshooting, upgrading software, and reimaging if broken.
Responsible for following IT policies in configuration.

Nick has Admin access to make changes directly, and is responsible for changes made.
If ChemIT reimages the computer (with Nick's approval), Nick can either let us know of his changes, or he can re-do them if they are still necessary.

Physics Admin
ChemIT registers devices

NO Deep Freeze (software used to prevent persistent changes made by user, often used for kiosks to make them more robust.)

Improvements desired:
Auto-login.

Option 2

On Nick's request, we can recommend replacement hardware, procure hardware, initially set up OS and default applications, as PhyIT's schedule permits.

Primary support, including: Initial image and configuration, troubleshooting, upgrading software, and restoration. Responsible for following IT policies in configuration and use.

AccessNet
Annual registration by Lou

NO Deep Freeze (software used to prevent persistent changes made by user, often used for kiosks to make them more robust.)

Floppy drive must be available.

Improvements desired:
Auto-login.
Contemporary OS, matching Library computers
Able to print to Library printer

Any networked printer?

Convert to a PhysIT staff computer.
Users login to their own account using their own NetIT credentials, providing them User-level access.
Primary support, including: Initial image and configuration, troubleshooting, upgrading software, and restoration.
Responsible for following IT policies in configuration.

Nick has Admin access to make changes directly, and is responsible for changes made.
If ChemIT reimages the computer, Nick can either let us know of his changes, or he can re-do them if they are still necessary.

Physics Admin
ChemIT registers devices

For faculty use, gated by physical and social means, not technical.
Improvements desired?

Notes

A few best practices include:

  • All use of computers is at the user-level, not as Admin.
    • Use Admin account to elevate privileges within the user account or to temporarily login as Admin to make the necessary changes.
  • Don't establish network shares.
  • No labels