Tag Archives: appointments

CN Appointments and Service Desk Staff Schedule

Please read for some important updates on appointment scheduling and staff mentoring schedules.

If you are scheduling an appointment for another person, the following people have time available for Spring term:

  • Ken Howard
  • Steven Tom
  • Robin Castle
  • Jeff Bonnichsen
  • Max Schmidt
  • Zach Colbert
  • Vu Le
  • Mack Powers

As before, only schedule them during their available times. In particular, please be careful to only schedule student techs during times their calendars show as available for appointments.

If an on-site visit is needed in an emergency, please check in with Max Cohen or a call mentor to see if you can go on-site to assist the customer. If we have sufficient coverage for calls and walk-up at that time, and you are sufficiently trained to address that type of issue, we can accommodate emergency on-site visits in this way.

Steven Tom is helping to prepare more back-packs with supplies for on-site visits.

The Service Desk mentoring schedule for Spring term is as follows:

  • Walkup Mentor
    • 8:00-12:00 Jeff
    • 12:00-1:00 Keenan
    • 1:00-5:00 Pat
    • Backups: Keenan, David
  • Call Mentor
    • 8:00-12:00 Nephele, Robin
    • 12:00-1:00 Nephele
    • 1:00-5:00 Ken, Steven
  • Builds Mentor
    • 8:00-1:00 David
    • 2:00-5:00 Nephele
  • CN Accounts
    • 8:00-12:00 Keenan, Pat
    • 2:00-5:00 David, Keenan
  • CN Scheduled Appointments
    • 8:30-12:00 Ken, Steven
    • 1:00-4:30 Jeff, Robin

The basic responsibilities for the staff roles are defined in the Service Desk guide here: https://oregonstate.teamdynamix.com/TDClient/KB/ArticleDet?ID=23358#12.0


Scheduling Computer Placements

Due to feedback from customers that a 90 minute appointment is too long for them, and from technicians that most placements do not take 90 minutes, we have made the following changes:

  • In Interview, the default appointment placement length is now 60 minutes.
  • The technician who does the interview may specify a different appointment length as needed. (See On Campus Interviews.)
  • The email response template notifying customers that they need to call us to schedule their placement no longer says how long the appointment will be. We can discuss that with them on the phone when scheduling the appointment.

If customers balk at a long appointment time, we can tell them that they really only need to be available for the first 30 minutes, but the technician may need longer to complete their setup. In such cases, we may miss some items, so it is preferable that they are available for the entire appointment. However, we can work around their schedule as needed.

Upcoming Change to note:

Many placements are pre-scheduled at the time we pick up the computer and do the interview, typically for 5 business days out. However, pre-scheduling the placement is not always possible. In the near future, BuildTracker/Interview will be updated to indicate the reason a placement was NOT pre-scheduled.

Example reasons to NOT pre-schedule placement include:

  • Extension customer (computer is shipped to them by Lisa Gillis, or picked up from Milne instead).
  • End-user not available to schedule placement.
  • Hardware issues may delay rebuild/repair.
  • Malware issues may delay rebuild/repair.

Service Desk Digest 5/16/2017

Student Meeting on 5/18

Most of you are scheduled to attend a mandatory meeting this Thursday from 5PM-7PM. We will record the meeting so that anyone who is not able to attend can catch up later. Food will be included (pizza).

The agenda so far includes the following:

  • Richard Turk – Computer lab support overview
  • Chris Evans – Beaverprint overview and troubleshooting
  • Nathan Power – Citrix XenApp overview and troubleshooting
  • Jason Appah – Exchange troubleshooting and road map
  • Josh Crowl – Wireless network troubleshooting
  • Andrew Wheeler – IS and Client Services strategic plan and direction
  • Max Cohen – Time off and scheduling procedures
  • Kirsten/Max/Andrew – OSU-Cascades tier 1 support
  • Jeff Bonnichsen – Reminders about ticket updates, professionalism
  • Kirsten/Max – Congratulations to graduating students

Appointment Ticket Troubles

Pat has been reviewing all on-site appointments and has been seeing the following issues repeatedly. Please make sure you are following proper process when creating appointments:

  • Ticket type still set to service desk / intake. This should be set to the type appropriate for the appointment.
  • Responsible not set for field technician. Responsible needs to be set so on-site techs can find their tickets.
  • Calendar notes field void of ticket # or ticket URL. On-site techs need these details so they can prepare for appointments.
  • Requested placement time (length) doesn’t match calendar appointment length. This can lead to problems with overbooking. Please pay attention to the placement time notes in the ticket.

Steps to create an appointment are outlined here. If you need a refresher, please talk to Pat or Robin.

LAN Party Finals Week

The next LAN party will be Friday, June 16 at 6:00PM in the Milne Computer Lab.

If you would like to contribute towards pizza, please see Kirsten.

If you have questions about what games we will be playing or what tech to bring, talk to Thomas.

Security Items

If you are not familiar with common strategies for account phishing and identity theft, please read up. I will provide some training materials shortly.

We have had a handful of incidents recently where a Service Desk technician gave really bad advice to a customer. Please be aware of the following common issues:

  • Tech Support Scam. A customer is directed to call a support number due to vague “security problems” on their computer. The person on the call wants to remote into their computer and install software. THIS IS A SCAM. They may be attempting to compromise the person’s computer, gain access to their data, or encrypt their data in a ransomware attack. If a customer asks about an attack like this, tell them it is likely malicious, and not to call the number. If they allowed someone to remote into their machine, help them check for malware. If they are a CN customer, make sure to ask first if they handle PII (Personally Identifiable Information) such as credit card numbers or social security numbers.
  • Account Phishing. If a customer has received an email telling them their account is going to be deactivated unless they take some action, help them review the email. If it does not look like a notice from the ONID system, and/or directs them to a website that is not at OSU, it is most likely a PHISHING ATTEMPT where an attacker attempts to gain access to their account, usually to send spam and more phishing email.  A good technique is to mouse over any links in the email and wait for the URL to pop-up – it is is not an oregonstate.edu URL, they should not click on it. This is a good technique to train customers on.
  • If Unsure, Change the Password. As our CIO Lois Brooks said, if someone is asking whether they should maybe change their password, we should tell them to change their password. If a customer has clicked on a suspicious link and then provided their username and password, help them IMMEDIATELY CHANGE THEIR PASSWORD.  Please also ask them for details about the phishing attack and record that in the ticket. Notify ONID Support of the potential compromise so they can check the account to see if there is any suspicious activity such as open connections from another country.

Client Services Code Moved to GitHub Enterprise

Our code repositories are moving (have moved?) to an IS-wide GitHub Enterprise account. If you have questions, please ask in #sd-development on Slack.

Restricted Groups in Active Directory

For some groups we manage for CN customers, the customers have indicated they do not want us to make any membership changes without explicit approval from the group owner. In the past, we have had a few issues were we made changes to these groups anyway, without the customers’ permission.

To avoid this problem, the naming convention for these restricted groups has been changed to: RESTRICTED-Name-RESTRICTED

If you are asked to make a change to a group with this naming convention, please check the notes on the object. If you are unsure what to do, please check in with a full-time staff member.

Out-of-Order in the Computer Labs

If an item in one of the computer labs is out of order, please do the following:

  • Post an “Out of order” sign
  • UNPLUG THE DEVICE (otherwise helpful customers will turn it back on)
  • Make a ticket with Responsible set to Campus Labs
  • If urgent, post in #is-campus-labs on Slack for assistance