Dynamic runtime interface for device management
US-10637957-B2 · Apr 28, 2020 · US
US10778666B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10778666-B2 |
| Application number | US-201916526002-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 30, 2019 |
| Priority date | Dec 9, 2016 |
| Publication date | Sep 15, 2020 |
| Grant date | Sep 15, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Various examples for performing automated enrollments of client devices with a management service after being accessed by a staging user account are described. A client device can be configured to identify a user account active on the client device and determine whether the user account is a staging user account or an end user account associated with an intended recipient of the client device. In an instance in which the user account is the staging user account, the client device can create an event listener on the client device that monitors a subsequent login of a user account performed through an operating system of the client device, the subsequent login of the user account being the end user account. In an instance in which the subsequent login of the user account is detected by the event listener, the client device can perform an automated enrollment with a remote management service.
Opening claim text (preview).
Therefore, the following is claimed: 1. A system, comprising: a client device; and program instructions stored in memory and executable in the client device that, when executed, direct the client device to: identify a user account active on the client device; determine whether the user account is a staging user account or an end user account associated with an intended recipient of the client device; in an instance in which the user account is the staging user account, create an event listener on the client device that monitors a subsequent login of a user account performed through an operating system of the client device, the subsequent login of the user account being the end user account; identify, by the event listener, a domain and a user handle from the subsequent login; and in an instance in which the subsequent login of the user account is detected by the event listener, perform an automated enrollment of the client device with a remote management service, wherein the automated enrollment is performed using at least one of the domain and the user handle identified from the subsequent login. 2. The system of claim 1 , wherein the automated enrollment comprises sending the domain and the user handle to the remote management service to enroll the client device with the remote management service. 3. The system of claim 2 , wherein the remote management service is configured to, in an instance in which the domain and the user handle are received from the client device, identify an existing user account of the remote management service as the end user account or create a new user account based at least in part on the domain and the user handle. 4. The system of claim 1 , wherein the event listener is further configured to detect an identifier on the client device that uniquely identifies the client device and send the identifier to the remote management service. 5. The system of claim 4 , wherein the identifier is obtained from a registry of the client device. 6. The system of claim 1 , wherein the user account is determined as the staging user account based at least in part on a current user identified from an operating system of the client device. 7. The system of claim 1 , wherein the domain and the user handle are parsed from an email address obtained during the subsequent login. 8. A method, comprising: identifying a user account active on a client device; determining whether the user account is a staging user account or an end user account associated with an intended recipient of the client device; in an instance in which the user account is the staging user account, creating an event listener on the client device that monitors a subsequent login of a user account performed through an operating system of the client device, the subsequent login of the user account being the end user account; identifying, by the event listener, a domain and a user handle from the subsequent login; and in an instance in which the subsequent login of the user account is detected by the event listener, performing an automated enrollment of the client device with a remote management service, wherein the automated enrollment is performed using at least one of the domain and the user handle identified from the subsequent login. 9. The method of claim 8 , wherein the automated enrollment comprises sending the domain and the user handle to the remote management service to enroll the client device with the remote management service. 10. The method of claim 9 , further comprising, in an instance in which the domain and the user handle are received from the client device, identifying, by the remote management service, an existing user account of the remote management service as the end user account or create a new user account based at least in part on the domain and the user handle. 11. The method of claim 8 , further comprising detecting, by the event listener, an identifier on the client device that uniquely identifies the client device and sending the identifier to the remote management service. 12. The method of claim 11 , wherein the identifier is obtained from a registry of the client device. 13. The method of claim 8 , wherein the user account is determined as the staging user account based at least in part on a current user identified from an operating system of the client device. 14. The method of claim 8 , further comprising parsing an email address obtained during the subsequent login to identify the domain and the user handle. 15. A non-transitory computer-readable medium embodying program instructions executable in a client device having at least one hardware processor that, when executed by the client device, direct the client device to: identify a user account active on the client device; determine whether the user account is a staging user account or an end user account associated with an intended recipient of the client device; in an instance in which the user account is the staging user account, create an event listener on the client device that monitors a subsequent login of a user account performed through an operating system of the client device, the subsequent login of the user account being the end user account; identify, by the event listener, a domain and a user handle from the subsequent login; and in an instance in which the subsequent login of the user account is detected by the event listener, perform an automated enrollment of the client device with a remote management service, wherein the automated enrollment is performed using at least one of the domain and the user handle identified from the subsequent login. 16. The non-transitory computer-readable medium of claim 15 , wherein the automated enrollment comprises sending the domain and the user handle to the remote management service to enroll the client device with the remote management service. 17. The non-transitory computer-readable medium of claim 16 , wherein the remote management service is configured to, in an instance in which the domain and the user handle are received from the client device, identify an existing user account of the remote management service as the end user account or create a new user account based at least in part on the domain and the user handle. 18. The non-transitory computer-readable medium of claim 15 , wherein the event listener is further configured to detect an identifier on the client device that uniquely identifies the client device and send the identifier to the remote management service. 19. The non-transitory computer-readable medium of claim 18 , wherein: the identifier is obtained from a registry of the client device; and the user account is determined as the staging user account based at least in part on a current user identified from an operating system of the client device. 20. The non-transitory computer-readable medium of claim 15 , wherein the domain and the user handle are identified from an email address obtained during the subsequent login.
User registration · CPC title
by adding security routines or objects to programs · CPC title
Structures or tools for the administration of authentication · CPC title
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.