Tech support hardware swap policy - Revision history

Koopa at 21:31, 24 February 2011

2011-02-24T21:31:19Z

Rfs at 01:33, 7 July 2010

2010-07-07T01:33:55Z

Evilgold: /* Policy */

2009-06-12T00:44:03Z

Policy

Evilgold: /* Policy */

2009-05-29T01:46:22Z

Policy

Evilgold at 01:46, 29 May 2009

2009-05-29T01:46:04Z

Badamski: /* Policy */

2009-05-29T01:25:24Z

Policy

Badamski: /* Policy */

2009-05-29T01:10:25Z

Policy

Badamski: /* Policy */

2009-05-29T01:09:30Z

Policy

Badamski: /* Policy */

2009-05-29T01:07:25Z

Policy

Badamski: /* Policy */

2009-05-29T00:33:59Z

Policy

← Older revision		Revision as of 21:31, 24 February 2011
Line 33:		Line 33:
	* Exceptions/Ramifications		* Exceptions/Ramifications
	* Etc...		* Etc...
		+	[[Category:Tech support]]

@@ Line 1: / Line 1: @@
 {{policy in development}}
 ==Policy==
 ''Body that set the policy(s) on [lists.freegeek_meeting_Minutes Date Adopted].''

@@ Line 12: / Line 12: @@
 * System does not turn on at all
 * Motherboard is bad (blown caps, or otherwise non-memory/video related issues)
 User modified boxes:

@@ Line 10: / Line 10: @@
 Conditions for swapping an entire system (box):
- * System does not turn on at all
+* System does not turn on at all
- * Motherboard is bad (blown caps, or otherwise non-memory/video related issues)
+* Motherboard is bad (blown caps, or otherwise non-memory/video related issues)
 User modified boxes:

@@ Line 14: / Line 14: @@
 User modified boxes:
- If a user has made hardware modifications to a system, it's hard for us to tell if the
+If a user has made hardware modifications to a system, it's hard for us to tell if the
- issues they are having is our fault or theirs. We also need to avoid situations where a
+issues they are having is our fault or theirs. We also need to avoid situations where a
- user may try to pass off their own bad hardware (memory, video card, etc) as ours in order
+user may try to pass off their own bad hardware (memory, video card, etc) as ours in order
- to get an exchange. If a user has not taken the build class then we may not want to make an
+to get an exchange. If a user has not taken the build class then we may not want to make an
- exchange unless its clearly unrelated to what the user has modified.
+exchange unless its clearly unrelated to what the user has modified.
 Once we determine that we are going to swap a system we need to:
- * Inform the user
+* Inform the user
- * Find a similarly spec'd system to swap
+* Find a similarly spec'd system to swap
- * Install the users old drive into the new system (unless old drive is bad or the user
+* Install the users old drive into the new system (unless old drive is bad or the user doesn't care)
-   doesn't care)
+* Install and setup any additional hardware that was in the old system (wireless cards, modems, etc) and test
- * Install and setup any additional hardware that was in the old system (wireless cards,
+* Send old machine to Build to QC or recycling
 ==Notes==

@@ Line 7: / Line 7: @@
 ''Body that set the policy(s) on [lists.freegeek_meeting_Minutes Date Adopted].''
-From time to time tech support will encounter hardware that either in part or in whole needs to be changed. Sometimes systems have things fail that would simply take too much time for us to troubleshoot and repair, usually they can be fixed or further diagnosed elsewhere at a later time.
+From time to time Tech Support will encounter hardware that either in part or in whole needs to be changed. Sometimes systems have things fail that would simply take too much time for us to troubleshoot and repair, usually they can be fixed or further diagnosed elsewhere at a later time.
 Conditions for swapping an entire system (box):

@@ Line 14: / Line 14: @@
 User modified boxes:
-If a user has made hardware modifications to a system, its hard for us to tell if the issues they are having is our fault or not. We also need to avoid cases where a user may try to pass off their own bad hardware (memory, video card, etc) as ours in order to get an exchange. If a user has not taken the build class then we may not want to make an exchanges unless its clearly unreleated to what the user has modified.
+If a user has made hardware modifications to a system, its hard for us to tell if the issues they are having is our fault or not. We also need to avoid cases where a user may try to pass off their own bad hardware (memory, video card, etc) as ours in order to get an exchange. If a user has not taken the build class then we may not want to make an exchanges unless its clearly unrelated to what the user has modified.
-Once we determin that we are going to swap a system we need to:
+Once we determine that we are going to swap a system we need to:
-*inform the user
+ * Inform the user
-*find a similarly spec'd system to swap for
+ * Find a similarly spec'd system to swap for
-*install the users old drive into the new system (unless old drive is bad/user doesnt care)
+ * Install the users old drive into the new system (unless old drive is bad/user doesn't
-*install and setup any additional hardware that was in the old system (wireless cards, modems, etc) and test
+   care)
 *send old machine to build for re-QCing or recycling.