Quest Software Inc.

Dell Software Inc.

Kiio Inc.

Chad Milton Lindley

Tomas Willis

Grigory Valerievich Vasiliev

Carl Jeffrey Rumachik

David J Grandin

Stewart Nutter

Lars James Lervik

Jason Coyne

Jon Obst

Lydia J Zeller

Brian Andrew Rossman

A computerized process for managing member participation and progression in a health engagement program including the steps of automatically validating eligible members, queuing for manual review and validation, members not automatically validated, and providing an interactive portal to enable an administrator to manually validate. Also, gathering with the assistance of a communication device in communication with a server, member screening information that includes access to equipment required for the health engagement program, and at least one medical factor associated with each member's health history. Further, stratifying, with the assistance of an application program in communication with the server, each of the validated members into risk categories based on the screening information gathered, and determining whether each validated member is appropriate for and suitable to continue with the health engagement program, and flagging, if deemed appropriate, each of the validated members indicating conditions for participation by analyzing the screening information.

System and process for managing participation and progression in health engagement programs

Methods, systems, and apparatuses for creating collections of associated accounts for a migration process. An example system includes a processing device and memory that stores accounts in accordance with a first email, identity or file domain. The processing device may create a collection of related accounts stored in accordance with a first email, identity or file domain based on active directory information of the stored accounts and may migrate information included in the collection of accounts into a second email, identity or file domain. The collection includes one or more first-level accounts that are identified as having a relationship with a predefined root account based on a delegation attribute.

Email and identity migration based on relationship information

A network-based solution for automatically processing large email attachments or other files during migration between email platforms or other platforms, as may be embodied by various systems, methods, and non-transitory computer-readable storage media, may involve downloading mailboxes from a source email platform and inspecting the mailboxes for emails containing attachment files. The solution may involve determining a file size of any detected attachment, comparing the file size of the detected attachment file to a predetermined attachment size limit, and uploading a copy of the detected attachment to a storage server for storage when the comparison determines that the file size of the detected attachment file exceeds the predetermined attachment size limit. The solution may further include modifying the email by replacing the detected attachment with a link to the copy of the detected attachment stored at the storage server and then migrating the modified email to the target email platform.

Automated large attachment processing during migration

Data loss prevention ('DLP') rules can be automatically applied to items during a migration. When a migration is performed, a migration engine may be configured with migration configuration settings which define the items to be migrated from the source system to the target system. The migration engine may also be configured with DLP configuration settings which define the type of items on which DLP should be performed. When the DLP configuration settings indicate that DLP should be applied to an item to be migrated, the migration engine routes the item to a DLP engine rather than directly migrating the item to the target system. After the DLP engine has processed the item, the DLP engine can return the processed item to the migration engine which in turn can migrate the processed item to the appropriate location in the target system.

Automatically applying data loss prevention rules during migration

During an email migration, a migration engine can identify which emails in the source system are associated with distribution lists. The migration engine can convert any emails that are associated with a distribution list into group content of an appropriate group in the target system. In contrast, for any email that is not associated with a distribution list, the migration engine can migrate the email into a corresponding mailbox in the target system.

During an email migration, converting distribution list messages into single-instanced content within a collaboration platform group

Access to admin credentials can be controlled during a migration. By controlling access to the admin credentials, a consultant can be allowed to perform migration tasks without the consultant being exposed to the administrative-level access necessary to perform such tasks. Accordingly, an organization can maintain complete control and visibility over the entire migration process, including how and when the admin credentials are used, while still being able to employ outside individuals or even inside individuals with reduced security or clearance levels in the process.

Growing community of inventors

Mt. Horeb, WI, United States of America

Chad Milton Lindley