Kirsten and I made some changes to the Ticket type and Form names. This is to make the process of selecting a Form easier.
Details on the changes are below.
- Inactivated (ticket type and form)
- Ticket type and form “Computer Build/Rebuild (personal device” inactive
- Ticket type and form “Malware response (personal device)” inactive
- Renamed (ticket type and form)
- “Device support (pc, phone, tablet, etc.)” –>”Personal Device Support”;
- “Computer Build/Rebuild (OSU device)” –>”CN Build/Rebuild”;
- “Campus Labs Support” –>”Campus Labs”
- “Device recommendation/purchase” -> “CN Recommendation/Purchase”; limited form and type to only those groups that need it
- “Malware response (OSU device)” -> “CN Malware Response”
- “Printer support” -> “CN Printer Support”
- “Surplus” -> “CN Surplus”
- Created new type: “CN Device Support”
The new form names and types going forward are:
- CN Build/Rebuild
- Campus Labs
- CN Recommendation/Purchase
- CN Malware response
- CN Printer Support
- CN Device support
- Personal Device Support
If you have any feedback, please let Kirsten Petersen and Lucas Friedrichsen know.
In the past month or so, we have had three headsets in the call center break. The connector between the earpiece and the headband is fragile plastic, and takes a beating when we remove the headbands frequently to re-cradle the earpiece.
Some of these headsets were quite old (5+ years?) and I think this is probably a design flaw. I have ordered 6 new headsets; most of these have arrived and a couple are still on their way.
I will be evaluating some alternative headsets to see if we can get something a bit tougher. For now, please be gentle with the headsets, particularly when you are removing the earpiece from the headband.
Referral Tool will be unavailable on Friday June 30th, from 5:15-5:45pm.
The older Referral Tool 1, https://tool.is.oregonstate.edu/reftool, is being turned off.
Referral Tool 2, https://tools.is.oregonstate.edu/reftool2, will continue to work. That URL will also be redirected.
After the change, the newer version will be located at – https://tools.is.oregonstate.edu/reftool
Backend, there is also a Cyder entry change to facilitate moving to a new VM.
Friday June 30th, 5:15-5:45pm.
Reduce the number of tools in use and consolidate the tools onto a newer production VM.
If you have any problems accessing RefTool2, please e-mail firstname.lastname@example.org
The Enterprise Computing Services – Operations group handles Banner access requests. ECS is now part of TeamDynamix and tasks/tickets can be escalated to them.
Escalations about Banner access and account issues were previously handled by sending an email to email@example.com. That email address no longer works for escalations.
To escalate a Banner account/access issue:
- Create the initial ticket and assign it to Service Desk.
- Create a task from the ticket with pertinent details.
- Assign task responsibility to Enterprise Comp Svcs – Ops.
- Set the initial ticket to Escalated – Internal, and the Goes Off Hold date for 3 days out.
Please note that this change is specifically for access/account issues; other Banner issues are still escalated by emailing ACT_Support@lists.oregonstate.edu.
The infosheet about the Banner service has been updated to reflect that change.
A status was added today to the “IT” application called “Closed as junk” to facilitate closing tickets faster that are SPAM.
Documentation about methods to close those tickets, including a bulk method is here:
It is a generally a bad idea for us to do a CN build for computers that came from OSU Surplus.
If a customer asks about this, please advise them that surplus computers are often too old to be set up with modern operating systems and software. Also, even if a surplus computer is not that old, it may have been sent to surplus because it has other reliability issues.
If a customer is adamant about having a surplus computer built as a CN device, please make a ticket and assign it to “Service Desk – Managers”. Let them know a member of the management team will get back to them.
Note: this notice applies to university-owned CN devices, not personally-owned devices. Also, I am not talking about “trickle-down” computers that came from another person or department. I am just talking about a computer that went to OSU surplus, and then was bought by a CN-supported department to be re-used as a CN machine.
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.
The Operations group in Enterprise Computing Services has been on-boarded to TD.
- You can reassign tickets to the group.
- You can assign tasks to the group.
The Operations Group handles:
- Tape backup processing
- AppWorx job scheduling and changes
- Banner, Nolij and DataWarehouse access requests
Current intake e-mail addresses:
Information about the operations group can be found here –
It’s time for the Spring 2017 LAN party. Please join us this Friday night for PC games, console games and tabletop – or just to hang out with your fellow IT folks.
When: Friday, June 16, 5PM-Midnight (you don’t have to go home but you can’t stay here)
Where: Milne basement
There will be a PS4 console and Rock Band. Feel free to bring games and additional controllers.
Some of the lab computers will be loaded with Steam.
If you prefer to bring your own computer: we can provide keyboards and mice, but you should bring your own monitor and headphones.
There is room for table top. Bring a game you want to play!
We encourage everyone to bring snacks and (non-alcoholic) drinks.
Pizza will be provided at 6:30 PM. Donations of money towards pizza are appreciated – please see Kirsten before Friday afternoon if you wish to donate.