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

RE: [fhctech] Subject Change: Improving the way we do things.

Expand Messages
  • RussellHltn
    I think the factory default is Symantec or some thing like that. ... From: fhctech@yahoogroups.com [mailto:fhctech@yahoogroups.com] On Behalf Of
    Message 1 of 53 , Mar 1, 2007
    • 0 Attachment
      I think the factory default is "Symantec" or some thing like that.


      -----Original Message-----
      From: fhctech@yahoogroups.com [mailto:fhctech@yahoogroups.com] On Behalf Of
      jbmarcum@...
      Sent: Wednesday, February 28, 2007 9:49 AM
      To: fhctech@yahoogroups.com
      Cc: ldmsguy
      Subject: Re: [fhctech] Subject Change: Improving the way we do things.

      Lynn,

      It seems like one way the church can cut down on support is to let the local
      computer specialists uninstall and reinstall programs when we have problems
      with them. I have 2 more machines that will not update Symantec's
      AntiVirus, and now I have to find time to go to the FHC when I can call
      Support on the phone and have someone remotely login and uninstall the
      application for me. Why are we not trusted with the password to uninstall
      it? It creates a bigger burden for me now to find the time to fix this
      problem since I work full time. I feel like just letting the problem go,
      because I have other problems to deal with, like setting up a new Admin pc.
      Is there a chance we can be provided with this password information?

      Judith Marcum
      Yuma Arizona Family History Center Computer Specialist jbmarcum@...
    • ldmsguy
      Thanks Kent. I appreciate your willingness to share information. We did a bit of research on several different types of software that offer drive protection
      Message 53 of 53 , Mar 6, 2007
      • 0 Attachment
        Thanks Kent. I appreciate your willingness to share information.

        We did a bit of research on several different types of software that
        offer drive protection (Deep Freeze, Drive Shield, Cornerstone, EAZ-
        FIX, MS Shared PC Toolkit, are the ones I remember at the moment).
        We found that none of the products were designed to work centrally in
        a distributed enterprise like ours where there are many remote
        networks that are autonomously administrated, and that are only
        connected via the Internet.

        We found that with most of these products, we could script a reboot
        to unlock the system, do maintenance, and then reboot the system to
        re-lock the system, but I think most FHC Technology Specialists would
        appreciate us more if we did NOT attempt that feat. Plus from our
        perspective it became much too unmanageable.

        We've come up with a simpler solution for systems with this type of
        technology installed. We're still testing it to see how well it
        works, and if it passes, then we'll release it. Hopefully soon.

        Again, thanks for being willing to give additional ideas. It really
        does help. You guys bring a vast amount of experience and knowledge,
        with lots of different backgrounds. That's one of the main reasons
        why I wanted to start participating in these forums.

        Lynn

        --- In fhctech@yahoogroups.com, "djkentsmith" <djkentsmith@...> wrote:
        >
        > Lynn,
        >
        > We are using Faronics Deep Freeze Enterprise version at our FHC for
        > drive protection software. We are not using this feature but as I
        > understand it Deep Freeze can be controlled via Landesk with a plug-
        > in for Landesk.
        >
        > I'm the FH Director and by no means a computer expert. I just
        wanted
        > to bring this to your attention as it may be something for you to
        > look into. The link is as follows:
        > http://www.faronics.com/html/deepfreeze.asp
        >
        > Kind regards,
        >
        > Kent Smith
        > Vancouver BC 1st Ward FHC
        >
        > --- In fhctech@yahoogroups.com, "Lynn Shaw" <shawlh@> wrote:
        > >
        > > Gary,
        > >
        > > The LANDesk Support Agent upgrade has been through many
        iterations
        > of testing,
        > > but still needs another round or two of beta testing. If you or
        > anyone else on
        > > this forum is willing to help by participating in the beta test,
        I
        > would
        > > appreciate the assistance.
        > >
        > > If you're interested, please send me an email with your contact
        > information,
        > > your family history center number and name, and the name of one
        or
        > two computers
        > > you want to include in the beta test.
        > >
        > > I'd also like to open a dialog with individuals discussing
        possible
        > custom
        > > LANDesk configurations for systems with drive protection software
        > installed.
        > >
        > > Thanks.
        > >
        > > Bro. Lynn Shaw
        > > LANDesk Specialist
        > > FamilySearch Support, CHQ
        > >
        > >
        > >
        > >
        > >
        > > >>> On 2/25/2007 at 5:14 PM, in message
        > > <001401c7593b$34502a80$0200a8c0@YOURB05330F56F>, "Gary Templeman"
        > > <gtempleman1@> wrote:
        > > Is there any news on an ETA for the update? I hadn't had a chance
        > to install
        > > the workaround program, and today (during our genealogy class)
        our
        > DIS
        > > computer pegged out at 99% CPU usage for LDISCN32.EXE for over 30
        > minutes
        > > before I finally killed the process. That was when logged on as
        > > Administrator. The initial boot into the Patron user had errors
        > associated
        > > with the Inventory Scanner that were logged under the Event
        Viewer.
        > >
        > > Three other computers has periods of sluggish responses. After
        > class I
        > > uninstalled LanDesk on all the computers. I am willing to
        > reinstall, but I
        > > would rather not have to install another program as temporary
        > workaround. If
        > > the update is imminent I would wait for it.
        > >
        > > Gary Templeman
        > > Corvallis Oregon FHC
        > >
        > > ----- Original Message -----
        > > From: "ldmsguy" <shawlh@>
        > > To: <fhctech@yahoogroups.com>
        > > Sent: Wednesday, February 14, 2007 8:49 AM
        > > Subject: [fhctech] Re: LANdesk caused problems?
        > >
        > >
        > > >I actually was out of the office taking care of my family while
        one
        > > > of our children was in the hospital for 8 days. So I hadn't
        been
        > > > reading any of the postings.
        > > >
        > > > This looks like a good workaround until we can get the update
        > > > deployed.
        > > >
        > > > --- In fhctech@yahoogroups.com, "Dan" <dvester@> wrote:
        > > >>
        > > >> Lynn, since it appears you may have missed my post in a new
        > thread,
        > > > I'm
        > > >> re-posting it to this thread for you. This will fix your
        slowdown
        > > > problems:
        > > >>
        > > >> After observing the debilitating effects that Landesk's
        inventory
        > > > scanner
        > > >> has on our FHC computers, particularly on a brand new 3 ghz
        > machine
        > > > we just
        > > >> put in service, I decided to find a solution. After a little
        > > > searching
        > > >> through Google, I discovered the following utility program:
        > > >>
        > > >> http://www.bitsum ( http://www.bitsum/ )
        > > <http://www.bitsum.com/prosuper.asp>
        > > > com/prosuper.asp
        > > >>
        > > >> This is a utility that loads as a service, and continuously
        > > > monitors all
        > > >> programs and processes running on the computer. When it finds a
        > > > program or
        > > >> process that is hogging CPU time for more than 2 or 3 seconds
        > (like
        > > > the
        > > >> landesk inventory scanner), it automatically, temporarily,
        > reduces
        > > > it's
        > > >> priority level to low, this freeing up the computer for the
        local
        > > > user,
        > > >> while still letting the hoggish task finish it's duty in the
        > > > background.
        > > >>
        > > >> I've installed this on two of our 8 computers, and have let it
        do
        > > > it's thing
        > > >> for 2 days now, and it's a thing of beauty to behold! Landesk,
        > nor
        > > > any other
        > > >> errant process, can no longer lockout the user. The computers
        now
        > > > seem
        > > >> faster to respond than I have ever seen them before. I will be
        > > > installing
        > > >> this utility on all of our computers in the next few days.
        > > >>
        > > >> It's a free utility, and I'm sure that there may be others out
        > > > there that do
        > > >> the same thing.
        > > >>
        > > >> I have seen no negative effects to date from using this
        utility.
        > I
        > > > would
        > > >> appreciate all feedback from any of the rest of you who may
        > choose
        > > > to run
        > > >> this utility.
        > > >>
        > > >> Dan Vester,
        > > >> Prescott Arizona FHC
        > > >>
        > > >>
        > > >>
        > > >> -----Original Message-----
        > > >> From: fhctech@yahoogroups.com [mailto:fhctech@yahoogroups.com]
        On
        > > > Behalf Of
        > > >> lemow@
        > > >> Sent: Wednesday, February 07, 2007 7:01 AM
        > > >> To: fhctech@yahoogroups.com
        > > >> Subject: Re: [fhctech] Re: LANdesk caused problems?
        > > >>
        > > >>
        > > >>
        > > >> Brother Shaw,
        > > >> Thank you very much for your quick reply. We continue to have
        > > > slowdown
        > > >> problems at our FHC. Will you please let us know when the new
        > > > Landesk has
        > > >> been implemented?
        > > >> Lynn E. Mower
        > > >>
        > > >> > ----- Original Message -----
        > > >> > From: "Lynn Shaw" <shawlh@ldschurch. <mailto:shawlh%
        > > > 40ldschurch.org> org>
        > > >> > To: lemow@email. <mailto:lemow%40email.com> com,
        > > > fhctech@yahoogroups
        > > >> <mailto:fhctech%40yahoogroups.com> .com
        > > >> > Subject: [fhctech] Re: LANdesk caused problems?
        > > >> > Date: Wed, 31 Jan 2007 13:24:33 -0700
        > > >> >
        > > >> >
        > > >> > All,
        > > >> >
        > > >> > I am aware of three possible things that may be causing this
        > type
        > > > of
        > > >> problem:
        > > >> >
        > > >> > 1) A software inventory scan is taking place on
        > > >> > a system with a slow hard drive
        > > >> > and it is causing a bottleneck.
        > > >> > >> The frequency a software inventory scan was set to take
        > place
        > > > was every
        > > >> 7
        > > >> > days. As of today, the software inventory scan frequency has
        > been
        > > > changed
        > > >> to
        > > >> > every 180 days.
        > > >> >
        > > >> > 2) There is a known defect with the currently deployed
        LANDesk
        > > > Inventory
        > > >> > Scanner (ldiscn32.exe) that causes, on some systems, the CPU
        > > > utlization to
        > > >> be
        > > >> > maxed out.
        > > >> > >> This problem should be resolved as we update the LANDesk
        > > > servers and
        > > >> deploy
        > > >> > an automatic agent update. We're hoping to
        > > >> > have this implemented by the end of
        > > >> > next week.
        > > >> >
        > > >> > 3) The Symantec Antivirus is running "Administrative Scans"
        of
        > the
        > > >> computer
        > > >> > system which may cause the system to be sluggish.
        > > >> > >> Up to this point in time, the Symantec policy has been
        > locked
        > > > down so
        > > >> that
        > > >> > the two Administrative Scans could not be modified, deleted,
        or
        > > > configured
        > > >> to
        > > >> > run at different times. We are in the process
        > > >> > of changing it so that ALL of the
        > > >> > antivirus configuration can be modified by the FHC. We are
        > hoping
        > > > this to
        > > >> be
        > > >> > resolved by the end of this week.
        > > >> >
        > > >> > Once the updated LANDesk configuration has been
        > > >> > deployed, the following changes
        > > >> > will also be implemented:
        > > >> > - Hardware Inventory Scans (ldiscn32.exe; < 30 secs to run,
        > very
        > > > low
        > > >> system
        > > >> > impact), currently scheduled to run once per day, will run
        once
        > > > every 4
        > > >> days
        > > >> > - LANDesk check-in for updates (amclient.exe;
        > > >> > usually very low system impact),
        > > >> > currently scheduled to run every 6 hours, will run once per
        day
        > > >> > - Vulnerability Scan (vulscan.exe; low system impact),
        > currently
        > > > scheduled
        > > >> to
        > > >> > run once every 2 days, will run once every 30 days
        > > >> >
        > > >> > There are no other LANDesk or Symantec related causes that
        we
        > are
        > > > aware
        > > >> of.
        > > >> > Use standard troubleshooting to pursue other possible
        problems.
        > > > You can
        > > >> check
        > > >> > the Task Manager to see which processes are using the most
        CPU
        > > > percentage,
        > > >> and
        > > >> > select other additional parameters to monitor the hard drive
        > > > usage under
        > > >> the
        > > >> > View - Select Columns menu.
        > > >> >
        > > >> > The main Symantec Antivirus process to look for is
        > rtvscan.exe. It
        > > >> provides
        > > >> > the Auto-Protect (real-time) protection and also runs the
        full
        > > > scans.
        > > >> >
        > > >> > An official memo will be released to FHC
        > > >> > directors via the ldsmail.net accounts
        > > >> > before the LANDesk update occurs. We also hope to have a
        custom
        > > > LANDesk
        > > >> > configuration at that time for those FHCs that use drive
        > > > protection
        > > >> software.
        > > >> >
        > > >> > I hope this information is helpful.
        > > >> >
        > > >> > Sincerely,
        > > >> >
        > > >> > Brother Lynn Shaw
        > > >> > LANDesk Specialist
        > > >> > FamilySearch Support, CHQ
        > > >> >
        > > >> >
        > > >> >
        > > >> > >>> On 1/31/2007 at 10:15 AM, in message
        > > >> > <20070131171505.
        > > >> <mailto:20070131171505.4D51683BE2%40ws1-1a.us4.outblaze.com>
        > > >> 4D51683BE2@>, <lemow@email.
        > > >> <mailto:lemow%40email.com> com>
        > > >> > wrote:
        > > >> > Brother Shaw,
        > > >> > We have been having problems with our FHC computers running
        > > > extremely
        > > >> slow. I
        > > >> > don't know if it is caused by LANdesk or not.
        > > >> >
        > > >> > I have had reported to me that on Sunday mornings a Sunday
        > School
        > > > class
        > > >> has to
        > > >> > wait nearly the entire class time for the computers to become
        > > > useable.
        > > >> >
        > > >> > I have had reported to me that some week days the computers
        > work
        > > > extremely
        > > >> > slow.
        > > >> >
        > > >> > Yesterday I saw this for myself for the first
        > > >> > time. It would take five minutes
        > > >> > for PAF to load and five more minutes for the next step.
        > > >> >
        > > >> > I don't know if this is caused by LANdesk or not. That is the
        > > > problem. I
        > > >> > spent my entire four hour shift trying to
        > > >> > findout what was taking place without
        > > >> > any success.
        > > >> >
        > > >> > What I am suggesting is that whenever LANdesk
        > > >> > is doing anything to the computer
        > > >> > a notice is placed on the screen to that effect. The note
        could
        > > > say:
        > > >> >
        > > >> > LANdesk is currently updating this computer
        > > >> > from church headquarters.
        > > >> > While this is taking place, applications
        > > >> > may run extremely slow.
        > > >> > When LANdesk is finished,this note will be removed.
        > > >> > Please be patient.
        > > >> >
        > > >> > That will let us know that LANdesk is causing
        > > >> > the problem and we will not spend
        > > >> > fruitless hours trying to fix something that is not broken.
        > > >> >
        > > >> > Also, is there some way that we can look to see if it is
        > actually
        > > > LANdesk
        > > >> that
        > > >> > is causing the slow down?
        > > >> >
        > > >> > What is the schedule used by LANdesk to update the computers
        at
        > > > our
        > > >> specific
        > > >> > center?
        > > >> >
        > > >> > Lynn E. Mower
        > > >> > Layton Utah Valley View FHC
        > > >> >
        > > >> > ----------------------------------------------------------
        > > >> > NOTICE: This email message is for the sole use
        > > >> > of the intended recipient(s) and may contain
        > > >> > confidential and privileged information. Any
        > > >> > unauthorized review, use, disclosure or
        > > >> > distribution is prohibited. If you are not the
        > > >> > intended recipient, please contact the sender
        > > >> > by reply email and destroy all copies of the
        > > >> > original message.
        > > >>
        > > >> >
        > > >>
        > > >>
        > > >>
        > > >>
        > > >>
        > > >> __________ NOD32 2044 (20070207) Information __________
        > > >>
        > > >> This message was checked by NOD32 antivirus system.
        > > >> http://www.eset.com ( http://www.eset.com/ )
        > > >>
        > > >
        > > >
        > > >
        > > >
        > > > Home Page: http://fhctech.org/
        > > > Community email addresses:
        > > > Post message: fhctech@yahoogroups.com
        > > > Subscribe: fhctech-subscribe@yahoogroups.com
        > > > Unsubscribe: fhctech-unsubscribe@yahoogroups.com
        > > > List owner: Rick@
        > > > Shortcut URL to Yahoo! group page:
        > > > http://groups.yahoo.com/group/fhctech
        > > > Yahoo! Groups Links
        > > >
        > > >
        > > >
        > >
        > > ------------------------------------------------------------------
        --
        > --
        > > NOTICE: This email message is for the sole use of the intended
        > recipient(s) and may contain confidential and privileged
        information.
        > Any unauthorized review, use, disclosure or distribution is
        > prohibited. If you are not the intended recipient, please contact
        the
        > sender by reply email and destroy all copies of the original
        message.
        > >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.