UNSW   Faculty of Engineering myCSEPRINT VERSIONSITE MAP  
cse | School of Computer Science and Engineering (CRICOS Provider No. 00098G)
    #About CSE     #Undergraduate Study     #Postgraduate Study     #Timetables & Courses     #Research & Publications     #People & Work Units     #Help & Resources     #News & Events     #High School Portal

Last updated 29.06.09

System Support

Who we are

System Support is a small team of sysadmins and support staff, a subset of the Computing Support Group here at CSE.

As some of SS staff work part-time, the staff on duty at any given time will vary, but our current crew consists of:

What we do

We focus on two major roles: Day-to-day monitoring and maintenance of the CSE computing infrastructure, and providing technical support for staff and postgraduate students.

We also provide support for undergraduate students, but only in cases where the CSE Helpdesk has escalated the call to us.

We handle any and all problems with CSE computing services, and also allocate print/internet quota, create and configure accounts/classes/groups, restore backups, manage the mail subsystem, build and configure new machines, and do pretty much anything else that needs doing in this general field.

Requests mailed to SS are placed on a mail queue, and should be answered within a day or so (though not necessarily in the order that they are received). Mails that are not answered in a short time are flagged for attention, and are guaranteed not to fall through the cracks.

Opening Hours: System Support operates from 9am - 5pm on weekdays. For assistance outside of these hours, please refer to the emergencies section.

What else we do

Since August 2005, System Support staff also help provide face-to-face support at the CSE Helpdesk. Information on its operations are detailed on its web page.

What we don't do

With all of the maintenance and support tasks we are responsible for, there are some tasks that we must give extremely low priority. Such tasks include:

  • Help with programming problems
  • Use or configuration of non-CSG-maintained software, beyond a very basic level
  • Configuration or troubleshooting of non-CSG-maintained machines, beyond a very basic level

This is not to say that we won't take a quick look at pretty much anyting that comes our way (except outright help with assignments, etc. for obvious reasons), but just an acknowledgement that we cannot devote serious amounts of time to problems that lie outside of our domain.

How to contact us

The primary means of contact with System Support is via email. Wherever possible, all problems, questions or requests should be sent to ss@cse.unsw.edu.au, so that they can be tracked and replied to in a timely manner.

Alternatively, urgent matters (or situations where email is not possible) can be dealt with over the phone, on extension 54199, or external phone (02) 9385 4199. You will likely be asked to forward any relevant details or even just a summary of the issue by email anyway, where possible.

When neither of the above is possible, you can visit the SS area in room K17-111, situated behind the lifts on the first floor of the K17 building (take the right-hand hallway as you face the lifts).

Once again, however, we stress that due to the high probability that we'll be fixing urgent problems at any given time, we cannot always provide prompt attention to phone calls or in-person visits, so email really is your best option in all cases.

Emergency Out of Hours Assistance

A situation may be considered an emergency if it concerns many members of the school or stands to impede the work of several students. Before calling for assistance out of hours please consider that there is a cost to the school for every call out.

After hours assistance is generally provided between 5pm and 9pm weekdays and between 9am and 5pm during weekends all year.

Out of hours contact can be made with e-mail to csg-alert. This address is usually used by our helpdesk. This service sends a message to the CSG pagers as well as an e-mail. You can include detail in a message to csg-alert in the e-mail body, remember to put a brief description and your phone number in the subject line. The thing to remember with csg-alert is that this will only work if the CSE e-mail server is working.

Help us help you

Policy issues

Both the school and the Computing Support Group have a number of policies in place regarding requests sent to SS, and proactively complying with these policies will result in faster, more efficient results for you.
  • Ask your supervisor (if you have one)

    Requests for resources (such as print/IP/disk quota) or for new accounts or classes, addition to groups, or other privileges, must generally be endorsed by your supervisor or lecturer, where applicable. (If you are a lecturer or supervisor yourself, then you needn't worry about this, of course.) Don't send or CC these requests to SS, as we will only bounce them back stating that we need endorsement. Instead, mail them to your supervisor, and ask them to forward the mail to us with their approval.

  • Send mail from your CSE account wherever possible

    Requests that have security implications (such as registering wireless MACs to your account, requesting CD keys for software, resetting your password, etc.) must be sent either from your account on a CSG-maintained machine, or using SMTP authentication. Basically, if sending the mail didn't require the use of your password at any stage, then we can't be sure the request is actually from you and not an imposter, and so we can't carry it out. (this is actually a GOOD thing...)

Provide enough information

One of the most common causes of "email tag" in our daily routine is insufficient information as to the nature of the problem. Please ensure that wherever possible you always provide as much relevant information as you can, such as:
  • Your CSE username (and alternate contact details, if it's an email-related problem)
  • Exactly what you were trying to achieve
  • Which machine you are/were using
  • Exactly what commands or actions you performed
  • What you expected to happen
  • What actually happened
  • The (preferably exact) text of any error messages you encountered
  • Any steps you've taken to try and isolate/identify the problem, and any conclusions you've reached

If you can include the contents of your Xterm session where you encountered the problem, so much the better.

Useful links

Top Of Page

 ###
Site maintained by webmistress@cse.unsw.edu.au
Please read the UNSW Copyright & Disclaimer Statement