Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Embodiments described herein are directed to enabling a user to modify data stored locally during a data migration process in which the user's data is being transferred to the cloud. For instance, a synchronization service requests the user's device (e.g., a client-based server) to provide a hash value for each data object maintained thereby (including modified data objects) and compares the hash values to hash values generated for the data uploaded to the cloud. If a hash value provided by the server does not match any of the hash values generated for the uploaded data, this means that the data object associated with the unmatched hash value has been modified since the initiation of the data transfer process. The synchronization service receives the modified data object from the server and uploads it to the cloud, thereby synchronizing the data uploaded to the cloud with the data locally-maintained by the server.

Abstract: Embodiments described herein are directed to enabling a user to modify data stored locally during a data migration process in which the user's data is being transferred to the cloud. For instance, a synchronization service requests the user's device (e.g., a client-based server) to provide a hash value for each data object maintained thereby (including modified data objects) and compares the hash values to hash values generated for the data uploaded to the cloud. If a hash value provided by the server does not match any of the hash values generated for the uploaded data, this means that the data object associated with the unmatched hash value has been modified since the initiation of the data transfer process. The synchronization service receives the modified data object from the server and uploads it to the cloud, thereby synchronizing the data uploaded to the cloud with the data locally-maintained by the server.

Abstract: Techniques for facilitating telemetry driven configuration of software products in computing systems are disclosed herein. In one embodiment, a method can include transmitting an indication of a software product entering a configuration mode for a configuration parameter of the software product to a server. The method can also include receiving, from the server, a list of values for the configuration parameter each previously adopted by additional users for the same configuration parameter of the software product and displaying, on a user interface, the received list of values for the configuration parameter and indicating that one of the displayed values in the list is most commonly adopted by the additional users.

Abstract: Methods, systems, and apparatuses are described for dynamic management of file system objects (e.g., a file or a directory). Such management includes syncing, routing, and storing capabilities. A file system object may be tagged with one or more tags based on at least one of file system object content or file system object location. Dynamic rules that control routing of file system objects to one or more locations based on the one or more tags are accessed and searched for an applicable rule. The file system object may be routed and/or stored based on the applicable rule. The rules may specify allowable locations as well as locations that are not allowed for a given file system object. The location may be a cloud-based location, a location that is on the premises of the enterprise, a location provided by and/or serviced by a competing entity, etc.

Abstract: Techniques for facilitating telemetry driven configuration of software products in computing systems are disclosed herein. In one embodiment, a method can include transmitting an indication of a software product entering a configuration mode for a configuration parameter of the software product to a server. The method can also include receiving, from the server, a list of values for the configuration parameter each previously adopted by additional users for the same configuration parameter of the software product and displaying, on a user interface, the received list of values for the configuration parameter and indicating that one of the displayed values in the list is most commonly adopted by the additional users.

Abstract: A method and system for e-mail message user notes. E-mail servers may attach and store user notes with e-mail messages. An e-mail server may store user notes as part of user-profiles. Servers may provide notes to e-mail clients as e-mail header fields in e-mail messages and may generate custom header field names from user input. E-mail servers may associate notes with messages only when communicating with a specific e-mail client or may provide different notes for different e-mail clients. E-mail servers may provide custom views including user notes to web browser based e-mail clients. E-mail clients may allow users to specify a set of predefined notes from which specific notes may later be attached to e-mail messages.