Porting security application preferences from one system to another

• US 20070192322A1
• Filed: 01/31/2006
• Published: 08/16/2007
• Est. Priority Date: 01/31/2006
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Dandekar, Shree, Gupta, Abhinav, Borchers, Roger, Lyudovyk, Olga
• Granted Patent: US 7,617,214 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 9/4451 User profiles; Roaming

Abstract

Configuring a security application includes determining whether user preferences for the security application are pre-loaded in an information handling system (IHS) received by a user. If the user preferences have not been pre-loaded a request to receive the user preferences corresponding to the user and the security application is sent to a provider of the security application. The request includes a unique identifier for accessing the user preferences for the security application. The user preferences, which have been previously configured by the user for another IHS, are stored in a predefined format and are accessible to any requester providing the unique identifier. The provider provides the user preferences corresponding to the unique identifier.

Claims

1. A method for configuring a security application, the method comprising:

receiving a first input from a user, wherein the first input is indicative of the user selecting the security application from a plurality of security applications,

receiving a second input, wherein the second input includes a request to load user preferences corresponding to the user and the security application;

receiving a unique identifier, wherein the user preferences for the security application are accessible by providing the unique identifier;

requesting the user preferences corresponding to the unique identifier; and

receiving the user preferences.

2. The method of claim 1 further comprising:

preparing a pre-configuration file corresponding to an order entered by the user, wherein the pre-configuration file includes the user preferences.

3. The method of claim 2, further comprising:

installing the pre-configuration file on an information handling system (IHS) being fabricated corresponding to the order, wherein the user preferences are loaded on the IHS during the installing of the pre-configuration file.

4. The method of claim 1, wherein the user preferences are stored in a repository in accordance with a predefined format, wherein a provider for each one of the plurality of security software applications stores the user preferences corresponding to the unique identifier and the user in accordance with the predefined format.

5. The method of claim 4, wherein the predefined format is defined in accordance with an extensible markup language (XML).

6. The method of claim 4, wherein the predefined format includes a tag identifier and a plurality of attributes corresponding to the tag identifier, wherein the unique identifier includes the tag identifier.

7. The method of claim 4, wherein the user preferences stored in the predefined format are accessible to any requester providing the unique identifier.

8. The method of claim 1, wherein the user preferences are provided by a provider of the security application in response to the requesting.

9. The method of claim 1, wherein the unique identifier is a service tag, wherein the service tag uniquely identifies an information handling system purchased by the user.

10. A method for configuring a security application, the method comprising:

determining whether user preferences for the security application are pre-loaded;

receiving an input, wherein the input includes a request to load the user preferences corresponding to a user and the security application in response to determining that the user preferences are not pre-loaded;

receiving a unique identifier, wherein the user preferences for the security application are accessible by providing the unique identifier;

requesting the user preferences corresponding to the unique identifier; and

receiving the user preferences.

11. The method of claim 10, wherein the user preferences are stored in a repository in accordance with a predefined format, wherein a provider for each one of a plurality of security applications accesses the repository to store the user preferences corresponding to the unique identifier and the user in accordance with the predefined format.

12. The method of claim 11, wherein the predefined format is defined in accordance with an extensible markup language (XML).

13. The method of claim 11, wherein the predefined format includes a tag identifier and a plurality of attributes corresponding to the tag identifier, wherein the unique identifier includes the tag identifier.

14. The method of claim 11, wherein the user preferences stored in the predefined format are accessible to any requester providing the unique identifier.

15. The method of claim 10, wherein the unique identifier is a service tag, wherein the service tag uniquely identifies a previously configured information handling system purchased by the user.

16. An information handling system (IHS) comprising:

a processor;

a memory coupled to the processor for storing a plurality of instructions executable by the processor to configure a security application, wherein the plurality of instructions are executable for;

determining whether user preferences for the security application are pre-loaded in the memory;

receiving an input, wherein the input includes a request to load the user preferences corresponding to a user and the security application in response to determining that the user preferences are not pre-loaded;

receiving a unique identifier, wherein the user preferences for the security application are accessible by providing the unique identifier;

requesting the user preferences corresponding to the unique identifier; and

receiving the user preferences.

17. The system of claim 16, wherein the user preferences are stored in accordance with a predefined format in a repository coupled to the IHS, wherein a provider for each one of a plurality of security applications accesses the repository to store the user preferences corresponding to the unique identifier and the user in accordance with the predefined format.

18. The system of claim 17, wherein the predefined format is defined in accordance with an extensible markup language (XML).

19. The system of claim 17, wherein the predefined format includes a tag identifier and a plurality of attributes corresponding to the tag identifier, wherein the unique identifier includes the tag identifier.

20. The system of claim 17, wherein the user preferences stored in the predefined format are accessible to any requester providing the unique identifier.

21. The system of claim 16, wherein the unique identifier is a service tag, wherein the service tag uniquely identifies a previously configured information handling system purchased by the user.