[OPLINTECH] Handling Scheduled Library IT Outages

[Chad Neeper]

This isn't necessarily apples-to-apples, but as outsourced IT, I tend to do
workstation updates during business hours while working around
patrons/staff as much as possible. I try to keep kicking patrons/staff off
the computers to a minimum and just bounce around between them as they
vacate computers. As for server/firewall updates, I try to keep anything
that requires a reboot to non-business hours as much as possible. Usually
this means connecting in remotely overnight or during the weekend/holiday
and performing the necessary maintenance. Occasionally, however, I need to
be present for a reboot/shutdown/whatever and it needs to be done during
the normal working day. It is what it is.

FWIW,
Chad


______________________________
*Chad Neeper*
Senior Systems Engineer

*Level 9 Networks*
740-548-8070 (voice)
866-214-6607 (fax)

*Full IT/Computer consulting services -- Specialized in libraries and
schools*

On Tue, Jul 31, 2018 at 12:11 PM, Lane, Bill via OPLINTECH <
oplintech at lists.oplin.org> wrote:

> All,
>
>
>
> I was wondering how other libraries handle IT maintenance outages? Do you
> have a regularly scheduled monthly or quarterly outage or do you schedule
> them as needed?
>
>
>
> Thanks,
>
>
>
> *Bill Lane*
>
> *IT Manager*
>
> *Public Library of Cincinnati and Hamilton County*
>
> *Desk: 513-369-6948*
>
> *Wireless: 812-532-9058*
>
> *Fax: 513-369-3188*
>
> *e-mail:  bill.lane at cincinnatilibrary.org
> <bill.lane at cincinnatilibrary.org> *
>
>
>
> _______________________________________________
> OPLINTECH mailing list
> OPLINTECH at lists.oplin.org
> http://lists.oplin.org/mailman/listinfo/oplintech
>
> ***Would your library like to keep its servers in a  Tier III rated data
> center? OPLIN provides this service: https://www.oplin.ohio.gov/co-
> location-service***
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplintech/attachments/20180731/d6178039/attachment-0001.html>