I have good intentions to put something together with guidelines I have in mind for these kind of events and things that I have learned. it's totally cool that others are "copying" this idea. I have seen someone else do this kind of thing and we got to know each other but have kind of lost touch again. His events are highly structured, where you check in, drop off your computer and leave, come back later and voila, it's fixed. My vision always was for the "customers" to hang with us and this serves 2 purposes. It allows them to show you specifically what is going on, what error messages etc or to even express in greater detail what they are experiencing. It's also a time to get to know people. Finally, it ensures that you don't end up with extra machines that might be abandoned or just slow in getting back to the church.
Ideally, your church members can use this opportunity to bring their non-churched friends and neighbors to get their computers worked on and it allows a non-believer to get a glimpse of Jesus in your service. It also can show the non-believer that these church people are ok, know how to have a good time and are not always preaching at them or condemning them.
After acquiring some old dead hardware, I made it a point of requiring everybody to take with them whatever they bring in. The church does not need to become a final resting place for other people's old hardware, in my opinion. After I ended up with stuff I had no use for, I have been very willing to carry there old dead monitor back out to their car or whatever, then advise them where they can properly dispose of it.
There's a lot I could've done better and been more prepared. I would recommend making 5 or 6 CD's of the latest download of AVG, SpyBot, C-Cleaner and other handy free utilities. We generally had 4 -5 CRT monitors with corresponding keyboards, mice and power cords. For the most part, we didn't tap into a network, but in the end, I had a switch connected. We would download the utilities onto jump drives, usually that morning. Food is always good. One thing we started doing is have the people fill out a form with name, address, email, phone, PC brand, etc and the problem. We also had them sign a legal disclaimer. This releases the church, the tech team and the PC Workshop from any liability. that way, people understand that you will do the best you can but in reality not everything can be fixed.
By the way, I built my team by doing to PC Workshop. The people that helped at the first one were really my core team.
Here's a link to a site I have begun that has links to the documents I used. I intend to grow this site into something usable.
http://sites.google.com/a/jimwalton.org/pc-workshop/Also, here's a site to links to the utilities that I like to use. It started as a Fairview Tech Team site but I am in the process of migrating into a CTM site.
http://sites.google.com/a/churchtechmat ... -UtilitiesFeel free to use this info as you wish and please continue to share your stories of your events.
Jim