Patent application number | Description | Published |
20090006503 | System Virtualization Instance Management for Terminal Sessions - Terminal sessions providing remote access to functionality may be isolated from each other, as well as from the server system space, by being placed in system virtualization instances. Applications associated with terminal sessions may be allocated to system virtualization instances. In particular, system virtualization instances may be pre-instantiated, and applications may be dynamically allocated to the system virtualization instances, for example, according to a virtualization instance policy. The system virtualization instances may provide, in particular, an ability for terminal session components and associated applications to create, read, update and delete resources in a global name space of a host server without conflict, collision or other interference with each other or other server components. | 01-01-2009 |
20090007139 | Running Add-On Components in Virtual Enviroments - Systems and methods for running add-on components in virtual environments are described. An add-on component can be executed in a virtual environment by setting up a communication link between a component proxy in the host operating system and a server process running in the virtual environment. The server process executes the add-on component based on commands forwarded by the component proxy forwards the commands from the operating system. | 01-01-2009 |
20090007151 | Printing For Virtualized Applications - Procedures for printing virtualized applications are discussed. In implementations, a spooler is associated with an established virtual environment including a virtualized application. The spooler may be associated by making a native spooler, installed on a computing system aware of the virtual environment. In other implementations, the spooler may be virtualized such as by including an instance of a spooler in the virtual environment. A printer driver may be virtualized for use in print virtual application output. Virtualizing printer drivers may allow virtual applications to access and use printer and/or software resources without installing the resource on the device. | 01-01-2009 |
20090007161 | NAMESPACE MERGER - In a virtualization environment, there is often a need for an application to access different resources (e.g., files, configuration settings, etc.) on a computer by name. The needed resources can potentially come from any one of a plurality of discrete namespaces or containers of resources on the computer. A resource name can identify one resource in one namespace and another resource in another namespace, and the namespaces may have different precedence relative to one another. The resources needed by the application can be accessed by enumerating names in a logical merger of the namespaces such that as new names in the logical merger are needed they are dynamically chosen from among the namespaces. When two resources in different namespaces have a same name, the resource in the higher precedence namespace can be chosen. | 01-01-2009 |
20090007162 | FLEXIBLE NAMESPACE PRIORITIZATION - Access to resources on a computer may be provided by using a first namespace of resources and a second namespace of resources, where one or more names are common to both namespaces and those names refer to different respective instances of resources. A request is received for a first resource name from an application, where the first resource name exists in the first resource namespace and in the second resource namespace. In response to the request, whether to obtain a resource from the first namespace or from the second namespace is determined by applying one or more resource policies to the first resource namespace and to the second resource namespace. | 01-01-2009 |
20090044170 | Automated Application Modeling for Application Virtualization - Automated application modeling for application virtualization (auto-modeling) may be incorporated into an application installer and/or other suitable component of a computer operating system. Auto-modeling may be performed by an auto-modeling agent. The auto-modeling agent may employ one or more of multiple auto-modeling strategies. The auto-modeling agent may assess one or more of a particular application, application installation package and/or application environment in order to determine a suitable auto-modeling strategy. Auto-modeling strategies may include active auto-modeling and passive auto-modeling. Active auto-modeling strategies may require at least partial installation and/or execution of the application to be modeled, whereas passive auto-modeling may generate corresponding auto-modeling data independent of application installation and/or execution, for example, by obtaining suitable data from a corresponding application installation package. In particular, The auto-modeling agent may perform active auto-modeling by directing an independent application modeler and/or an application installer, for example, in accordance with an auto-modeling rulebase. | 02-12-2009 |
20090293054 | Streaming Virtual Disk for Virtual Applications - A sparsely populated, streaming virtual disk may be used with a virtual application to enable fast launching of a virtual application from a network server. The virtual disk may be configured and populated in blocks, enabling those blocks that are used at a particular time to be downloaded and stored in the virtual disk. As other blocks are requested by the virtual application, those blocks may be fetched from the network server. Each block may be validated using a hash tree or some other function so that the recipient may verify authenticity and completeness. In some embodiments, a virtual application may be configured and deployed as a single file, enabling simple version control among other things. | 11-26-2009 |
20100023738 | State Separation for Application Changes - Application states may be stored and retrieved using policies that define various contexts in which the application is used. The application states may define configurations or uses of the application, including connections to and interactions with other applications. Applications that are virtualized may have state that is defined within a usage context and multiple states or configurations may be stored and recalled based on the usage context. Policies may define the context and what parameters are to be saved, and may be applied when applications are operated in a virtualized manner. | 01-28-2010 |
20100023934 | Computer Application Packages with Customizations - Applications operated within a virtual environment may be organized into a package containing various software components. Each software component or resource may have a specific name and other metadata, including a designator for overwriting or modifying the component. A policy may define how any changes to specific software components may be stored and retrieved based on the designator. One or more sets of changed components may be generated, persisted, and re-applied to create a customized version of the application based on the original package. The application may be operated within a virtual application environment or within a dedicated virtual machine environment. | 01-28-2010 |
20110088040 | Namespace Merger - In a virtualization environment, there is often a need for an application to access different resources (e.g., files, configuration settings, etc.) on a computer by name. The needed resources can potentially come from any one of a plurality of discrete namespaces or containers of resources on the computer. A resource name can identify one resource in one namespace and another resource in another namespace, and the namespaces may have different precedence relative to one another. The resources needed by the application can be accessed by enumerating names in a logical merger of the namespaces such that as new names in the logical merger are needed they are dynamically chosen from among the namespaces. When two resources in different namespaces have a same name, the resource in the higher precedence namespace can be chosen. | 04-14-2011 |
20110246617 | Virtual Application Extension Points - A virtual application may be configured with several extension points within a host operating system. The virtual application may be configured with a private namespace in which various components, such as registry settings, dynamic linked libraries, and other components may reside. During configuration, links may be placed in the host operating system that may point to objects in the virtual application's private namespace so that the operating system and other applications may launch, control, or otherwise interact with the virtual application. The links may be located in a file system, registry, or other locations and may be available to other applications, including other virtual applications. A configuration routine may place the links into the host operating system at the time the application may be configured. | 10-06-2011 |
20110302581 | State Separation for Virtual Applications - Application states may be stored and retrieved using policies that define various contexts in which the application is used. The application states may define configurations or uses of the application, including connections to and interactions with other applications. Applications that are virtualized may have state that is defined within a usage context and multiple states or configurations may be stored and recalled based on the usage context. Policies may define the context and what parameters are to be saved, and may be applied when applications are operated in a virtualized manner. | 12-08-2011 |
20130263134 | State Separation For Virtual Applications - Application states may be stored and retrieved using policies that define various contexts in which the application is used. The application states may define configurations or uses of the application, including connections to and interactions with other applications. Applications that are virtualized may have state that is defined within a usage context and multiple states or configurations may be stored and recalled based on the usage context. Policies may define the context and what parameters are to be saved, and may be applied when applications are operated in a virtualized manner. | 10-03-2013 |
20130305264 | Virtual Application Extension Points - A virtual application may be configured with several extension points within a host operating system. The virtual application may be configured with a private namespace in which various components, such as registry settings, dynamic linked libraries, and other components may reside. During configuration, links may be placed in the host operating system that may point to objects in the virtual application's private namespace so that the operating system and other applications may launch, control, or otherwise interact with the virtual application. The links may be located in a file system, registry, or other locations and may be available to other applications, including other virtual applications. A configuration routine may place the links into the host operating system at the time the application may be configured. | 11-14-2013 |
20140109092 | RUNNING ADD-ON COMPONENTS IN VIRTUAL ENVIRONMENTS - Systems and methods for running add-on components in virtual environments are described. An add-on component can be executed in a virtual environment by setting up a communication link between a component proxy in the host operating system and a server process running in the virtual environment. The server process executes the add-on component based on commands forwarded by the component proxy forwards the commands from the operating system. | 04-17-2014 |