Abstract:
The present invention permits registry settings and other pertinent shared artifacts to be distributed across many different computing devices. More specifically, the invention permits applications installed on an external drive to be activated, when the external drive is connected to a main computing device. When connected, a drive agent can detect registry settings stored on the external drive and can synchronize these settings with a main registry of the main computing device. Further, interface elements, such as icons for the new applications can be added to a GUI of the main computing device. Once the registry settings are included in the main registry, applications on the external drive can used from the main computing device. When the external drive is detached from the main computing device, the device agent can automatically remove all registry settings, shared artifacts, and interface elements.

Description:
BACKGROUND  
       [0001]    1. Field of the Invention 
         [0002]    The present invention relates to the field of device access and, more particularly, to an automated solution to provide immediate requisite access to data and applications on an attached external device. 
         [0003]    2. Description of the Related Art 
         [0004]    Advances in portable hard drives and flash drives permit users to easily carry a tremendous amount of convenient storage space when traveling, which could in theory be used to satisfy their data and application needs. At present, however, portable storage devices are only useful for storing data and are unable to store applications that consume or manipulate the data. This is because use of most modern applications requires a set of Application Program Interfaces (APIs), Dynamic Link Libraries (DLLs), registry settings, and the like, which are stored on a main drive of an operating system at application installation time. Consequently, data can be transported on external drives, but is often unable to be used because access to a necessary and corresponding application is unavailable. 
         [0005]    A wide variety of solutions have been developed to ensure users have access to needed applications. One attempted solution is to continuously install and uninstall application programs, such as from images stored on the portable drive. This solution has many flaws. First, users are often not granted access to install programs on public use machines, such as those found at libraries, internet cafés, and airports. Further, constantly installing and removing programs is a practice that corrupts a registry and shared library stores, is time consuming, and may even be impossible due to computer specific hashes used to “activate” many software programs. 
         [0006]    One technique that could minimize some of the flaws with repetitive install and uninstall operations is application virtualization. Commercial application virtualization solutions are currently provided by companies such as Atiris, Inc., Softricity Inc., and AppStream Inc. Application virtualization creates a virtual application layer between an operating system and an application. This layer is activated when a program is installed. The virtual application layer functions as a proxy between a registry and an installed application, where application specific settings are placed in the virtual application layer. If an application is moved from one machine to another that includes the same virtual application layer, machine-specific settings do not have to be adjusted. In order for a virtualized application to execute, the application virtualization layer first needs to be executing. 
         [0007]    This solution fails to overcome problems involving insufficient permission to install applications. Permission problems are actually increased, since creating a new application virtualization layer on a machine is a very intrusive process typically requiring system administrator privileges. Further, application virtualization fails to address situations of executing applications from a periodically removed external drive. When the drive is present, necessary application programs can exist. When removed, these programs will be absent, creating problems and errors when an associated icon or shortcut is selected. 
         [0008]    A traditional solution to ensuring application availability is to create an application server on the network that allows a multitude of users to access an application. However, the application server is only accessible when a user is connected to the network. Thus, the issue of needing additional hardware and software to overcome the distance resurfaces in order to provide a remote user with access. Further, network latency issues can result in application performance that is below an acceptable level. This can be especially true when a traveler is accessing a served application over a low quality network connection. 
         [0009]    In addition to issues of hardware and performance, current software licensing practices are a precarious quagmire of issues relating to applications. Most commercial software requires a license and/or activation for each installation of the application, whether or not the additional installation is for the same user. A user can easily consume multiple licenses in order to accommodate an assortment of devices that are necessary to provide them access in a variety of locations and situations. For example, a user may need a license for a work computer, a home computer, a laptop computer, and the like. Conventional solutions working with the current licensing system severely limit a user and a company in terms of portability and affordability. 
       SUMMARY OF THE INVENTION 
       [0010]    The present invention permits registry settings and other pertinent shared artifacts to be distributed across many different computing devices. More specifically, the invention permits applications installed on an external drive to be activated, when the external drive is connected to a main computing device. When connected, a drive agent can detect registry settings stored on the external drive and can synchronize these settings with a main registry of the main computing device. Further, interface elements, such as icons for the new applications, can be added to a GUI of the main computing device. Once the registry settings are included in the main registry, applications on the external drive can be used from the main computing device. When the external drive is detached from the main computing device, the device agent can automatically remove all registry settings, shared artifacts, and interface elements. 
         [0011]    The present invention can be implemented in accordance with numerous aspects consistent with the material presented herein. For example, one aspect of the present invention can include a method for permitting applications stored within an external drive to execute from a software environment of a computing device whenever the external drive is connected to the computing device. The method can include a step of storing within an external drive at least one external software application, wherein external configuration items relating to the software application can be stored in an external configuration store of the external device. The external drive can be connected to a computing device. The computing device can have a local configuration store that includes local configuration items related to local software applications installed within a local software environment of the computing device. External configuration items can be automatically added to the local configuration store, which can permit the external software application to execute from within the local software environment. The external drive can later be disconnected from the computing device, which results in the external configuration items being automatically removed from the local configuration store. 
         [0012]    Another aspect of the present invention can include a method for permitting software applications installed on a removable external device to be used in a local environment. In the method, a software application can be installed to an external drive. Installation can involve creating configuration items for the software application within an external configuration store of the external drive. An event can automatically detect when the external drive is connected to a local computing device hosting a local software environment having a local configuration store. The adding of the drive can cause configuration items for the installed software application to be dynamically and automatically added to the local configuration store. The added configuration items can include at least one configuration item that adds a graphical item to a graphical user interface of the local software environment. The added configuration items can also include at least one configuration item that causes the local software environment to associate at least one file type with the external software application. A user selection of the graphical item or file having the associated file type can cause the external software application to execute within the local software environment. 
         [0013]    It should be noted that various aspects of the invention can be implemented as a program for controlling computing equipment to implement the functions described herein, or a program for enabling computing equipment to perform processes corresponding to the steps disclosed herein. This program may be provided by storing the program in a magnetic disk, an optical disk, a semiconductor memory, any other recording medium, or can also be provided as a digitally encoded signal conveyed via a carrier wave. The described program can be a single program or can be implemented as multiple subprograms, each of which interact within a single computing device or interact in a distributed fashion across a network space. 
         [0014]    The method detailed herein can also be a method performed at least in part by a service agent and/or a machine manipulated by a service agent in response to a service request. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0015]    There are shown in the drawings, embodiments which are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown. 
           [0016]      FIG. 1  is a graphical representation illustrating changes in a client environment when attaching an external device in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0017]      FIG. 2  is a schematic diagram illustrating a system for providing automated and immediate requisite access to data and applications on an attached external device i accordance with embodiments of the inventive arrangements disclosed herein. 
           [0018]      FIG. 3  is a graphical representation illustrating the basic interactions between components when an external device is attached to a client in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0019]      FIG. 4  is a flow chart of a method for providing automated and immediate requisite access to data and applications on an attached external device in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0020]      FIG. 5  is a flow chart of a method detailing the automated and immediate requisite access to data and applications on an attached external hard drive in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0021]      FIG. 6  is a flow chart of a method detailing the adjustment process to provide automated and immediate requisite access to applications on an attached external hard drive in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0022]      FIG. 7  is a flow chart of a method detailing the changes to a system that provides automated and immediate requisite access to applications on an attached external device when the external device is removed from the system in accordance with an embodiment of the inventive arrangements disclosed herein. 
           [0023]      FIG. 8  is a flow chart of a method where a service agent can configure a system to provide automated and immediate requisite access to applications on an attached external device in accordance with an embodiment of the inventive arrangements disclosed herein. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0024]      FIG. 1  is a graphical representation  100  illustrating changes in a client environment when attaching an external device in accordance with an embodiment of the inventive arrangements disclosed herein. The changes illustrated in this graphical representation  100  can occur in the context of system  200  or any other system supporting immediate requisite access to data and applications on an attached external device in an automated fashion. 
         [0025]    The initial environment  101  contains the contents of the external device  110  prior to the attachment of the external device  110  to the client  105 . It should be appreciated that the contents of the client  105  and external device  110  are for illustrative purposes only and are not meant as limitation of the invention. In this example, the client  105  contains a library file  107  and has and email application  108 , Web browser  106 , and word processing application  109 . The external device  110  contains a newer library file  115  and data files  111  and has a newer version of the word processing application  112 , a presentation application  113 , and a movie editor application  114 . 
         [0026]    The attachment of external device  110  to client  105  can produce resultant environment  120 . The resultant environment  120  can include accessible content changes  125 , client graphical user interface (GUI) changes  130 , and configuration store changes  135 . The accessible contents  127  can be a result of the accessible content changes  125  in the resultant environment  120 . 
         [0027]    As shown in this example, the accessible contents  127  can display the union of available content from the client  105  and external device  110 . It should be noted that the device agent  112  of system  100  can allow for the coexistence of multiple versions of the same application, as in word processing applications  109  and  112 , and the replacement of an older file with a newer version, as in library file  107  being replaced with library file  115 . The accessible contents  127  can be displayed within the client GUI changes  130 . 
         [0028]    Client GUI changes  130  can include a display of desktop  132 . Desktop  132  can display the changes made when external device  110  is connected to the client  105 . The applications and data contained on the external device  110  can be made available to a user on client  105  via program icons  133  and shortcuts  134 . Selection of a program icon  133  or shortcut  134  can access the associated data or application on the external device  110 . 
         [0029]    Connecting external device  110  to client  105  can also result in configuration store changes  135 . A format of the configuration store can be dependent upon the operating system used by the client  105 . This example utilizes a WINDOWS environment. As such, the editor GUI  136  reflects the registry used in WINDOWS to store this information. The concepts expressed herein are not limited to any particular platform or operating system. 
         [0030]    The configuration store changes  135  made to client  105  can be viewed in an editor GUI  136 . Since the movie editor application  114  resides on the external device  110 , the registry of the client  105  can be modified, as shown in the registry display  138 , so the movie editor application  114  can be run on the client  105 . The highlighted entry  140  can be added to the registry of the client  105  in order for it to run the movie editor application  114 . Additionally, the editor GUI  136  can display the path  145  for the highlighted entry  140 . 
         [0031]      FIG. 2  is a schematic diagram illustrating a system  200  for providing automated and immediate requisite access to data and applications on an attached external device in accordance with embodiments of the inventive arrangements disclosed herein. In system  200 , the external device  215  can be directly connected to the client  210  to provide a user  205  with direct access to the contents of the external device  215 . Connectivity can be provided by a variety of means, including, but not limited to, a Universal Serial Bus (USB) connection, FIREWIRED, BLUETOOTH, WIFI, an Ethernet cable, a null modem cable, a connection utilizing a parallel interface cable, and the like. 
         [0032]    The client  210  can be any of a variety of devices used by a user  205  that can support the direct attachment of an external device  215  and communicatively linked to a server  225  by a network  220 . By extension, applications residing on the external device  215  can access the server  225  through its connection to the client  210 . 
         [0033]    The client  210  can include a device agent  212 , main configuration store  213 , and a policy manager  214 . The device agent  212  can be a software application that synchronizes data between the client&#39;s  210  main configuration store  213  and the local configuration store  216  of an external device  215  and enforces the access policy determined by the policy manager  214 . The device agent  212  can be responsible for the modifications to the main configuration store  213  that allow the user  205  to run software applications installed on the external device  215  from the client  210  machine. Additionally, the device agent  212  can reverse modifications upon the removal of the external device  215  from the client  210 . 
         [0034]    The main configuration store  213  can be a memory location of the client  210  designed to contain hardware and software configuration information as well as user preferences. It should be noted that the actualization of the main configuration store  213  is dependent upon the operating system in use on the client  210 . For example, in a WINDOWS platform, the main configuration store is called the registry; in a UNIX environments, the main configuration store is called the global registry and stored in a specific file and location. Additionally, the data that would be expected to be stored within the main configuration store  213  can also be spread out over multiple files and/or locations on the client  210 , as in the case of a MACINTOSH. 
         [0035]    The policy manager  214  can be a software application that attempts to negotiate and enforce an inclusive access policy for items contained on the external device  215 . This access policy can be formulated from a device policy list  217  stored on the external device  215  as well as a system policy list  226 . The system policy list  226  can reside upon an accessible server  225  or other available networked component. Alternately, the system policy list  226  con reside upon the client  210 . A policy list can contain data pertaining to the access of data and applications. For example, a policy list can include digital certificates, licensing information, user permissions, and the like. 
         [0036]    It should be appreciated that the policy negotiated by the policy manager  214  from the policy lists  217  and  226  can limit a user&#39;s  105  access to network resources. For example, a service agent can take an external hard drive containing all data and applications necessary to perform his duties to a customer site. At the customer site, the server agent can connect the external hard drive to a computer on the customer&#39;s network to perform tasks. The customer&#39;s network may contain data files that should not be accessible to the service agent. This access restriction can be contained in a system policy list on the customer&#39;s network. Therefore, the policy negotiated by the policy manager on the customer&#39;s computer can include this restriction and the designated data files and/or areas will be unavailable to the service agent. 
         [0037]    The external device  215  can be any of a variety of devices capable of storing data and/or applications and connecting to a client  210 . In addition to applications and/or data, the external device  215  can include a local configuration store  216 , a device policy list  217 , and adjustment processes  218 . The local configuration store  216 , similar to the main configuration store  213  of the client  210 , can contain hardware and software configuration information and user preferences specific to the external device  215  and any data and/or applications stored upon it. It should be noted that the structure of the local configuration store  217  should correspond to that of the main configuration data store  213 , which should be aligned with the operating system of the client  210 . 
         [0038]    It should be appreciated that this aspect of the invention allows for complete portability of a software license. For example, an installation of a word processing application will function on any compatible client  210  machine regardless of location and network access. Thus, a user can install all necessary applications on an external device  215  and access them from any client  210  in any location. In such an example, the loaded external device  215  could take the place of a traditionally loaded laptop computer. 
         [0039]    The adjustment processes  218  can be one or more software routines designed to modify elements of the client  210  in order for the user  205  to access applications on the external device  215 . Copying files, updating entries in the main and/or local configuration stores, and reversing previous actions are examples of modifications that can be made by adjustment processes  218 . 
         [0040]    In another contemplated embodiment, the external device  215  can be attached to the server  225  instead of client  210 . The user can then access the contents of the external device  215  over the network  220  providing that the server  225  is available. 
         [0041]    Network  220  can include any hardware/software/and firmware necessary to convey data encoded within carrier waves. Data can be contained within analog or digital signals and conveyed though data or voice channels. Network  220  can include local components and data pathways necessary for communications to be exchanged among computing device components and between integrated device components and peripheral devices. Network  220  can also include network equipment, such as routers, data lines, hubs, and intermediary servers which together form a data network, such as the Internet. Network  220  can also include circuit-based communication components and mobile communication components, such as telephony switches, modems, cellular communication towers, and the like. Network  220  can include line based and/or wireless communication pathways. 
         [0042]      FIG. 3  is a graphical representation  300  illustrating the basic interactions between components when an external device is attached to a client in accordance with an embodiment of the inventive arrangements disclosed herein. The interactions illustrated in this graphical representation  300  can occur in the context of system  200  or any other system supporting immediate requisite access to data and applications on an attached external device in an automated fashion. 
         [0043]    The client  305  can include device agent  306 , policy manager  307 , and main configuration store  308 . The external device  310  can include policy list  312 , local configuration store  313 , and adjustment processes  314 . The system  315  can include a policy list  316 . The interaction between the various components can be shown by the various request and responses of the graphical representation  300 . 
         [0044]    Interaction between the various components can begin once an external device  310  is attached to the client  305 . At this time, the device agent  306  can issue a get info request  320  to the local configuration store  313  of the external device  310 . The requested information can be returned to the device agent  306  via response  321 . 
         [0045]    Upon the receipt of response  321 , the device agent  306  can execute a procedure  325  to create a candidate list. Once the candidate list is created, the device agent  306  can issue an invoke command  330  to the policy manager  307 . The policy manager  307  can then send a get info request  335  to the external device  310  requesting the information contained within its policy list  312 . This information can be returned to the policy manager  307  via response  336 . Next, the policy manager  307  can send a get info request  340  to the client&#39;s  305  system  315 . The system  315  can return the information contained within its policy list  316  via response  341 . 
         [0046]    Once the policy manager  307  receives the information for both policy lists  312  and  316 , it can execute code  345  to negotiate a policy. After the negotiation, the policy manager  307  can execute another procedure  350  to determine the compliance of the candidate list with the negotiated policy. The resultant policy and compliance list can be returned to the device agent  306  in response  351 . 
         [0047]    The device agent  306  can make modifications to the client  305  environment to accommodate items contained on the compliance list by issuing an adjust client command  355  to the adjustment processes  314 . The adjustment processes  314  can perform actions, such as copying files and modifying data entries of the local configuration store  313 , as specified by the device agent  306 . Completion of the adjust client command  355  can be contained within a response  356  to the device agent  306 . 
         [0048]    Lastly, the device agent  306  can issue an update command  360  to the main configuration store  308  of the client  305 . The update command  360  can change the entries and data values of entries within the main configuration store  308  for allowing a user to run applications installed on the external device  310 . Confirmation of changes can be returned to the device agent  306  in response  361 . 
         [0049]      FIG. 4  is a flow chart of a method  400  for providing automated and immediate requisite access to data and applications on an attached external device in accordance with an embodiment of the inventive arrangements disclosed herein. 
         [0050]    Method  400  can begin in step  405  when a user attaches an external device to a client machine. This triggers step  410  where the device agent can synchronize the configuration stores of the client machine and external device. In step  415 , the policy manager can negotiate and enforce an access policy. 
         [0051]    In response to the negotiation and enforcement of the access policy, step  420  occurs where the device agent can adjust the client machine to provide access to applications residing on the external device as necessary. The user can then access any applications and data on the external device that comply with the access policy from the client machine in step  425 . 
         [0052]      FIG. 5  is a flow chart of a method  500  detailing the automated and immediate requisite access to data and applications on an attached external hard drive in accordance with an embodiment of the inventive arrangements disclosed herein. 
         [0053]    Method  500  can begin in step  505  where a user can attach an external hard drive to a client machine. In step  510 , the client&#39;s operating system can detect the addition of the new hardware and invoke the device agent. It should be noted that the device agent can be run in a passive state until needed to increase responsiveness. 
         [0054]    In step  515 , the device agent can retrieve information from the local configuration store of the external hard drive and create a candidate list. The candidate list can include the applications and data files contained on the external drive. In step  520 , the device agent can invoke the policy manager. 
         [0055]    The policy manager retrieves the policy list from the external drive and the client&#39;s system in step  525 . In step  530 , the policy manager can negotiate an effective policy. Next, the policy manager checks an entry of the candidate list against the effective policy in step  535 . Should the candidate list entry not comply with the effective policy, flow proceeds to step  540  where the entry can be removed from the candidate list. 
         [0056]    Should the candidate list entry comply with the effective policy or a non-compliant entry removed from the list, flow proceeds to step  545  where it can be determined if the end of the candidate list has been reached. If more entries exist on the candidate list, then step  550  occurs where the device agent can move to the next entry in the list. After the execution of step  550 , flow loops back to step  535 . Once the end of the candidate list has been reached, step  555  is executed where the device agent can modify the client&#39;s main configuration store. 
         [0057]      FIG. 6  is a flow chart of a method  600  detailing the adjustment process to provide automated and immediate requisite access to applications on an attached external hard drive in accordance with an embodiment of the inventive arrangements disclosed herein. 
         [0058]    Method  600  can be an extension of method  500 , continuing where method  500  ended. Therefore, method  600  begins with step  605  where the device agent can determine if the client machine requires adjustment in order to run the application specified on the candidate list. In step  610 , the device agent can retrieve application information. Upon receipt of this information, the device agent can determine if the application already exists on the client machine in step  615 . 
         [0059]    Should the application already exist on the client, then flow proceeds to step  617  where the device agent can prompt the user for the appropriate action to take. It should be noted that additional actions can be implemented with additional steps necessary and that those illustrated in method  600  are for illustrative purposes only. 
         [0060]    If the user opts to have the specified application version override the version that is available on the client, then step  618  is executed where the device agent can make the necessary modifications to override the existing version. Upon completion of step  618 , flow proceeds to step  625 . Should the user opt to have both application versions coexist on the client, flow also proceeds to step  625 . The user could also opt to skip any action for the application, branching flow to step  635 . 
         [0061]    However, if step  615  determines that the application does not exist on the client, then step  620  occurs where the device agent can add the application&#39;s information to the main configuration store on the client machine. Step  625  then occurs where the device agent can update the local configuration store of the external hard drive, if necessary. 
         [0062]    In step  630 , the device agent can execute an appropriate adjustment process allowing the client machine the ability to run the application. Step  635  can then determine if the end of the candidate list has been reached. If more entries exist on the candidate list, then step  640  occurs where the device agent can move to the next entry in the list. After the execution of step  640 , flow loops back to step  605 . Once the end of the candidate list has been reached, Step  645  is executed where the device agent can terminate its processing and enter a passive state until needed. 
         [0063]      FIG. 7  is a flow chart of a method  700  detailing the changes to a system that provides automated and immediate requisite access to applications on an attached external device when the external device is removed from the system in accordance with an embodiment of the inventive arrangements disclosed herein. 
         [0064]    Method  700  can begin with step  705  where a user can detach an external device from a client machine. In step  710 , the device agent can remove data that was added to the configuration data stores, both local and main, when the external device was added to the client. Additionally, the device agent can remove any data files that were copied to the client from the external device. 
         [0065]    In the case when the device agent attempts to remove an application version that is later than what was on the client originally, the deice agent can notify the user in step  715 . Should the user desire to reinstate the previous application version, step  720  is executed where the device agent can reset configuration store entries to values appropriate for the previous version. 
         [0066]    Flow branches to step  717  should the user desire to ignore the previous application version. In step  717 , the device agent can clean the configuration store entries associated with the application. The device agent can optionally trigger the client to uninstall the application in step  718 . 
         [0067]    Lastly, step  725  is executed where the device agent can remove all data files that were copied onto the client from the external device. It should be noted that the actions performed in steps  717 ,  718 ,  720 , and  725  can be included as functions in adjustment processes. These steps were detailed specifically to illustrate the depth of changes made during this method  700 . 
         [0068]      FIG. 8  is a flow chart of a method  800  where a service agent can configure a system to provide automated and immediate requisite access to applications on an attached external device in accordance with an embodiment of the inventive arrangements disclosed herein. 
         [0069]    Method  800  can begin in step  805 , when a customer initiates a service request. The service request can be a request for a service agent to establish a new system to provide automated and immediate requisite access to applications on an attached external device. The service request can also be a request to troubleshoot a problem with an existing system that provides automated and immediate requisite access to applications on an attached external device. 
         [0070]    In step  810 , a human agent can be selected to respond to the service request. In step  815 , the human agent can analyze a customer&#39;s current system and can develop a solution. The solution can result in system  200  or any system supporting immediate requisite access to data and applications on an attached external device in an automated fashion, such as a system that performs the steps of method  400 . 
         [0071]    In step  820 , the human agent can configure the customer&#39;s system to provide automated and immediate requisite access to applications on an attached external device. This can include the installation of a device agent and policy manager on the client machine. This can also include the installation of a local configuration store and adjustment processes on an external device as well as the implementation of a policy list. 
         [0072]    In step  825 , the human agent can optionally maintain an existing system that is configured to provide immediate requisite access to data and applications on external devices for the customer. In step  830 , the human agent can complete the service activities. 
         [0073]    The present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. 
         [0074]    The present invention also may be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.