Again, I don’t claim to take good notes, but there is some stuff I want to remember here. These are just rough notes I take while we’re talking.
Introductions – IT people from churches all over the country – churches range from 1000 people to 19,000. Also representatives from Blackbaud, MBS, & others. 2 churches – 1000-1999, 9 churches 2000-3999, 17 over 4000. Tony surveyed the entire group – assume results will be on Tony’s site.
Virtualization – memory is key. Perimeter used existing dual processor boxes, including a SAN – recommended 4GB per core. For VMotion, must have consistent server/processor for “live” motion, but if you power it down and move it, it doesn’t matter. What types of things are people virtualizing? Almost everything. P2V works great. Only downside is you’re bringing all the legacy “stuff” along with it, instead of bringing up a brand new clean install. Planning, research and training is key. Dedicate some boxes and take some time. Perimeter running everything on VMWare except backup & Exchange. VMWare told Jason to call them if they have a problem w/ a MS program. Tech support is phenomenal. Problems/limitations? Not trouble free, but mainly set it and forget it. VMWare has tremendous I/O. Also now that everything is virtual, new servers can get created in 5 minutes – they replicate like bunnies. It’s also really easy to delete an entire server. Local VMWare user’s group? Look for one! 16GB on 3 PowerEdge 2950’s and could easily use 16 more. With servers being virtual, as long as you have the VM file, you can throw them on a desktop if you have to, like if the physical box dies or the server room explodes. As long as you have the vmdk file, you can bring that server back up.
Sharepoint – stick with Sharepoint Services as long as possible, before going to Server. Lots of free add-ons. Great place to consolidate all the different databases & interfaces – EventU, Shelby, helpdesk, etc. Make simple things simple. SOAP interface with ServiceU? Many intranets came from indirect requests – not direct requests. A central repository. SharePoint 2007 more powerful than 03. Use the intranet as a resource for orientation. Many have on-staff development, but even Perimeter outsources development – currently in a SharePoint development. Also look at 1 and 1 – hosting company for hosted Sharepoint http://order.1and1.com/xml/order/Sharepoint;jsessi… – also “web host 4 life” – http://www.webhost4life.com/. Also look at dotnetnuke as alternative.
Staffing – how do you justify new positions? First ask “Are you utilizing the staff you have now?” Of course it’s better to have a more independent entity recommend the need for additional staff. Willowcreek has a technology advisory board. Must track metrics – how many help desk tickets per day/week/month, how long does it take to close, etc. Then you have statistical data necessary for requesting additional staff. Volunteers – Willowcreek has 800,000 sq. ft under roof, 7000 volunteers to keep it running every week. Has computer connection ministry that started with infrastructure - cabling, hardware, etc. Now is more independent ministry that takes donated computers and refurbs them (I knew I had a good idea there). Get a pool of volunteers, and then you can pick from that pool the people who have the skill set you need. Send out an email every month or 2 announcing upcoming projects and see who has the necessary skills.
