A Year Without Tech Fires: Central Montana K8 Gets Real IT Support Around a Part-Time Tech

A central Montana K8 school with under 150 students relied on a full-time principal and a part-time retired tech, onsite only 6–8 hours a week. A 2008 Windows server was still in production, wireless ran on a consumer mesh kit, there was no managed AV or EDR, and everyone operated in firefighting mode. The principal fielded most tech requests. Some issues sat for days until the retired tech was physically on campus. Testing days and busy instructional blocks always felt risky.

This is what changed when they added K12 Managed IT from a Montana based team around that existing setup.

Before: Principal as Help Desk, Old Server, Consumer WiFi

1. Part-time retired tech with limited hours The tech knew schools and basic systems but had only 6–8 hours per week on site. Anything that broke outside that window waited.
2. Principal handling support Teachers went to the principal first. Many tickets were verbal hallway requests. Issues often resurfaced because there was no central tracking.
3. 2008 Windows server in production The server was out of support and could not take current updates. It was a single point of failure for important functions.
4. Consumer mesh WiFi The network used a home grade mesh kit. Coverage was uneven. Performance dropped when multiple classes were online or during testing.
5. No managed AV or EDR Devices had basic, unmanaged protection. No one had centralized visibility into malware, risky behavior, or compromised accounts.

The result: constant reaction, little planning, and a lot of stress on a small leadership team.

The Turning Point: They Needed More Than “One More Good Effort”

The district accepted that:

1. They were not going to hire a full time enterprise experienced IT person for a 150 student K8.
2. The retired tech was doing solid work within limited hours. The problem was scope, not effort.
3. The risk from the old server, consumer Wi-Fi, and no security tools was out of line with the size of the school.

They wanted three things:

1. Modern, supported infrastructure.
2. A clean, simple way for staff to get help fast.
3. A model that respected their budget and their existing people.

The Fix: Managed IT Wrapped Around the Existing Tech

They partnered with Schoolhouse IT for K12 Managed IT, with a clear division of labor.

1. Server migration plus Google Workspace for Education The 2008 server was migrated off to supported infrastructure. At the same time, Google Workspace for Education was set up as the core platform so staff and students had modern, cloud based tools.
2. Google SSO for logins All computers were configured to use Google SSO, so users signed in with one account for devices and Google tools. This cut down on password confusion and simplified account management.
3. Enterprise grade WiFi Consumer mesh was replaced with a school ready wireless system designed for classroom density. Coverage and performance improved immediately.
4. Managed AV / EDR Centrally managed antivirus and basic endpoint protection were deployed across staff and student devices. Alerts went to the managed IT team, not to the principal.
5. Full remote help desk plus predictable onsite visits Staff could call a full remote help desk whenever they needed support. In addition, boots on the ground were scheduled at a consistent time every month for hands-on work, projects, and check-ins with the principal and tech.

The part time tech stayed in place, now as a supported local presence instead of the only line of defense.

How Day to Day Life Changed

After these changes, the school saw practical, noticeable improvements.

1. Fewer bottlenecks Issues were routed directly to the remote help desk or to tickets. The principal still had visibility, but was no longer the frontline troubleshooter.
2. Faster resolution for staff Teachers could pick up the phone or submit a ticket and get remote support right away, instead of waiting for the one day the retired tech was on site.
3. A safer, simpler login experience Google SSO meant staff and students used one set of credentials across devices and tools, reducing lockouts and wasted class time.
4. More use out of monthly onsite time Because the remote team handled many of the day-to-day problems, the scheduled onsite visit each month focused on proactive work. Checking Wi-Fi coverage, cleaning up wiring, reviewing upcoming projects, and meeting with leadership.

The environment stopped lurching from issue to issue. The retired tech’s limited hours went further because they were no longer trying to do everything alone.

The Bottom Line After One Year

Within a school year, this central Montana K8 achieved:

1. No critical systems running on an unsupported operating system like a 2008 server.
2. Stable, school grade WiFi that could handle testing and normal instruction.
3. Centralized security tools with real monitoring for devices.
4. A full remote help desk plus predictable monthly onsite visits.
5. A principal and part-time tech who could finally work from a plan instead of a stack of problems.

For a small K8, that is what “a year without tech fires” actually looks like. Not perfection. Just calm, predictable technology that lets the adults focus on students.

If you want this kind of stability in your Montana school while keeping your existing tech role, see what is included in our K12 Managed IT services for Montana schools and districts.