• This will not be from a coders viewpoint but that of a tech head that knows the terminology
• I know this won’t be all encompassing but I trust it proves informative
• I am not a trained project manager so your mileage may vary
• I have to use outside resources

With that said, let’s dive straight in with the first part:As I said above, I’m not a project manager but I am an organised and logical person and have had plenty of experience in organising many different projects, events, plays, etc. For me the hardest part of any project is where to start but typically I start with a brain storming (some call it mind mapping) session and for this I use pen and paper and FreeMind. FreeMind is so much more flexible than pen and paper but I still prefer the tactileness (Ed: is that a word?) of the old school approach.

When running a project there are always several steps and I’m sure there are as many variations of this as there are people running projects, but my approach could be defined as this - although I admit that this mostly just happens without my thinking about the steps:

• Define and agree the objective of the project
• Brainstorm ideas
• Assess / analyse ideas
• Categorise, refine and combine ideas
• Agree way forward
• Assign, analyse, prioritise & monitor tasks
• Agree timescales
• Feedback at agreed intervals
• Above all, keep God central in the plans

So that’s my nine step approach. Some will slot easily into other areas and I can already think of more that could be added - however I firmly believe that project managing should be about facilitating and not getting mired in the process.

In future posts I intend to cover the above steps in more detail - at present I don’t know how many pots this will take up but I foresee at least three or four…

• site design and content creation
• hosting
• dealing with leadership / employing third parties
• wrap up

If there is anything I don’t cover then please give me a shout and I’ll either include it or try to find a solution.

This video is a very basic primer about how ANY church can podcast. I worked with the South Carolina Baptist Convention to make this available in their podcast series.

While there are many different ways to record, encode and post your content, this was just one way - specifically on the cheap. How does your church do it?

In short there are two main types, IDE and SATA. However these are often given alternative names and in some cases have been renamed to try and avoid confusion but in reality have only added to it. Physically the two cables are radically different in size and make up with the older IDE cable having 40 pins (some modern iterations have 80 wires but retain the 40 pins) on the end of a flat, typically grey, ribbon cable. A SATA cable on the other hand, is much more compact having only 7 (or 8 if you include the coding notch) pins.

As with any 101 we can’t totally avoid history. The IDE was originally a Western Digital design and stood for Integrated Drive Electronics. That said, I was never a huge fan of history and there are lots of other pages on the web that can give you much greater detail. Suffice to say WD invented the IDE and that has subsequently been known down
the years as:

• IDE - Integrated Drive Electronics
• EIDE - Enhanced IDE
• ATA - AT** Attachment
• ATAPI - AT Attachment Packet Interface
• ATA-1
• ATA-2 and
• PATA - Parallel ATA

It is this last that has really lead to the confusion many of my friends have today. PATA, or Parallel ATA is a retroactive name given to the IDE/AT interface back in 2003 when SATA was introduced to the market.

40 & 80 wire ATA cables

In reality, what you need to know for all of the above is that they all use the 40 pin flat ribbon cable to interface to your computer. The only change to this standard was the introduction of the 80 pin cable. This was introduced with the Ultra DMA/33 (UDMA) standard. As mentioned above, the cable doubles its number of wires to 80 but retained the same 40 pin connectivity. This allowed for backwards compatibility and meant if I purchased a UDMA drive but only used a 40 pin cable then it would gracefully degrade to the slower speed. So what did / do the extra 40 wires do? They provide what is known as capacitive coupling which in essence reduces the crosstalk across the
original 40 wires and allows for the higher data transfer rates.

The only other item to note is that all of these older style drives use a 4 pin Molex connector for power.

Serial ATA (SATA) is the relatively new boy on the block, having been released to the world in 2003. You will see it referred to as:

• SATA
  
• SATA 1
• SATA 1.5
• SATA II
  
• SATA 2
• SATA 3
• SATA 6

(colour groupings indicate these are functionally identical, just a different naming convention)

The basic requirement was to give desktop hard drives a boost in data throughput without huge increases in cost - prior to SATA the debates used to centre around why a home user would want the power, expense and confusion that was SCSI. With SATA it started to eliminate those arguments and allow home users access to the power, onfigurability
and scalability of technologies like SCSI. Choices like hot swapping or drive redundancy (also know as RAID) were suddenly within the reach of mere mortals and by extension smaller Church / Business / Non-Profit setups.

SATA cable

The cable for a SATA drive is radically different though and is only 7 pins wide with an equally compact connector. The other differences between SATA and PATA cables is that SATA is a one to one affair and the length of cable you can use is  twice that of an IDE ***. This eliminates cabling and jumper confusion and also eases cabling routes through the PC. The main issue I am faced with by friends, etc is that not all SATA drives are made equal and the problems arise when you try to connect power to them.

The early generation SATA drives still use the trusty 4 pin Molex - however more and more they are adopting the newer 15 pin wafer like connector of the data cables. Like the Molex they are keyed so as to make incorrect alignment and mis-identification harder. For those that don’t yet have the latest PSU’s cable of handling the newer power sockets directly then fear not as there are adapters that are easily and cheaply available to convert from the 4 pin Molex to the 15 pin SATA power strip.

And that, ladies and gents, is that. I trust you’ve found this useful as well as a little educational and will hopefully serve to clarify what cable you require for which hard drive.

* Should you really wish to know, then ask away and I’ll write a “HDD Cabling 201″ post - though I’m not sure even I fancy that task.
** AT was always thought to refer to the fact that it was introduced for the IBM PC/AT (Advanced Technology) family of computers but to avoid any trademark issues it was simply known as the AT Attachment or ATA.
*** Though in reality I have used far longer than the IDE specified maximum length of 45cm without problems.

Anyway, in mid April 2009, the latest upgrade was released.  No, this isn’t the long awaited MAJOR upgrade which will bring cross-platform (read: PC and Mac) functionality.  According to the forums over at the EasyWorship, that major release won’t be release till late 2009 or early 2010.  However, this release has some key fixes

• PAL DVD issues
• Erroneous “Unable to validate your serial number” Messages
• Vista Service Pack 1 issues:
  • “The following Media file appears not to be supported…” Message
  • Not building video thumbnails
  • DVD Clips not working
  • Division by zero error messages on some DVDs
  • Disney and other famous brand DVDs will now work as they did before in the 2006 verison.

The upgrade is FREE and is available HERE. To read more about the recent upgrade, visit the EW forums.

In our installation, we had been experiencing the first bullet under Vista Service Pack 1 issues.  This bug was frustrating because EW would completely lock at random times when we tried to run video clips. Post upgrade - no problems.

There are a few important upgrade notes mentioned in the forums:

• DVD clips are not cross platform compatible - . i.e. clips produced in Vista will only work on another Vista installation.
• DVD clips produced in earlier versions of EW will have to be recreated.
• All EW installations will need to be upgraded to this latest release to ensure that schedules are compatible.

I can’t stress it enough, the upgrade is FREE and will maintain the stability of your installation.

Possible Disadvantages of Google Apps

• * If you want to back up individual email boxes, you will need to obtain a separate solution to do this or work with the IMAP/POP access to download your messages locally.
• * You do not have any administration over individual messages or mailboxes outside of changing passwords. You cannot delegate access to another account or a group of accounts. For some people, this is really important. The most Google Apps lets you do is change a user’s password or tell people to share passwords. I’ve seen hints that there may be a little more functionality in the Enterprise edition, but have not personally tested that.
• * Setting up a shared calendar for everyone in the domain takes a little bit of work, though it’s gotten easier in the recent months. Setting up resources such as rooms is quite a bit more difficult than doing the same in Exchange.
• * You are at Google’s mercy for backups and restores. If you host your own email or use a dedicated email host, you may have more granular backups.  On the flip side, if you host your own email, you’re responsible for the backups so this may even out for some people.
• * Our biggest limitation – trying to send out to a large number of email addresses for bulk mailings. Google has an upper limit of 100 distinct email addresses at a time and 500 distinct email addresses per day per account.  That means that if you want to send out an email to a larger congregation, you’ll be better off with using a dedicated email service or some other notification method.  Google Apps will definitely run into some limitations.  You’ll know that the emails failed because they’ll all come back with a “failed permanently” message.
• * In order to enable each user’s POP or IMAP access or to set auto-replies or forwards, you need to log in to each account. I wanted to be sure that people were set up with IMAP access and that certain accounts had an auto-response on every email. Having to log in to each account to set this bothered me a little from an administration standpoint. Using multiple browsers helps some, but it still takes some extra time. I hope the administration side grows as Google Apps gets more popular.

For our purposes, the administration is a little awkward, but we have a small number of users. The limitations on how many emails we can send per day affects us only when we’re doing a new program or holding a new event. Other than that, the benefits far outweigh the negatives. With all of that being said, I wanted to concentrate on the next areas of concern in our migration process.

3. Migration process to Google Apps.

  For most people, this is one of the big concerns. Your users probably have a lot of emails already stored either in Exchange or in POP3 and local stores.  If your email client supports IMAP, you could simply add your Google Apps account as a new IMAP account and then drag and drop your emails from your old folders into Gmail.  If this option won’t work, there is a Google Email Uploader that may work for you. You can find the instructions here or the FAQ here. Note that this tool is designed primarily for Google Apps email and will probably not work with a normal Gmail account.

  For our purposes, we started forwarding a copy of each user’s mail as it arrived on our old web host accounts.  That let us pick up from that point and not worry about migrating those emails. It was also easier for us than logging into each account and setting up POP access to the old servers. The older email still lives in Outlook PST files for the moment, mostly because our users haven’t asked to have them migrated yet. We definitely plan to migrate them, but nobody has even mentioned missing old emails so far.  That probably says something about our use of email, but I’d rather not concentrate on that right now.

  What will work best for you depends quite a bit on how heavily each person uses email. Some may be a simple drag and drop through IMAP. Some may want to organize everything in specific categories. Do some planning with your users and you will have a much better success rate.

4. Current usage of Google Apps

  We made it easy for our staff to use by setting up some basic aliases for our domains. Google provides some suggestions for you if you want to change their default (long) URLs to something friendlier. For example, if you use Calendar, the first option you see when you choose to change the URL is calendar.yourdomain.org.  You may customize this as you see fit, but I’d recommend coming up with something easy to remember and setting up your CNAME aliases shortly afterwards.  Google makes this pretty easy by including instructions for all sorts of DNS hosts. Just follow those to add new CNAME aliases and you’ll be able to point your users to much easier to remember addresses.

  Our primary use of Google Apps is still email. We don’t do too much planning at this time, though I’m trying to encourage at least a small internal calendar for our staff and workers.  We still set up some IMAP clients for sending more richly formatted HTML messages, especially when doing announcement mailings. Because we regularly send out messages to groups of people, we have created several different Groups within the domain management piece. This lets our church administrator define a group such as “Men” or “Women” that he can use to send announcements to a targeted set of people. Google Apps allows some control there so members may email that group, only specified people may email the group, or the group is accessible to everyone.  Most of our email lists of this sort are limited to certain owners to avoid possible abuse of the address tied to the group.  Other listserv systems may be better suited to this purpose so I’d still advise looking around at your options before choosing to set up groups on Google Apps.

  Having finished the basic configuration of Google Apps, I’ve mostly had the experience now of being able to sit back and let it run.  The worst problem we had was when our users tried to set up or access their accounts on new machines. The default CAPTCHA images are pretty hard to read even for someone used to CAPTCHAs. For older users, the images are pretty hard to figure out and I’ve had to talk people through this a couple of times. However, once everyone is up and running, I don’t hear anything about email issues. In fact, most of the users like the ability to log in easily while not in the office.

5. Other benefits of Google Apps for the small church

  So what other benefits are there to Google Apps? For our church, we’re content with just email. However, I know of churches who use the Calendar and Docs areas heavily to share important internal documents. Some set up Sites within their domain for internal use and share information through those sites.  However, the biggest benefits after email are likely to be found in the Calendar and Docs areas.

  With just a little effort, your users can set up a new calendar to plan out an event or to track vacations. They can then share that calendar easily to people within the domain so others can either see the details as they arise or even help edit the calendar events. This is a great way to ensure that your event planning runs smoothly. It can also be helpful to keep track of your staff members’ appointments and allow your office workers to help them plan out their schedules. if you want, you can even set up a public-facing Event calendar that can be pushed outside of your Google Apps users.  People can subscribe to the calendar through a URL or through RSS feeds. If you have a calendar of events that changes regularly, this may be very helpful for you.

  I’ll touch on Google Docs briefly. Google Docs includes Word Processor, Spreadsheet, and Presentation modules as well as a PDF (Adobe Acrobat) viewer. Any PDF files can be viewed straight out of your Google Apps email now and then saved if you wish into your Documents.  Most common Office document formats (Word, Powerpoint, Excel) can be viewed or imported into Google Docs, though you may lose formatting along the way so the document may not appear exactly the same.  If you just need to work on a basic Word Processor, Spreadsheet, or Presentation, Google Docs can get the job done. It’s a great way to take notes and then share them easily to your users or to save an initial draft for later work when you’re not near your normal PC.

If you want to keep up with the changes to Google Apps, be sure to follow this RSS Feed. It’s a great way of getting notifications about everything that Google is rolling out to your users.

I’d love to hear from you now. What are you doing? What questions did I not answer? How do you use Google Apps for your organization?

For Him,

-Peter Schott

Whether you are a volunteer or on staff and whether you are with a mega church or small or mid-size church, here are some resources that I should have been promoting long ago.

The portal for all things church IT related:
http://citrt.org/ (CITRT = Church IT Roundtable)

Everything else I mention below is found at the main page I just mentioned.

There is a weekly call that anyone is welcome to join.  You can either just call and join the conversation or in addition to that, log in to the CITRT podcast chatroom and that will further enhance your experience.  Check the page for dates and times and instructions because it could change.
http://citpodcast.wiki.zoho.com/

Join the Twitter group #CITRT:
http://twittgroups.com/group/citrt

By far, the easiest way to plug into this community is to visit the IRC chatroom.  This is where the CITRT peeps hangout 24/7.  I used to frequent this chatroom but have not in quite awhile.  I think I’ll try to hang there more.  The beauty of this is even if you can’t sit there and actively participate, login and just let the thread roll.  When you come back, you are likely to have a wealth of information on all kinds of topics.  You will have a thread of all kinds of conversations.  Of course take some time to join in to the conversation as well.  The link below gives simple instructions to join the room.
http://jpowell.blogs.com/jason_powell_church_it/2008/01/easy-way-to-joi.html

If you don’t have time to read instructions and just have get in the chatroom NOW, click the next link for instant access:
http://embed.mibbit.com/?server=irc.freenode.net&channel=%23citrt&forcePrompt=true

I want to encourage all church IT volunteers, to jump into this community.  They are here for you and are more than willing to help out.  Plus, you have a lot to offer.  Don’t view this as a one way street where you just go there when you need something.  Get to know these men and women and contribute to the community.

Last night, Jason and I had a chance to visit and I made the point that there is a huge gap between the large/mega-church and the small to mid-size church as far as IT goes.  We began talking about how to address this issue more effectively in future roundtables.

So, get involved, plug in and be a part of the CITRT community.

In room 1, our initial list of ideas that we all came up with: (We got through 3 of the first 4)

Must Discuss

• Network Monitoring - Many solutions, hoping to find one that doesn’t require reprogramming, forensic monitoring software was suggested, called NetScout, following up with the name.
• Google Apps
• Help Desk Software - TrackIT (tickets, no threaded email), Spiceworks (has threaded email, asset tracking, help tickets tied to the asset), ServiceDesk, SysAid, HelpDeskPilot (web based, no asset tracking
• ChMS and web integration - Process more important than the tool, if not happy with current ChMS then they won’t be happy with a new one. Take time to gather requirements and document what you envision you need. Training is priority. Tony Dye has documented the process his church went through.(He also has a lot of other great documentation

High Priority

• Embedding Video in email
• Mac/PC Combo
• Remote connectivity
• Backup solutions

Medium Priority

• Live streaming
• Security Surveilance solutions
• Wireless
• Virtualization

Low Priority

• Kiosk Software
• Intranet
• Project Management
• e-learning - online leadership development
• MS Publisher
• Digital Signage solutions
• Mobile device support

Lunchtime!