Loading ...
Sorry, an error occurred while loading the content.

Re: Please Help - LANDesk & drive protection software

Expand Messages
  • ldmsguy
    Gary, We completely agree! There are many pieces to the puzzle and we re trying to take all of them into account. Those of us on my team that are implementing
    Message 1 of 41 , Nov 29, 2006
    • 0 Attachment
      Gary,

      We completely agree! There are many pieces to the puzzle and we're
      trying to take all of them into account.

      Those of us on my team that are implementing and supporting LANDesk
      and the Symantec Antivirus Deployment are doing our best to provide
      great service with little or no interruption to family history
      centers. This includes a great deal of testing and continual
      tweaking to streamline and improve the pieces we are responsible for.

      Thanks for positive feedback and patience.

      Mr. Lynn Shaw
      LANDesk Specialist
      FamilySearch Support, CHQ



      --- In fhctech@yahoogroups.com, "Gary Templeman" <gtempleman1@...>
      wrote:
      >
      >
      > ----- Original Message -----
      > From: "sjniedermeyer" <yahoo@...>
      > To: <fhctech@yahoogroups.com>
      > Sent: Thursday, November 16, 2006 8:59 PM
      > Subject: [fhctech] Re: Please Help - LANDesk & drive protection
      software
      >
      >
      > Hi Lynn,
      >
      > I don¡¦t envy you trying to manage so many disparate systems fº
      >
      > You might be able to license the Centurion Technologies product
      line
      > to allow you to:
      >
      > 1) disable or ¡§thaw¡¨ the protection software using a command
      > line option
      > 2) push your updates via LANDesk
      > 3) then issue a reboot which will restart the system and enable
      > the protection software
      >
      > On frozen computers or not, I would definitely be nervous about
      item #3.
      > Reboots that are not local user controlled have the potential of
      losing
      > data. LANDesk can only do its job when the computer is on. For
      many centers,
      > that coincides with their hours of operation. A patron (or staff
      member for
      > that matter) getting caught with an automatic reboot may have no
      chance to
      > save, print, finish burning a CD, etc. and will get really peeved.
      >
      > That is precisely why on my personal and business computers I do
      NOT allow
      > Windows to do automatic updates. I never want to walk away from
      the computer
      > with something in progress, only to come back to see a message
      that Windows
      > had installed an update that required an automatic reboot. I let
      it tell me
      > that updates are available. Unless something is super critical, I
      wait a few
      > days to be sure nothing adverse pops up (Microsoft has not has a
      stellar
      > record with all their patches), then I download and install when
      it is
      > convenient for ME.
      >
      > Perhaps for any of those types of updates that require a reboot, a
      message
      > could pop up (like those annoying task bar balloons), giving
      instructions
      > how someone in the center could initiate the update, and they
      could then do
      > it at an opportune time fro a reboot. That doesn't fully address
      the
      > unfreezing issue, but it would prevent nasty surprises to a patron.
      >
      > Human beings make mistakes, and the techs in SL are human. I know
      some of
      > them monitor this list. Many of us recall the fiasco last year
      where a
      > change to the servers in SL threw MANY centers off the Internet. I
      > understand a desire for SL to have more standardization and
      control, but
      > PLEASE be careful with the centralization process. If I screw up
      and knock
      > out the computers in my center, a few people are affected, and
      many can go
      > to a neighboring FHC while things get fixed. If a "push" turns out
      to cause
      > problems, it could negatively affect dozens or hundreds of
      centers, and we
      > in the trenches have to pick up the pieces.
      >
      > If this isn't already happening, I would suggest that a good sized
      pool of
      > centers be asked to designate one of their computers as a beta
      computer.
      > Have a variety of old and new computers, ones with different
      software
      > configurations, etc. That would let any potential changes be
      tested on a
      > wider range of configurations. Then let those changes "simmer" out
      in the
      > field for a while before the final push. Aside from A-V and
      Windows security
      > updates, there is little in the software on our computers that
      will require
      > an emergency patch, so things should be able to be tested VERY
      thoroughly
      > before general distribution.
      >
      > We also need to remember that there are probably many centers
      where someone
      > has carefully and lovingly nurtured their centers technical issues
      over a
      > long period of time. I see a potential for hard feelings if that
      nebulous
      > entity called FHC Support messes up their finely tuned and tweaked
      systems.
      >
      > Gary Templeman
      >
    • ldmsguy
      It would be interesting to know which process(es) are causing the problem. You may already know this... but in the Task Manager, under the View menu, you can
      Message 41 of 41 , Dec 21, 2006
      • 0 Attachment
        It would be interesting to know which process(es) are causing the
        problem. You may already know this... but in the Task Manager,
        under the View menu, you can select additional columns to be
        displayed. Check out Page Faults Delta, Virtual Memory Size, I/O
        Reads, I/O Writes, CPU Usage and CPU Time. If you can get this
        information while the problem is occurring, and communicate this
        data and the process name to the FamilySearch Support, Church
        Headquarters Team, it will be very helpful in troubleshooting and
        resolving the problem.

        Thanks.

        Lynn Shaw
        LANDesk Specialist
        FamilySearch Support, CHQ

        --- In fhctech@yahoogroups.com, Merlin R Kitchen <mkitchen@...>
        wrote:
        >
        > >Gary Templeman writes:
        > >I can report that in the last few weeks, ALL or our computers
        seem to
        > have
        > >periods of sluggish behavior (mouse clicks do not open menus
        quickly,
        > etc.),
        > >often for the first few minutes right after boot up. I have not
        had time
        > to
        > >try to trace it down, but it does seem *suspicious* that this has
        > happened
        > >only since LANDesk (and the Symantec installation) has taken
        place.
        >
        > I can confirm that symptom. We were told earlier in this
        discussion that
        > if a Friday 3 pm update got missed, it would wait until the next
        time the
        > computer was on at 3 PM. That does not appear to be true. Our
        computers
        > were on last Friday at 3PM but were turned off at 5 PM MST; on
        Monday
        > (yesterday) I noticed that three of our computers became totally
        unusable
        > because they would not respond. I could see that the internet
        traffic
        > was high to that computer by looking at the lights on the ethernet
        > interface; I could also see the disk "thrashing" because the disk
        > activity light on the front of the computer was blinking so rapid
        it was
        > almost as if it was constantly on.
        > I just had to tell the person on that computer--go to another
        computer
        > or wait until the lights stop blinking. And in fact as soon as
        those
        > symptoms went away (the disk stopped thrashing and the ethenet
        traffic
        > went way down) then the computers started acting normal again.
        > Yesterday, since we had classes running, we just had to wait for
        it to
        > finish whatever it was doing. I tried to use the Windows Task
        Manager
        > screen to see what was going on, and could not tell.
        > I want a way to control when those things happen--when we are
        closed!
        > I am willing to leave the computers on overnight if need be.
        >
        > Merlin Kitchen
        > Utah South Area Family History Training Center
        > FHC 3369722
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.