Category Archives: Bench

Base, Bench, Community Network, Field

Updates to Build Tracker

Leave a comment

Good Evening Colleagues,

I have recently added some features to Build Tracker and they are now live.

Features:

  • Build Location now displays relevant locations
  • TDx Asset information retrieval
  • Minor updates to instructions

Build Location:

Prior to this update, the “Build Location” column in the list of was rarely filled in, and quite frankly, not helpful. Now that builds are scattered around across multiple rooms, I feel it’s especially important to be able to keep better tabs on where each build is. With this update, you’ll be able to set your desk location as the location of the build. These desk locations pull directly from Teamdynamix, so any changes to those in the future should be reflected in Build Tracker.

To set a specific location, set “Build Location” to “Technician Desk”, and the “Specific Location” dropdown will appear. Then simply select your desk and click save. This will update the entry in Build Tracker as well as update the Teamdynamix Ticket.

Asset Retrieval:

In our transition from Inventory to Teamdynamix Assets, I have implemented a button in Build Tracker Interviews that will retrieve Asset information. It works identically as retrieving Inventory data, albeit slightly slower in response.

Thank you, and let me know if you have any questions.

Base, Bench, Community Network, Field

ISCS-MDT moved to new core

Leave a comment

The ISCS-MDT server (used for Windows deployments at the build bench) has been moved to new core and to the same VLAN as the build bench in Milne. Anyone using a USB boot stick to do deployments will need to update. Some quick notes about the move:

– Cyder workgroups (DHCP options) OSU-MDT-PXE and OSU-MDT-PXE-UEFI have been updated with the server’s new IP address.

Old: VLAN 463, 10.198.0.68
New: VLAN 1112, 10.217.96.133

Note: Next week I will be asking NOC to configure IP helpers on the Milne building router. This will replace the workgroups above for the build bench, allowing any client (BIOS or UEFI) to PXE boot.

– MDT boot images have been updated to use the server’s FQDN/DNS name instead of IP address.
– The build bench firewall (CN2-FW) has been updated to allow the necessary ports through for remote management and OS deployment.

Bench, Community Network, Field

CN computer intake location

Leave a comment

Team,

For CN computers destined for the build bench, the intake/drop-off location is now the grey cabinets at the West end of the long corridor outside Andrew’s office (end closest to the door).

A sticker should be added to each computer including the following information:

  • Ticket #
  • Customer Name
  • Date dropped off

If a computer is too large to fit in the cabinet, it can be placed on the floor next to the cabinets or across the walkway. For large shipments of computers that won’t fit by the cabinets, they can be stored in the old Bench office – please notify Samuel and Jeff if this is the case.

This is ONLY for CN computers, not personal devices.

Let me know if you have any questions or concerns about this change.

NOTE: the intake location for Extension computers is still the Ballard office.

Base, Bench, Community Network, Field

NEW WINDOWS IMAGES WITH OFFICE 2016

Leave a comment

New Windows images with Office 2016 will go live tomorrow.

Windows 7/8.1: Added .NET 4.6.1, PowerShell 5.0, Office 2016 (replaces 2013)
Windows 10 CB/LTSB: Added Office 2016 (replaces 2013)

Added the following applications/packages to the MDT build share:

  • All IE11 prereqs
  • Microsoft Internet Explorer 11 for Win 7
    • Created a custom deployment package with IEAK 11
  • Microsoft .NET 4.6.1
  • Microsoft Windows Management Framework 4.0
  • Microsoft Windows Management Framework 5.0 for Win 7
  • Microsoft Windows Management Framework 5.0 for Win 8.1
  • Kernel Mode Driver Framework 1.11
  • User Mode Driver Framework 1.11

These applications have been added to all applicable build task sequences to reduce manual work on reference images.

Base, Bench, Call Desk, Community Network, Field

Call Center assistance expectations

Leave a comment

The managers would like to clarify expectations during times you help out in the Call Center.

Max is the quarterback for the Client Services Call Center; he calls the shots when it comes to logistics. Max may reach out for call center assistance from people who are not regularly assigned to the call center in times when additional coverage is needed.

The managers want to clarify expectations for that assistance.

Phones: If Max asks you to help with calls, you should sign into the split and AUX in to take calls. Using a computer in the call center area is recommended as it facilitates communication with the team. Joining the #callcenter channel in Slack is also recommended. Unless Max specifically asks you to help in the queue only, or do some other specific task (such as assisting other phone technicians) you should assume that taking calls is priority number 1. This is usually where we need the most help.

Prior obligations: If you have conflicting priorities that would prevent you from taking calls (such as an appointment with a customer), please let Max know.

If you have any questions about these changes, please discuss with your manager. If you need training or a reminder on how to do something, please ask Max or another member of the regular call center crew.