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

RE: [fhctech] Temple Ready for Windows Installation (and welcome to our world)

Expand Messages
  • Bill Henderson
    Isn t tribal knowledge great!! Tribal knowledge is where nothing is ever written down, just passed from person to person. Oh! no one passed the tribal
    Message 1 of 3 , Oct 31, 2006
    • 0 Attachment
      Isn't tribal knowledge great!!  Tribal knowledge is where nothing is ever written down, just passed from person to person.  Oh! no one passed the tribal knowledge down to you?  Well that is one of the weaknesses of that system.
       
      Some months ago, I brought up the idea of each FHC having a System Administrator's Manual (SAM).  If Kress' predecessor had developed one, or even a beginnings of one, most of those headaches would not have occurred.  One of the first things any FHC support person should do is locate the equipment and resources he/she needs to do the job.  My SAM has a page of quick reference numbers at the front of the manual, and a locations guide under the General tab.  I don't know if the message threads from March and April are still available, but if so, you may want to browse through them.  I suppose there should be a section on the FHCtech.org website for building a SAM.  The second thing I did was put things in a standard location (or locations) to reduce the number of places required to look.  Third, we trashed things we no longer needed to avoid clutter and confusion. 
       
      As I mentioned back then; Congratulations, by developing your own SAM you have the opportunity to truly learn and know your FHC.  The fellow behind you (who will have your SAM to follow) won't learn as much as you will, because he didn't have to put forth the effort.  I have attached a copy of my Table of Contents to give you a design to follow.   Good luck.
       
      Bill H.

      Dana Repouille <drepouille@...> wrote:
      Kress,
      Welcome to the club! Several of us on this list are computer professionals
      of various types, and we have all gone through your frustration. We have all
      asked FHC staffs, "Where are your installation disks, installation
      instructions, passwords, etc?" Our requests are usually met with blank
      stares, and we have to dig through drawers, closets, and boxes.

      The instructions on FHCTech.org are not perfect or complete, but they are
      much better than anything I have received from Church HQ. I have been able
      to follow the instructions enough to install the DOS FamilySearch and
      TempleReady for Windows in a networked environment. You efforts to provide
      better instructions are certainly welcome.

      The files at
      http://groups. yahoo.com/ group/fhctech/ files/
      and the message archive at
      http://groups. yahoo.com/ group/fhctech/ messages
      are valuable supplements to FHCTech.org.

      Like you, I have repeatedly told the FHC staff that my job is to install and
      maintain the systems, not to train them to use the applications. They never
      believe me. Over time, I have had to learn a little about each application
      just to be able to test each one and ensure it is working properly. Somehow,
      that has qualified me to be an "expert" on these applications.

      When my wife was called to be the Stake FHC Director three years ago, I
      learned with her about all the resources available to FHC directors. She
      assembled an Operations Guide for her FHC staff, which they of course
      ignore, because they can just call her or me for help. It seems that nobody
      likes to read anymore. My wife and I have become experts and legends around
      our stake simply because we take the time to read the documents provided,
      and to experiment with the software to see how it works. Even though her
      calling as Stake FHC Director does not including training the other four FHC
      Directors and their staffs, guess what? That is what they all expect her to
      do. Everyone assumes that the Stake FHC Director is supposed to train all
      the Ward and Branch FHC Directors. I fear we may never be released.

      I "train" new FHC directors by rattling off a list of things they need to do
      and read and request from HQ. (No, training is not in my job description,
      but they appreciate the help.) Many FHC directors and staff members simply
      throw up their hands in frustration with all the fancy technology, and go
      back to their film readers. Some who are comfortable with "the old ways" of
      doing things refuse to change. For example, I have found it extremely
      difficult to convince people to STOP using the "Export for TempleReady"
      feature of PAF to create a GEDCOM file. My wife and I plead with people to
      bring a backup of their PAF files to the FHC, not just a small GEDCOM
      extract. We try to teach them to lauch TempleReady directly from the PAF
      Tools menu, but they usually go back to the old way, using GEDCOM files.
      Argh.

      I find that if I sit at home waiting for someone from the five FHCs I
      support to call me with a question or problem, nothing happens. I have to be
      proactive and either call someone or make the rounds to see what is broken.
      I have begged the FHC directors and staff members to maintain a trouble log,
      and record everything that goes wrong with the computers in sufficient
      detail for me to reproduce the problems. Of course, they ignore my pleas. I
      often walk into a FHC after several months absence to find several major
      problems waiting to be fixed. This despite the fact that I leave my business
      card everywhere in plain sight. Sigh.

      By the way, as the Stake Executive Secretary, I also post my name and cell
      phone number on the bulletin board of every chapel, so people can call me to
      request appointments with the Stake President. However, it seems that no
      one, including the bishops, knows my cell phone number. They usually call my
      home number, and my kids lose the messages.

      Again, welcome to our Brotherhood.
      Dana Repouille
      Council Bluffs Iowa Stake Technology Specialst, Stake Executive Secretary,
      and husband of the Stake FHC...
      (I also do Windows.)



      We have the perfect Group for you. Check out the handy changes to Yahoo! Groups.

    • carolannpierson
      Hi Bill, Your TOC attachment didn t get attched to the message digest or your message. Could you please send me a copy of the Network TOC? I am the Systems
      Message 2 of 3 , Nov 13, 2006
      • 0 Attachment
        Hi Bill,

        Your TOC attachment didn't get attched to the message digest or your
        message. Could you please send me a copy of the Network TOC? I am the
        Systems Admin/Computer Specialist for the Manteca FHC. We have put a
        book together using the info from the fhctech.org site, but I would like
        to see what you include in your SAM.

        Thanks a lot...Carol Pierson


        --- In fhctech@yahoogroups.com, Bill Henderson <wch3120@...> wrote:
        >
        > Isn't tribal knowledge great!! Tribal knowledge is where nothing is
        ever written down, just passed from person to person. Oh! no one passed
        the tribal knowledge down to you? Well that is one of the weaknesses of
        that system.
        >
        > Some months ago, I brought up the idea of each FHC having a System
        Administrator's Manual (SAM). If Kress' predecessor had developed one,
        or even a beginnings of one, most of those headaches would not have
        occurred. One of the first things any FHC support person should do is
        locate the equipment and resources he/she needs to do the job. My SAM
        has a page of quick reference numbers at the front of the manual, and a
        locations guide under the General tab. I don't know if the message
        threads from March and April are still available, but if so, you may
        want to browse through them. I suppose there should be a section on the
        FHCtech.org website for building a SAM. The second thing I did was put
        things in a standard location (or locations) to reduce the number of
        places required to look. Third, we trashed things we no longer needed to
        avoid clutter and confusion.
        >
        > As I mentioned back then; Congratulations, by developing your own SAM
        you have the opportunity to truly learn and know your FHC. The fellow
        behind you (who will have your SAM to follow) won't learn as much as you
        will, because he didn't have to put forth the effort. I have attached a
        copy of my Table of Contents to give you a design to follow. Good luck.
        >
        > Bill H.
        >
        > Dana Repouille drepouille@... wrote:
        > Kress,
        > Welcome to the club! Several of us on this list are computer
        professionals
        > of various types, and we have all gone through your frustration. We
        have all
        > asked FHC staffs, "Where are your installation disks, installation
        > instructions, passwords, etc?" Our requests are usually met with blank
        > stares, and we have to dig through drawers, closets, and boxes.
        >
        > The instructions on FHCTech.org are not perfect or complete, but they
        are
        > much better than anything I have received from Church HQ. I have been
        able
        > to follow the instructions enough to install the DOS FamilySearch and
        > TempleReady for Windows in a networked environment. You efforts to
        provide
        > better instructions are certainly welcome.
        >
        > The files at
        > http://groups.yahoo.com/group/fhctech/files/
        > and the message archive at
        > http://groups.yahoo.com/group/fhctech/messages
        > are valuable supplements to FHCTech.org.
        >
        > Like you, I have repeatedly told the FHC staff that my job is to
        install and
        > maintain the systems, not to train them to use the applications. They
        never
        > believe me. Over time, I have had to learn a little about each
        application
        > just to be able to test each one and ensure it is working properly.
        Somehow,
        > that has qualified me to be an "expert" on these applications.
        >
        > When my wife was called to be the Stake FHC Director three years ago,
        I
        > learned with her about all the resources available to FHC directors.
        She
        > assembled an Operations Guide for her FHC staff, which they of course
        > ignore, because they can just call her or me for help. It seems that
        nobody
        > likes to read anymore. My wife and I have become experts and legends
        around
        > our stake simply because we take the time to read the documents
        provided,
        > and to experiment with the software to see how it works. Even though
        her
        > calling as Stake FHC Director does not including training the other
        four FHC
        > Directors and their staffs, guess what? That is what they all expect
        her to
        > do. Everyone assumes that the Stake FHC Director is supposed to train
        all
        > the Ward and Branch FHC Directors. I fear we may never be released.
        >
        > I "train" new FHC directors by rattling off a list of things they need
        to do
        > and read and request from HQ. (No, training is not in my job
        description,
        > but they appreciate the help.) Many FHC directors and staff members
        simply
        > throw up their hands in frustration with all the fancy technology, and
        go
        > back to their film readers. Some who are comfortable with "the old
        ways" of
        > doing things refuse to change. For example, I have found it extremely
        > difficult to convince people to STOP using the "Export for
        TempleReady"
        > feature of PAF to create a GEDCOM file. My wife and I plead with
        people to
        > bring a backup of their PAF files to the FHC, not just a small GEDCOM
        > extract. We try to teach them to lauch TempleReady directly from the
        PAF
        > Tools menu, but they usually go back to the old way, using GEDCOM
        files.
        > Argh.
        >
        > I find that if I sit at home waiting for someone from the five FHCs I
        > support to call me with a question or problem, nothing happens. I have
        to be
        > proactive and either call someone or make the rounds to see what is
        broken.
        > I have begged the FHC directors and staff members to maintain a
        trouble log,
        > and record everything that goes wrong with the computers in sufficient
        > detail for me to reproduce the problems. Of course, they ignore my
        pleas. I
        > often walk into a FHC after several months absence to find several
        major
        > problems waiting to be fixed. This despite the fact that I leave my
        business
        > card everywhere in plain sight. Sigh.
        >
        > By the way, as the Stake Executive Secretary, I also post my name and
        cell
        > phone number on the bulletin board of every chapel, so people can call
        me to
        > request appointments with the Stake President. However, it seems that
        no
        > one, including the bishops, knows my cell phone number. They usually
        call my
        > home number, and my kids lose the messages.
        >
        > Again, welcome to our Brotherhood.
        > Dana Repouille
        > Council Bluffs Iowa Stake Technology Specialst, Stake Executive
        Secretary,
        > and husband of the Stake FHC...
        > (I also do Windows.)
        >
        >
        >
        >
        >
        >
        > ---------------------------------
        > We have the perfect Group for you. Check out the handy changes to
        Yahoo! Groups.
        >
      • Bill Henderson
        Sorry my TOC didn t work, here it is again. I have had trouble sending attachments through the FHCtech.org forum before. Hope this on gets through. Bill H.
        Message 3 of 3 , Nov 14, 2006
        • 0 Attachment
          Sorry my TOC didn't work, here it is again.  I have had trouble sending attachments through the FHCtech.org forum before.  Hope this on gets through.
           
          Bill H.

          carolannpierson <carolannpierson@...> wrote:

          Hi Bill,

          Your TOC attachment didn't get attched to the message digest or your
          message. Could you please send me a copy of the Network TOC? I am the
          Systems Admin/Computer Specialist for the Manteca FHC. We have put a
          book together using the info from the fhctech.org site, but I would like
          to see what you include in your SAM.

          Thanks a lot...Carol Pierson

          --- In fhctech@yahoogroups .com, Bill Henderson <wch3120@... > wrote:
          >
          > Isn't tribal knowledge great!! Tribal knowledge is where nothing is
          ever written down, just passed from person to person. Oh! no one passed
          the tribal knowledge down to you? Well that is one of the weaknesses of
          that system.
          >
          > Some months ago, I brought up the idea of each FHC having a System
          Administrator' s Manual (SAM). If Kress' predecessor had developed one,
          or even a beginnings of one, most of those headaches would not have
          occurred. One of the first things any FHC support person should do is
          locate the equipment and resources he/she needs to do the job. My SAM
          has a page of quick reference numbers at the front of the manual, and a
          locations guide under the General tab. I don't know if the message
          threads from March and April are still available, but if so, you may
          want to browse through them. I suppose there should be a section on the
          FHCtech.org website for building a SAM. The second thing I did was put
          things in a standard location (or locations) to reduce the number of
          places required to look. Third, we trashed things we no longer needed to
          avoid clutter and confusion.
          >
          > As I mentioned back then; Congratulations, by developing your own SAM
          you have the opportunity to truly learn and know your FHC. The fellow
          behind you (who will have your SAM to follow) won't learn as much as you
          will, because he didn't have to put forth the effort. I have attached a
          copy of my Table of Contents to give you a design to follow. Good luck.
          >
          > Bill H.
          >
          > Dana Repouille drepouille@. .. wrote:
          > Kress,
          > Welcome to the club! Several of us on this list are computer
          professionals
          > of various types, and we have all gone through your frustration. We
          have all
          > asked FHC staffs, "Where are your installation disks, installation
          > instructions, passwords, etc?" Our requests are usually met with blank
          > stares, and we have to dig through drawers, closets, and boxes.
          >
          > The instructions on FHCTech.org are not perfect or complete, but they
          are
          > much better than anything I have received from Church HQ. I have been
          able
          > to follow the instructions enough to install the DOS FamilySearch and
          > TempleReady for Windows in a networked environment. You efforts to
          provide
          > better instructions are certainly welcome.
          >
          > The files at
          > http://groups. yahoo.com/ group/fhctech/ files/
          > and the message archive at
          > http://groups. yahoo.com/ group/fhctech/ messages
          > are valuable supplements to FHCTech.org.
          >
          > Like you, I have repeatedly told the FHC staff that my job is to
          install and
          > maintain the systems, not to train them to use the applications. They
          never
          > believe me. Over time, I have had to learn a little about each
          application
          > just to be able to test each one and ensure it is working properly.
          Somehow,
          > that has qualified me to be an "expert" on these applications.
          >
          > When my wife was called to be the Stake FHC Director three years ago,
          I
          > learned with her about all the resources available to FHC directors.
          She
          > assembled an Operations Guide for her FHC staff, which they of course
          > ignore, because they can just call her or me for help. It seems that
          nobody
          > likes to read anymore. My wife and I have become experts and legends
          around
          > our stake simply because we take the time to read the documents
          provided,
          > and to experiment with the software to see how it works. Even though
          her
          > calling as Stake FHC Director does not including training the other
          four FHC
          > Directors and their staffs, guess what? That is what they all expect
          her to
          > do. Everyone assumes that the Stake FHC Director is supposed to train
          all
          > the Ward and Branch FHC Directors. I fear we may never be released.
          >
          > I "train" new FHC directors by rattling off a list of things they need
          to do
          > and read and request from HQ. (No, training is not in my job
          description,
          > but they appreciate the help.) Many FHC directors and staff members
          simply
          > throw up their hands in frustration with all the fancy technology, and
          go
          > back to their film readers. Some who are comfortable with "the old
          ways" of
          > doing things refuse to change. For example, I have found it extremely
          > difficult to convince people to STOP using the "Export for
          TempleReady"
          > feature of PAF to create a GEDCOM file. My wife and I plead with
          people to
          > bring a backup of their PAF files to the FHC, not just a small GEDCOM
          > extract. We try to teach them to lauch TempleReady directly from the
          PAF
          > Tools menu, but they usually go back to the old way, using GEDCOM
          files.
          > Argh.
          >
          > I find that if I sit at home waiting for someone from the five FHCs I
          > support to call me with a question or problem, nothing happens. I have
          to be
          > proactive and either call someone or make the rounds to see what is
          broken.
          > I have begged the FHC directors and staff members to maintain a
          trouble log,
          > and record everything that goes wrong with the computers in sufficient
          > detail for me to reproduce the problems. Of course, they ignore my
          pleas. I
          > often walk into a FHC after several months absence to find several
          major
          > problems waiting to be fixed. This despite the fact that I leave my
          business
          > card everywhere in plain sight. Sigh.
          >
          > By the way, as the Stake Executive Secretary, I also post my name and
          cell
          > phone number on the bulletin board of every chapel, so people can call
          me to
          > request appointments with the Stake President. However, it seems that
          no
          > one, including the bishops, knows my cell phone number. They usually
          call my
          > home number, and my kids lose the messages.
          >
          > Again, welcome to our Brotherhood.
          > Dana Repouille
          > Council Bluffs Iowa Stake Technology Specialst, Stake Executive
          Secretary,
          > and husband of the Stake FHC...
          > (I also do Windows.)
          >
          >
          >
          >
          >
          >
          > ------------ --------- --------- ---
          > We have the perfect Group for you. Check out the handy changes to
          Yahoo! Groups.
          >



          Everyone is raving about the all-new Yahoo! Mail beta.

        Your message has been successfully submitted and would be delivered to recipients shortly.