" > Tip of the Week : Windows Updates & Manitou Compatability - Eric Schmitt



Tuesday, February 07, 2012
Tip of the Week : Windows Updates & Manitou Compatability - Eric Schmitt
Minimize

Tip of the Week : Windows Updates & Manitou Compatability - Eric Schmitt

Posted in [Manitou Maintenance], [Tips] By Brandon Lilly

Every month Microsoft sends out updates to their Windows Operating System.  Most of us with our home PC's happily will let windows download and install these updates in the background.  This week's tip looks at how those updates can affect Manitou in a server environment.

We've all seen it, logging into our computers; a tooltip that comes up in our taskbar saying "Windows Updates are ready to install."  On servers like a Manitou system automatic updates can cause unintended issues.  In a best case scenario running the automatic updates will usually just reboot the server, at 3:00 am.  This usually ends with a call to either a central station supervisor, or Bold emergency support to get Manitou up and running again.  Things can get worse depending on what updates get installed as well.  Take for example the recent .net 4.0 updates that have just been released.  Manitou components have not yet been certified to work with .net 4.0 so installing those updates could lead to the system being down for an extended period while a technician works with you to roll your servers back to a compatible version.  As we all know, with Manitou and life safety, every minute a system is down has potential for disastrous results.

We at Bold Technologies will always make sure to disable automatic updates when setting up new systems but now you know a bit of the reasoning behind this practice.  To check for yourself whether or not your machine is set to update you can look at the "windows update" control panel on your system.  The best way to run updates on your system is to  run the windows updates on one of your backup servers only.  This ensures that the system will not go down during a reboot and that we can quickly recover should something go wrong.  After your backup server has been updated, do a controlled failover to that machine and test to make sure everything works correctly.  If there are no problems, run the updates on your remaining servers.

Feel free to connect with any of us here at Bold Technologies should you have any questions!

Eric Schmitt

erics@boldgroup.com

Comments

Was it good for you, too? Join the discussion »

    leave a reply

     [Quick Submit with Ctrl+Enter]


    1. Re: Tip of the Week : Manitou System Requirements - Jose Garundo

      Anyone have any trouble with 1.6 manitou client working on Windows 7 64bit machine?

      --chase

    2. Re: Tip of the Week : Manitou System Requirements - Jose Garundo

      Just FYI with respect to the SQL edition, if you get to SQL 2008 R2 the Express size limit jumps to ...

      --CM

    3. Re: Introducing Manitou 1.5.3. and a New Release Notes Process

      Keep up the good work.

      --chris

    4. Re: [Updated] Central Station Manager Course coming May 11

      When will you be having another course?

      --Kim

    5. Re: Patch release summaries

      Every time we speak to support we are told (more often than not) that the first thing we should do w...

      --Jon Shaw

    6. Re: Patch release summaries

      Hi Jon,As you may, or may not, know it is the policy of Bold Technologies to avoid disruption of the...

      --Jennifer Bruce

    7. Re: Patch release summaries

      About time we know about a patch before we find out we are something ridiculous like 15 patches behi...

      --JonBoy

    Privacy Statement  |  Terms Of Use
    Copyright 2011 Bold Technologies Ltd