CUSTOMER SUPPORT USING VIRTUAL MACHINES
A customer support system includes at least one subsystem to communicate with a customer about a problem with a customer information handling system (IHS), wherein the customer IHS includes a plurality of first customer IHS data. The plurality of first customer IHS data is received from the customer and used to create a virtual IHS having substantially the same characteristics as the customer IHS. A problem with the customer IHS is then diagnosed using the virtual IHS.
is a Continuation application to U.S. Utility application Ser. No. 11/953,431 filed Dec. 10, 2007 entitled “Customer Support Using Virtual Machines,” Attorney Docket No. 16356.1089, the disclosure of which is incorporated herein by reference in its entirety.
BACKGROUNDThe present disclosure relates generally to information handling systems, and more particularly to customer support for an information handling system.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system (IHS). An IHS generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes. Because technology and information handling needs and requirements may vary between different applications, IHSs may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in IHSs allow for IHSs to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, IHSs may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
IHS customers will typically need customer support for their IHSs sometime during the life of the IHS. Customer support for the IHS may address many different issues such as, for example, hardware issues, software issues, and/or usability issues. The provision of such customer support raises a number of issues.
Conventionally, the customer contacts a customer support provider over the phone or electronically (e.g. using an instant messaging or email system) to relay the problem and receive a solution. Such methods are time consuming and present difficulties in the determination, diagnosis, and resolution of the problem. Some customer support providers attempt to solve this problem by allowing the customer to send operating system backups to the customer support provider, but this may require a full operating system re-installation which further increases the time required for the customer support provider to deal with the problem.
Accordingly, it would be desirable to provide improved customer support.
SUMMARYAccording to one embodiment, a customer support system includes at least one subsystem to communicate with a customer about a problem with a customer IHS, wherein the customer IHS includes a plurality of first customer IHS data, to receive the plurality of first customer IHS data from the customer, to use the plurality of first customer IHS data to create a virtual IHS having substantially the same characteristics as the customer IHS, and to diagnose the problem with the customer IHS using the virtual IHS.
For purposes of this disclosure, an IHS may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an IHS may be a personal computer, a PDA, a consumer electronic device, a network server or storage device, a switch router or other network communication device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The IHS may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the IHS may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The IHS may also include one or more buses operable to transmit communications between the various hardware components.
In one embodiment, IHS 100,
The IHS includes a computer-readable medium that may include, for example, the mass storage 108, the system memory 114, removable media (e.g. optical disks, flash memory, etc.), and/or a variety of other computer-readable mediums known in the art. The computer-readable medium stores functional descriptive material such as, for example, software, computer programs, applications, and/or other data structures known in the art. Such functional descriptive material imparts functionality when encoded on the computer-readable medium. Within such functional descriptive material, computer programs define structural and functional interrelationships between such computer programs and the computer-readable medium. Such interrelationships permit the computer programs' functionality to be realized. For example, the processor 102 reads such functional descriptive material from the computer-readable medium onto the system memory 114 of the IHS 100, and the processor 102 performs its operations, in response to such material which is stored in the system memory 114 of the IHS 100. Further, the computer-readable medium is an apparatus from which the computer application is accessible by the processor 102, and the computer application is processable by the processor 102 for causing the processor 102 to perform such additional operations. In addition to reading such functional descriptive material from the computer-readable medium, the processor 102 is capable of reading such functional descriptive material from or through the network 102, which is also a computer-readable medium.
Referring now to
Each of the customers 206, 208 and 210 and the customer support provider 204 includes a respective network interface for communicating with the network 202 (e.g., outputting information to, and receiving information from, the network 202), such as by transferring information between such customers and the network 202. Accordingly, through the network 202, the customer support provider 204 communicates with the customers 206, 208 and 210, and the customers 206, 208 and 210 communicate with the customer support provider 204. The customer support provider 204 and the customers 206, 208 and 210 may each include a respective IHS such as, for example, the IHS 100 described above with reference to
Referring now to
Referring now to
The method 300 then proceeds to block 304 where the customer support provider 204 retrieves customer IHS data from the customer IHS. In an embodiment, the customer IHS includes a runtime environment that may include, for example, an operating system and a plurality of hardware dependencies that correspond to that runtime environment and allow that runtime environment to perform as it does on the customer IHS. In an embodiment, the operating system for the customer IHS includes a plurality of files such as, for example, configuration files, user data files, and a variety of other files known in the art that allow the operating system to perform as it does on the customer IHS. The customer support provider 204 may provide the customer 206 with a physical-to-logical image creation engine that may include, for example, software that may be loaded on the customer IHS and operable to collect the runtime environment of the customer IHS as customer IHS data, or an ‘image’ of the customer IHS, that may be run as a virtual machine, described in further detail below. In an embodiment, an ‘image’ of the customer IHS may include changes to the operating system run on the customer IHS that allows the operating system to run on a virtual IHS, described in further detail below. In an embodiment, the physical-to-logical image creation engine can be provided to the customer 206 through a hard copy (e.g. on an optical disk), an electronic file sent to the customer 206 through, for example, an electronic message, a link to a location where the physical-to-logical image creation engine is located, and/or using a variety of other provision methods known in the art. The customer 206 can then run the physical-to-logical image creation engine on the customer IHS, and the physical-to-logical image creation engine will collect the runtime environment of the customer IHS as customer IHS data that includes information relating to, for example, the operating system and the hardware dependencies within the operating system for the customer IHS. The physical-to-logical image creation engine or the customer 206 can then send that customer IHS data to the provider 204 through the communication engine 212 such that the customer IHS data is stored in the IHS image database 214. In an embodiment, the physical-to-logical image creation engine encrypts the customer IHS data in order to limit the customer IHS data from being viewed in transit from the customer IHS to the IHS image database 214. In an embodiment, the physical-to-logical image creation engine removes private customer data of the customer 206 from the customer IHS data such as, for example, digital photos, personal information, passwords, browser information, and a variety of other private files known in the art, before sending the customer IHS data to the provider 204.
The method 300 then proceeds to block 306 where a virtual IHS is run using the customer IHS data. In an embodiment, the customer support provider 204 can include a support IHS that may be, for example, the IHS 100, described above with reference to
Referring now to
Referring now to
Referring now to
Referring now to
In an embodiment, after the conclusion of the method 300, the customer 206 may experience another problem with the customer IHS. The method 300 may can then be repeated substantially similarly as is described above. However, second customer IHS data from the customer IHS that is retrieved at block 304 in the second iteration of the method 300 may can then be compared to first customer IHS data from the customer IHS that was retrieved at block 304 in the first iteration of the method 300. In an embodiment, the virtual IHS engine 216 and/or the physical IHS engine 218 may can compare the first customer IHS data and the second customer IHS data to determine whether or not a change has been made to the customer IHS between the first iteration of the method 300 and the second iteration of the method 300. In an embodiment, the comparing of the first customer IHS data and the second customer IHS data may occur before, during, or after the creation and/or running of the virtual IHS or the physical IHS.
Although illustrative embodiments have been shown and described, a wide range of modification, change and substitution is contemplated in the foregoing disclosure and in some instances, some features of the embodiments may be employed without a corresponding use of other features. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the embodiments disclosed herein.
Claims
1. A customer device problem diagnosis method, comprising:
- receiving, by a device support system through a network from a customer device, first customer device data that corresponds to a first customer device runtime environment that is provided using a customer device operating system and customer device hardware that are included in the customer device;
- creating, on at least one hardware subsystem in the device support system using the first customer device data, a virtual diagnosis device having a virtual diagnosis device operating system and virtual diagnosis device hardware that provide a virtual diagnosis device runtime environment; and
- reproducing, on the device support system using the virtual diagnosis device runtime environment on the virtual diagnosis device, the first customer device runtime environment that includes an operating problem with the customer device.
2. The method of claim 1, wherein the first customer device data includes a first customer device image of the customer device.
3. The method of claim 1, wherein the virtual diagnosis device runtime environment is the same as the first customer device runtime environment.
4. The method of claim 1, further comprising:
- sending, by the device support system through the network to the customer device, an electronic link to a network location that includes instructions for providing a physical-to-logical image creation engine that is configured to collect the first customer device data on the customer device and send the first customer device data from the customer device to the device support system.
5. The method of claim 4, wherein the physical-to-logical image creation engine is configured to recognize and remove private customer device data that is included in the first customer device data.
6. The method of claim 1, further comprising:
- receiving, by the device support system through the network from the customer device subsequent to receiving the first customer device data, second customer device data that corresponds to a second customer device runtime environment that is provided using the customer device operating system and the customer device hardware in the customer device;
- comparing, by the device support system, the first customer device data to the second customer device data; and
- determining, by the device support system based on the comparing of the first customer device data to the second customer device data, that a change has been made to the customer device.
7. The method of claim 1, further comprising:
- diagnosing, on the device support system based on the first customer device runtime environment that is reproduced on the virtual diagnosis device by the virtual diagnosis device runtime environment, the operating problem with the customer device.
8. An Information Handling System (IHS), comprising:
- at least one virtual diagnosis device hardware subsystem;
- a processing system that is coupled to the at least one virtual diagnosis device hardware subsystem; and
- a memory system that is coupled to the processing system and that includes instruction that, when executed by the processing system, cause the processing system to: receive, through a network from a customer device, first customer device data that corresponds to a first customer device runtime environment that is provided using a customer device operating system and customer device hardware in the customer device; create, on the at least one virtual diagnosis device hardware subsystem using the first customer device data, a virtual diagnosis device having a virtual diagnosis device operating system and virtual diagnosis device hardware that provide a virtual diagnosis device runtime environment; and reproduce, using the virtual diagnosis device runtime environment on the virtual diagnosis device, the first customer device runtime environment that includes an operating problem with the customer device.
9. The IHS of claim 8, wherein the first customer device data includes a first customer device image of the customer device.
10. The IHS of claim 8, wherein the virtual diagnosis device runtime environment is the same as the first customer device runtime environment.
11. The IHS of claim 8, wherein the memory system includes instruction that, when executed by the processing system, cause the processing system to:
- send, through the network to the customer device, an electronic link to a network location that includes instructions for providing a physical-to-logical image creation engine that is configured to collect the first customer device data on the customer device and send the first customer device data from the customer device to the device support system.
12. The IHS of claim 11, wherein the physical-to-logical image creation engine is configured to recognize and remove private customer device data that is included in the first customer device data.
13. The IHS of claim 8, wherein the memory system includes instruction that, when executed by the processing system, cause the processing system to:
- receive, through the network from the customer device subsequent to receiving the first customer device data, second customer device data that corresponds to a second customer device runtime environment that is provided using the customer device operating system and the customer device hardware on the customer device;
- compare the first customer device data to the second customer device data; and
- determine, based on the comparing of the first customer device data to the second customer device data, that a change has been made to the customer device.
14. The IHS of claim 8, wherein the memory system includes instruction that, when executed by the processing system, cause the processing system to:
- diagnose, based on the first customer device runtime environment that is reproduced on the virtual diagnosis device by the virtual diagnosis device runtime environment, the operating problem with the customer device.
15. A device problem diagnosis system, comprising:
- a first device that includes a first device operating system and first device hardware that operate to provide a first device runtime environment; and
- a second device that includes at least one hardware subsystem and that is coupled to the first device through a network, wherein the second device is configured to: receive, through the network from the first device, first device data that corresponds to the first device runtime environment; create, on at least one hardware subsystem using the first customer device data, a virtual diagnosis device having a virtual diagnosis device operating system and virtual diagnosis device hardware that provide a virtual diagnosis device runtime environment; and reproduce, using the virtual diagnosis device runtime environment on the virtual diagnosis device, the first device runtime environment that includes an operating problem with the first device.
16. The system of claim 15, wherein the first device data includes a first device image of the first device.
17. The system of claim 15, wherein the virtual diagnosis device runtime environment is the same as the first device runtime environment.
18. The system of claim 15, wherein the second device is configured to:
- send, through the network to the first device, an electronic link to a network location that includes instructions for providing a physical-to-logical image creation engine that is configured to collect the first device data on the first device and send of the first device data from the first device to the second device.
19. The system of claim 15, wherein the second device is configured to:
- receive, through the network from the first device subsequent to receiving the first device data, second device data that corresponds to a second device runtime environment that is provided using the first device operating system and the first device hardware included in the first device;
- compare the first device data to the second device data; and
- determine, based on the comparing of the first device data to the second device data, that a change has been made to the first device.
20. The system of claim 15, wherein the second device is configured to:
- diagnose, based on the first device runtime environment that is reproduced on the virtual diagnosis device by the virtual diagnosis device runtime environment, the operating problem with the first device.
Type: Application
Filed: Jun 20, 2017
Publication Date: Oct 5, 2017
Inventor: Douglas M. Anson (Dripping Springs, TX)
Application Number: 15/628,164