Dell Products Inc.

Wyse Technology Inc.

Sumit Popli

Suruchi Dubey

Ryan Mason

Puneet Kaushik

Salil Joshi

Jigar Shah

Oleg Rombakh

Varun Raghavan

An application can be dynamically selected to open a file. An application broker service can be configured to received intercepted requests to open files. The application broker service can process the intercepted requests to determine a type and location of the files to be opened. Using the type and the location of the files to be opened, the application broker service can select applications to open the files. If a file fails to open in a selected application, the application broker service can select another application to open the file.

Dynamically selecting an application to open a file

An agent can be employed on write filter enabled devices to retrieve a default configuration from a server when a user logs in. The default configuration can define which user configuration settings are persist-able. After the user has customized user configuration settings, the agent can identify customizations to any persist-able user configuration setting and create a delta configuration to define these customizations. The agent can send the delta configuration to a server so that it will be available when the user logs in to any other write filter enabled device. At any subsequent login, the agent can retrieve the delta configuration and use it to customize the user configuration settings. In this way, a set of customized user configurations settings can be persisted and applied on any write filter enabled device that a user may log in to.

Persisting user configuration settings on write filter enabled devices

A system and method for identifying write filter exclusions for information handling systems in a computing environment. Each information handling system includes a file exclusion driver and a file exclusion service. The file exclusion driver can monitor files to be stored in a write filter overlay and identify recurring files previously stored in the write filter overlay. The file exclusion driver can determine if a cumulative file size of a recurring file exceeds an adjustable threshold, and add data describing the recurring file to an exclusion list if the cumulative file size exceeds the adjustable threshold. The file exclusion service can transmit the exclusion list to the device management server for analysis, receive a master exclusion list from the device management server based on analysis, and can store a set of excluded files in a local storage resource based on the master exclusion list.

Identifying file exclusions for write filter overlays

In one or more embodiments, one or more system, methods, and/or processes may receive first data associated with a first write operation; may determine if a first amount of data that has been written to a non-volatile solid state storage device (NVSSSD) within a first amount of time has reached or exceeded a first threshold amount; if the first amount of data that has been written to the NVSSSD within the first amount of time has not reached or exceeded the first threshold amount: may store the first data to the NVSSSD and may increment a counter by an amount of the first data; and if the first amount of data that has been written to the NVSSSD within the first amount of time has reached or exceeded the first threshold amount, may store the first data to an overlay of a volatile memory medium.

System and method of utilizing a non-volatile solid state storage device

Access to functionality of a file-based write filter can be secured. A policy-based filter can be configured to monitor and filter calls to APIs that access functionality of the file-based write filter. Based on policy, the policy-based filter can selectively block such calls to ensure that only permitted applications and/or users are allowed to access the functionality of the file-based write filter. In some cases, the policy-based filter can be configured to communicate with a server component to determine whether a particular attempt to access the functionality of the file-based write filter should be allowed.

Securing access to functionality of a file-based write filter

Systems and methods are provided that may be implemented to prevent unexpected and/or uncontrollable system reboots that occur due to write filter overlay and/or RAM disk depletion within system memory of an information handling system by monitoring time-based write filter memory overlay and/or RAM disk usage. This information may be used to predict when the write filter memory overlay and/or RAM disk will fill up with data, and/or to take actions to prevent write filter memory overlay and/or RAM disk usage from reaching a threshold percentage or fractional utilization value that will trigger a system reboot. Those applications and/or data files that are primarily responsible for filling the memory of a write filter overlay may also be identified and stopped or restarted to prevent automatic system reboot due to write filter memory overlay usage.

Systems and methods for improved write filter operation with provision for monitoring and prediction to delay system reboot

Authentication can be performed on thin clients using independent mobile devices. Because many users have smart phones or other similar mobile devices that include biometric scanners, such mobile devices can be leveraged to perform authentication of users as part of logging in to a thin client desktop. A mapping can be created on a central server between a user's mobile device and the user's domain identity. A mapping can also be created between the user's domain identity and the user's thin client desktop. Then, when a user desires to log in to his thin client desktop, the user can employ the appropriate biometric scanner on his mobile device to perform authentication. The central server can then rely on this authentication to identify and log the user into his thin client desktop.

Authentication on thin clients using independent devices

A write filter can be configured to employ a dynamically expandable overlay. The size of the overlay could initially be small and could then grow and shrink during the current session based on demand. The overlay can span both RAM and disk to thereby allow the size of the overlay to be relatively large. When sufficient RAM is available, the overlay can be allowed to grow in RAM. In contrast, if RAM is low, the overlay can grow on disk. Also, artifacts in the overlay can be moved from the RAM portion to the disk portion to reduce the amount of RAM consumed by the overlay. Because the overlay is dynamically expandable, it will typically not become full and will therefore not force a reboot.

Write filter with dynamically expandable overlay

In particular embodiments, a server computing device receives one or more inputs specifying a software module and one or more portions of a network. Each of the portions of the network includes multiple client devices. For each of the client devices in a portion of the network, the server computing device determines whether the client device meets one or more criteria. For at least one portion of the network having a client device meeting the one or more criteria, the server computing device selects the client device as a master device and provides the software module to the master device. The master device is operable to download the software module from one or more server computing devices, provide the software module to the other client devices in the portion of the network, and provide status information to the server computing device.

Growing community of inventors

Campbell, CA, United States of America

Sumit Popli