Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the System Administration topic
No spam. Unsubscribe anytime.
Select board interviews IT systems administrator candidate to centralize Limerick’s IT services
Summary
At a Jan. 6 workshop the Limerick select board questioned an IT candidate about consolidating backups, inventorying roughly 20–25 devices, establishing a ticketing system, and defining service‑level expectations before soliciting comparable bids.
Get email alerts on the System Administration topic
No spam. Unsubscribe anytime.
LIMERICK — The select board interviewed an applicant for a contracted system administrator role on Jan. 6, pressing the candidate on backups, device inventory, availability and the scope of a proposed managed‑service arrangement.
The applicant, who identified himself as an IT systems engineer currently working at St. Joseph's College of Maine, said he has “a little bit over 10 years of experience” supporting municipal and educational environments and recommends a single point of responsibility for the town’s IT. “You can put a piece of software on all of the computers that you want me to manage and it would allow me to remote in and help you,” the applicant said.
Board members said the town has had trouble contacting its existing system administrator and cited an expired backup subscription in recent months. A select board member said the town’s Carbonite backup lapsed and was later reinstated, a lapse board members called unacceptable for a municipal backup. The candidate recommended assessing whether backups should use Microsoft 365 tools such as OneDrive and SharePoint, cloud services, or local server images depending on what the town needs.
The candidate recommended a ticketing system to log requests, track hours and prioritize incidents, and described routine remote fixes that typically take minutes. He said most issues can be handled remotely but acknowledged some projects — equipment installs or in‑person troubleshooting — require on‑site work and that response times should be defined in a service‑level agreement. “It really depends on the severity,” he said, describing a priority system that would distinguish an entire‑building outage from a lower‑priority request such as installing Microsoft Office for the fire department.
Board members and the applicant agreed the town lacks a reliable inventory. Participants estimated roughly 20–25 workstations across the municipal offices, library and the fire station, but the exact number and the number of mailboxes are unknown. The existing municipal software used for finance, Trio (Harris), is hosted on a server the board believes sits in the town basement; the applicant said a walk‑through of the server and firewall would help scope work and pricing.
Security concerns were a recurring theme. The applicant recommended managed antivirus, spam filtering and configuration limits (for example, throttling large outbound mail bursts) and described two‑factor authentication setup issues that had tripped staff during the Microsoft 365 migration. He also warned that certain legacy systems, including a small TV/streaming setup, can limit the ability to apply security updates without disrupting other services.
There were no formal votes. The select board said it will confer internally, develop a consistent scope of work so bidders can offer comparable proposals, and collect device counts and server‑location details to circulate to candidates. The board estimated it would follow up within a week to determine next steps.
The workshop began at 6:03 p.m., paused at 6:24 p.m., reconvened at 7:00 p.m. for a second session of follow‑up questions, and ended at about 7:28 p.m.

