Everybody Staze...

Nobody leavz...

  • Home
  • About Me
    • LinkedIn
    • Lab
  • Contact
  • Links
  • Reviews
  • Sitemap
  • Weather
You are here: Home / Archives for 2020

Archives for 2020

Official job change

2020/07/23 By staze Leave a Comment

For those that don’t know, I work at a higher ed institution in IT. Specifically I started as a student employee at the central helpdesk, then moved to work as a sys admin, then manager at the Journalism school for over a decade.

For the last couple years, our CIO has been working toward centralization/consolidation/unification/buzzword of IT on campus. This is partially because campus has “haves” and “have nots” as far as IT, and also in an attempt to get ahead of any discussion on cost cutting/savings. State funding has wained for years, and every few years budgets get scrutinized/cut and people start asking “how can we save money?” When the vast majority of expenses are FTE (people), you have to start looking at job cuts. But, when you’ve centralized, and eliminated a lot of the redundancy, and are offering more consistent services across campus, it’s hard to come and say “you need to cut services”. This theme is playing out across campus as things like Communications, Business offices, HR, etc are all slowly consolidating for various reasons above and beyond cost savings.

Related to this, we launched a “Transform” process where working groups were built to plan the future. What did we want to do? Part of the process was also to highlight things that campus needed and were missing, and if we could use this as a chance to implement. In my case, we formed a Device Management group to plan and pitch for a Device Management team that would handle managing macOS and Windows computers across campus, iOS/Android, and also ideally handle lifecycle management (purchasing, surplus/food chaining, and disposal). Campus already had a few Jamf Pro instances, and a couple SCCM/MECM instances. There were no campus standards for computers, but many departments had standards. Some departments were heavily macOS (Design, Journalism) and some were heavily Windows (Business, Administration), but most departments were mixed, and management was extremely inconsistent across campus (some were entirely managed, some were partially managed, and some had almost no management because of lack of knowledge, or faculty resistance).

The outcome of the work was to have support for campus broken into 4 different support units. Academic North, Academic Central, Academic South, and Admin (handling the bulk of the administrative units). Then there was the central helpdesk that would continue to handle non-employees, and personal computers, and then Enterprise Device Management, or EDM. The support zones were just going to absorb the existing departmental support based on where they were, the helpdesk was largely going to stay the same, but EDM required interviews since it was determined none of the existing people on campus were doing that job already (this was arguable, but whatever). Those of us that were doing the job all applied, and got the jobs. It was 4 primary EDM Admins who did management of fac/staff and departmental machines on campus with both Jamf and MECM. Then a labs team who would handle the academic labs across campus.

Which is where I come in. I got one of the EDM Admin jobs, so my job now is 100% device/computer management which is what I wanted. I was a Sys Admin and enjoyed it. I got promoted to being a manager (and still did sys admin stuff), which I didn’t overly enjoy. I always felt I preferred a “lead” position more than a “boss” position.

While all this was being planned, we had our final recommendations, and things were moving along… then COVID happened and everything got pushed forward much faster because campus had to go 100% online in very short notice, and we all had to work together. Many of us started doing our jobs before we got the jobs officially because of this. We stood up a much larger VDI infrastructure to offer online labs. We also took on much of campus computer purchasing, and campus software licensing. We also went about standing up a brand new MECM instance (that was clean and would JUST handle things supported by the new support), and a new site in our existing main Jamf Pro instance to handle macOS and iOS devices.

Anyway, greatly enjoying new job. It’s a great team, and has given many of us team members we can trust to handle things if we take vacations, are sick, etc. Many of us were solo in our previous jobs and being on a team is a huge win.

Filed Under: Uncategorized

Repairing Yale YRD226 Motherboard sensor

2020/01/18 By staze 4 Comments

I recently purchased a Yale YRD226 off eBay for next to free ($35) that came with the zwave plus module. Was sold for parts/repair. Figured even if it didn’t work, it would be worth it just for the Z-wave module.

I got the unit and it appeared brand new, albeit terribly packaged. I powered it up, got it enrolled in my Z-wave mesh, and didn’t think anything of it trying in vane to calibrate the motor since it wasn’t in the door at the time.

Today, I installed it, and it would fail it’s handing (figuring out which side of a door it was installed on, which direction was lock vs unlock, etc). I THOUGHT it was locking and not realizing it was locking, but then I hit “lock” on my Hubitat, and it unlocked. Huh. I factory reset twice, and did the auto-handing via the keypad, and neither fixed it. Calling Yale, they said it’s likely a failed sensor, but I would need proof of purchase to get the back unit replaced. Now knowing where the sensor in question likely was, I took the unit to the bench.

So, under the microscope, I noticed just above the motor shaft there was a nice dent. Some sharp probes on my multimeter showed the track going to one of the latch IR sensors was busted. Sorry I don’t have pictures! I’ve yet to get a camera for my microscope.

After some scraping of the PCB solder mask and conformal coating, some 30AWG wire, and I was able to bridge the gap. Installing back on the door, it powered up and again had issues, but then I went in and did the auto-handing. It calibrated! Fixed!

So, long and short of it, likely previous owner either wasn’t careful and bashed the PCB with the latch “bar” missing the motor output, or it was damaged in shipping from the seller. But, it’s now fixed! If it breaks again, I’ll drill out the via on the board and solder directly to the IR sensor. Sadly, I didn’t have any good “glue” to hold the wire in place from vibration from the motor (and door opening/closing). May need to reevaluate that and throw some non-acidic silicone on there.

Kudos to the Yale support I talked to. While they did say it would void the warranty to repair the lock, I didn’t have a warranty to void, so them sharing that the sensor was on the “back side” piece of the lock was enough to look and find the damage! This lock is replacing a Schlage Z-Wave lock I’ve had issues with, but I will say, Schlage do a better job of protecting the PCB from accidents.

Filed Under: Electronics

Weather

Categories / Archives

  • Apple
  • Coding
  • Electronics
  • Energy
  • Home Ownership
  • Miscellany
  • Politics
  • Prius
  • Sys Admin
  • Travel
  • Uncategorized
  • Work
  • June 2026
  • April 2026
  • August 2025
  • April 2025
  • January 2024
  • February 2021
  • July 2020
  • January 2020
  • April 2019
  • March 2018
  • February 2018
  • June 2017

Copyright © 2026 · Staze On Genesis Framework · WordPress · Log in