Punk Shows to Patch Management: Richard Glaser's Mac Admin Career

Before Richard Glaser was a Solutions Architect, he was a math major working the library's computer lab by day, and living a whole other life by night: playing guitar in punk and alternative bands, running studio sessions, spending years immersed in the Salt Lake City music scene. Before that he was delivering newspapers with his sister at age 10, then washing dishes and working prep in kitchens.

None of it looked like a path into IT. It found him anyway.

Two worlds that weren't really separate#

The math-major-by-day, punk-musician-by-night combination looks like a contradiction from the outside. Richard didn't experience it that way. His dad ran an Apple User Group, so Apple technology was part of the household well before Richard had to pick a major.

That early exposure gave him a head start most students didn't have. By the time he landed a student job in the library's computer lab, he already understood how Apple machines worked from years of watching his dad's group tinker, troubleshoot, and swap knowledge long before there was a manual for any of it.

Music ran alongside that, not against it. Richard was drawn to the same instincts in both: recording and producing tracks, designing cassette and CD artwork, building the visual identity for shows, figuring out how things worked by doing them.

The scene itself had its own character. Salt Lake City's punk and alternative crowd played all-ages DIY spots and underground clubs like the Speedway Café, tucked beneath the 500 South viaduct, along with DV8, The Palladium, and the Pompadour, a tight-knit local circuit that Richard knew from the inside, the same one later dramatized in SLC Punk!

From the stacks to the server room#

Richard was working as a student consultant in the University of Utah's Marriott Library computer lab, one of the original ARPANET sites. The University of Utah carries deep roots in computer history, with John Warnock earning multiple degrees there before co-founding Adobe with Charles Geschke. It was also chosen in Apple’s formative years as a select few universities to initially sell and deploy its personal computers, building a deeply rooted institutional partnership.

A student job turned into a full-time offer, and Richard's first job was managing modified Macintosh SE systems, using rdist (a Mac port of Unix tools) to keep files distributed and machines in sync. It was the start of a career that eventually took him from hands-on Mac administration to IT Management looking after Apple, Microsoft, and network teams, and finally into his current role architecting technology strategy for the whole library.

The project that helped shape Mac OS X#

Some of the most formative years of Richard's career were spent being part of the Higher Education Mac OS X Labs Deployment Project, a collaborative effort that grew out of Apple's University Executive Forum in the early Mac OS X days. Around 20 universities took part, including the University of Utah as a founding participant, all working out how to deploy, secure, and manage Mac OS X across large computer labs. They shared what they learned through macosxlabs.org: scripts, tools, real documentation, using things like NetBoot, NetInstall, Apple Software Restore, and Radmind. The project eventually grew into MacEnterprise, taking the same problem set from computer labs into full enterprise environments.

One meeting has stuck with Richard ever since. The group was in Cupertino meeting with Apple, working through a long list of requests based on what universities and Mac admins actually needed on the ground. At one point, Phil Schiller got frustrated with how many requests the group was making, and later realized the complexity these environments presented.

"It was a memorable reminder that we were having a real influence on the direction of Mac OS X, and that Apple was genuinely listening to what administrators were asking for."

Richard remembers this meeting as proof the work mattered, that a room full of admins pushing back on Apple actually changed something.

What carries over#

Ask Richard what from those early days still shows up in how he works, and it's not a tool or a specific technique. It's more of a posture. Early Mac administration didn't come with a vendor playbook.

"There often wasn't a guide or a vendor-supported solution, so you had to understand how things worked, experiment, build your own tools, and learn from what went wrong."

That's still the job, twenty-some years later. New technology shows up, there's no obvious answer yet, and the way through is the same as it always was: dig in, try things, pay attention to what breaks.

The value of community is also timeless. His dad's Apple User Group taught him people learn faster together, just like bands playing and promoting each other's records. Now Richard runs the University of Utah's Apple Admin Group, giving back the same way his dad did.

From punk shows to prep lines to a seat at the table that helped shape Mac OS X, nobody plans a path like this. But the curiosity, and the instinct to build community around it, is what makes Richard's path so unique.

Know someone with a "previous MacAdmin life" story like this? We're always looking for the next Mac admin to feature. Reach out to Kitty Shephard.