Changing+To+New+PC+at+C3H

toc

Status
Despite the proclamations by Microsoft, any PC with daily use will likely need major Windows maintenance, likely re-installed (rebuilt) within 2-3 years. This is not something any of us **//like//** to do, it becomes necessary due to crashes, misbehaving software, or the inevitable decline in performance of a Windows PC that has been run constantly for years. (We're not going to get into far less need for such intrusive rebuilds with Linux or MacOS PCs...) Windows/XP is up to 2 1/2+ years on average, Windows/2000 perhaps 2 years, jury is still out on Windows Vista.

Network Station alternatives
One way to deal with this issue that is very popular in small to mid-size churches that have more than a few PCs is to install software on the older PCs to create [|Thinstations] or use a thin client such as setting up Remote Desktop on XP Pro workstations. The cost and reliability are now at a point where we believe it is suitable for C3HUU and other small churches.

NOTE: Microsoft has also released Remote Desktop client software for Windows/2000 or XP or Vista PCs. However, you still need to maintain the Microsoft operating system to use this piece of software. On the past two desktop PCs that developed Windows problems, the Remote Desktop software wouldn't work well, but rebooting the same PC with a [|Thinstation] CD worked fine.

Focus on Thinstation
Though there are several alternatives in this space, we've focussed effort on using older PCs to create [|Thinstations], because:
 * 1) [|Thinstation] software is well documented, has a large user base and good support tools,
 * 2) [|Thinstation] software is straightforward to setup (notice, we didn't say EASY, but straightforward)
 * 3) [|Thinstation] is meant to be run on 4-6 year old PCs
 * 4) [|Thinstation] software is free!

Rebuilding a PC for Staff
Until a [|Thinstation] setup is workable, when a staff member has a PC that needs to be rebuilt here is a proposed process. This process has been updated over the past few years as we have had to rebuild 6 PCs since 2001. This assumes the original PC hardware is still in 100% working order and install media is available. At this time (3Q2009), we are evaluating Windows 7. One staff PC at C3HUU is running Vista.

IF the "Problem PC" can still boot:
>> Setup staff member to share an existing Windows XP Pro or Vista PC with enough power to run the staff member's jobs too >>>> [|pricing for Avast!], which has changed policies on non-profit use. AVG has not, and with the recent releases better using CPU, we are migrating back to [|AVG Free].
 * 1) Install the C3H Backup PC (currently the PC in the Soundroom) for the C3H Staff member whose PC needs to be re-installed, hook it up with the KVM switch which allows two PCs to be hooked up to one monitor and keyboard.
 * Switching between the two PCs is accomplished by tapping the 'Scroll-Lock' key twice and then the 'Up Arrow' key or 'Down Arrow' key.
 * Give the staff member a chance to try switching between the two PCs in case there are questions about how to use this
 * 1) Show the staff member how to save their files on the C3H Snap Server which is accessible to ALL C3H PCs once they are hooked up on the C3H Ethernet network. Once files are on the Snap Server NAS, they are available to any and all C3H PCs using the staff member's public or private space on the Snap Server NAS.
 * Alternative: install the Mirra software and show that the files that were in "My Documents" folder on the old PC are now accessible from the Backup PC
 * 1) Allow the staff member enough time to transfer files and get comfortable using the new PC, then
 * 2) Remove the Problem PC that is to be rebuilt
 * 3) Allow the staff member a few more days before starting Windows rebuild just in case some files that are needed were not moved correctly
 * 4) Backup the Problem PC and keep the backup separate (on external USB disk or DVDs)
 * 5) Put new Operating System image on the Problem PC (can you guess which option we prefer?):
 * 6) Option A: (the way that is not quite working yet, really requires an always on, virtualized staff office server)
 * Upgrade this second PC if needed to accommodate the new load (usually only needs more memory)
 * Customize [|Thinstation] CD for staff member
 * Insert [|Thinstation] CD and diskette to PC with unstable Windows build and reboot.
 * 1) Option B (tried and true way): Start the rebuild of Windows and all the applications on the PC
 * Obtain all original installation media, especially for Windows, Microsoft Office, other key applications
 * This may take a couple of weeks unless a volunteer can commit to helping out
 * The minimum set of applications to be reinstalled:
 * 1) Windows XP standard, one system now has Vista
 * plus any special device driver installation media if it is called out.
 * 1) [|OpenOffice v3.1]
 * 2) Microsoft Office components licensed to this PC (differs on each PC, ITS would like to eliminate in favor of Open Office to save $175-250 per PC in licenses). This is trickier due to stricter licensing, ask on the [|C3HITS list] for the correct CD for the particular PC being built.
 * 3) [|Avast! anti-virus software] (as of 3Q2008) OR [|AVG Free] and activate the built-in Windows firewall
 * 1) [|Logos II workstation client] (need to get install CD from "Network" closet)
 * 2) [|TightVNC v1.3.9]
 * 3) [|Konica/Minolta Bizhub C451 software]
 * 4) HP LaserJet 2100TN printer software (built-in XP driver, use IP address 192.168.1.10 )
 * 5) Mirra Client - CDs in the Network closet. The Mirra server is approaching 4 years old, testing is underway to replace with a file sync software package using the QNAP NAS in the Network clost from software such as [|GoodSync] (base rsync and Unison software was tried, not very "user friendly").
 * 6) Retrospect 6.5 Backup client - CDs in the Network closet
 * After install of above, verify that the rebuilt PC is stable, accesses the network when connected to ethernet at C3HUU, and runs these applications well.
 * Install any upgraded hardware as per the agreed upon list.
 * 1) Return the PC to the staff member, installed again with the KVM switch so that the staff member may continue to use either the Backup PC or the original PC with reinstalled software and any upgraded hardware.
 * 2) Remove the Backup PC after a few weeks or when the C3H Staff member tires of having two PCs at his/her desk!
 * 3) Return the Backup PC to the Soundroom as soon as possible.

If the Problem PC won't boot:

 * 1) Insure that all the software listed in step 5.1 Option B above is installed on the Backup PC
 * 2) Install the Backup PC for the C3H Staff member
 * 3) Remove the Problem PC and attempt to recover data from the Problem PC hard disk
 * If not successful recovering data from the had disk, then attempt to recover the "Documents and Settings" folder (for XP) to alternate media (USB hard disk) from the Mirra Backup server
 * Mount the USB hard disk on the Backup PC with data from the My Documents folder for the C3H Staff member and allow them to copy the documents that they believe they need to the Backup PC
 * 1) The Backup PC becomes the Staff Member PC
 * 2) Rebuild the Problem PC and return it to C3H

With [|Thinstation], the number of PCs to be maintained can be reduced, however we will purchase larger PCs capable of hosting multiple users. Each [|Thinstation] terminal can be set to log into a different PC should the first PC fail.

Note: at this time we DO NOT recommend use of tools such as PCAnywhere or GotoMyPC to remotely access the PC assigned to staff. Using these tools poses a risk that data that is on the private network of C3H PCs may be visible outside of C3HUU. This is especially true of using Logos Church Management System (ChMS). Future ChMSs are being evaluated for their remote access capabilities.

At this time C3H IT Services and many church IT professionals believe use of online applications with appropriate use of limited access have appropriate security for all but the most sensitive financial or personal spreadsheets, documents, or presentations. Sensitive documents should only be stored locally on PCs on the C3H Network. If USB devices are used, please insure their physical security or password protect the documents.