Difference between revisions of "Helpful information to know"

From DCWiki
Jump to: navigation, search
(What to do when you get in)
(How to comment tickets)
Line 45: Line 45:
 
==How to comment tickets==
 
==How to comment tickets==
  
*Include more information than seems necessary.
+
*Include more information than you may think is necessary.
  
*Document scans starting and finishing, whether they found/removed anything. If a scan errors, include the error number/description.
+
*Document any scans starting and finishing, whether they found/removed anything. If a scan errors, include the error number/description.
  
*Include what you did and what you are doing. Include any specific settings or programs you used.
+
*Include what you did and what you are doing.
 +
 
 +
*Include any specific settings or programs you used.
  
 
*Update the ticket as soon as you do something.
 
*Update the ticket as soon as you do something.
  
*Before you leave make sure to go on and comment on anything you did.
+
*Before you leave at the end of your shift, make sure you have commented on anything you worked on or accepted.
  
 +
*Remember, the next person to work on the computer was probably not there with you and will not know what you did, what you determined or what should happen next. You need to let them know all of that information in the tickets.
  
 
==Phone Messages==
 
==Phone Messages==

Revision as of 16:16, 31 January 2019

Websites

Student Tickets: http://sta.hampshire.edu

IT Tickets: http://ittix.hampshire.edu

Logins / where to find passwords

The usual DC username is 'labrats'. The STA password can be found on the bottom of the printed staff list. (Take the first letter of each word!)

IT username on Windows computers is 'Administrator' and on Macs is 'Admin'. Ask Gavin or Rae if you need the IT Admin password.

Can't make your shift

Email the listserv at dc-sta@lists.hampshire.edu and ask if someone can cover your shift.

What to do when you get in

  1. Login to http://sta.hampshire.edu.
  2. Read through ALL of the open tickets.
  3. Check that all computers in the DC have a ticket and that all tickets have a computer.
    • If any computers are unaccounted for or a ticket doesn't accurately reflect a machine's status, post in the DC Slack channel. Include the user's name, the computer model, and the latest comment with a specific question for information.
  4. Continue working on as many computers as you can.
    • If you do anything to a computer make sure there is a comment saying what you did
    • If you don't know the next step for a certain machine, make sure you comment in the ticket that you're leaving it for the next person.
  5. If you have any questions feel free to ask Rae, Kate or in the DC channel in Slack.


When someone brings in a machine:

  1. Talk to them about their problem.
  2. Ask if the computer is under warranty.
    • If it is and the problem appears to be hardware related, direct them to one of the computer repair shops in the area.
  3. Have them fill out a blue Machine Ticket. Add your own notes if their description excludes things they told you.
  4. Take the user's computer (and power adapter, external HDD, etc.). Tell them that we will call and/or email them with updates.
  5. Input the ticket to the online ticket system, include a note if they leave a power adapter, external HDD, etc. (Be accurate!)
  6. Tape the ticket to the computer and print labels with their name for any cords, drives, adapters etc.
  7. If you have ideas, begin diagnostics (don't forget to comment the ticket!) and repair. Otherwise, note that you're leaving it for someone else.


  • If you have free time on your shift, clean up the counters, put tools away, wipe down the counters if dirty.

How to comment tickets

  • Include more information than you may think is necessary.
  • Document any scans starting and finishing, whether they found/removed anything. If a scan errors, include the error number/description.
  • Include what you did and what you are doing.
  • Include any specific settings or programs you used.
  • Update the ticket as soon as you do something.
  • Before you leave at the end of your shift, make sure you have commented on anything you worked on or accepted.
  • Remember, the next person to work on the computer was probably not there with you and will not know what you did, what you determined or what should happen next. You need to let them know all of that information in the tickets.

Phone Messages

Dial 9 then 1 then the area code to dial out

Always include the following in your voicemail messages:

  • Your name
  • Computer Diagnostic Center
  • We are open from 9am-5pm Monday-Friday

HDD formats: What do they mean?

NTFS (New Technology File System)

Developed by Microsoft for the Windows operating system.
Can be opened read-only by Mac file systems.
Most Linux systems (including Ubuntu) have read/write capabilities.

HFS+ (Hierarchical File System Plus)

Developed by Apple for the Macintosh operating system.
Windows systems can open a read-only version via Bootcamp.
Most Linux systems (including Ubuntu) have read/write capabilities for drives under 2 TB.

FAT32 (File Allocation Table)

Simple legacy filesystem.
4 GB file size limit without FAT+ extension.

ext4 (Fourth Extended File System)

Journaling file system for Linux. Developed as a successor for ext3 after initially a series of backwards compatible extensions for ext3.
Both Mac and Windows can usually open these read-only.

Others

exFAT
Patented file system developed by Microsoft for flash drives.
Windows systems have full capabilities.
Mac systems since 10.6.5 have read/write/verify/repair capabilities.
There is an open-source Linux kernel module that supports the reading of exFAT, however it can not become an official part of Linux due to the patent status of exFAT.


If you'd like to read about other types of file systems, go visit wikipedia.


Only work on as many computers as you can keep updated.