IP Library Granted Patent US 10,776,489
Granted Patent B2
US 10,776,489 · App. 14/997,783 · Granted Sep 15, 2020

Methods and systems for providing and controlling cryptographic secure communications terminal operable to provide a plurality of desktop environments

Inventors: Steven L Rajcan (Malvern, PA); Matthew Mohr (Malvern, PA); Jim Trocki (Malvern, PA); Mark K Vallevand (Roseville, MN)
Assignee: Unisys Corporation
G06F21/575G06F9/442G06F9/4406G06F9/4408G06F9/4416G06F9/452G06F9/454G06F21/53G06F21/74H04L63/029H04L63/0428H04L63/08H04L67/025H04L67/306H04W12/06G06F9/441G06F21/31G06F2221/034H04L63/101
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,776,489
App. No.
14/997,783
Granted
Sep 15, 2020
Kind
B2
Abstract

Methods and systems for switching between multiple languages of a remote desktop client operating on a secure boot device are disclosed. A method includes initiating an operating system from the secure boot device and receiving credentials including a user identification and a password. The method also includes booting, from the secure boot device, the operating system in a first language and receiving a selection of a second language different from the first language within a user interface of the operating system. The method further includes performing a desktop reset to execute the operating system in the second language.

Claims (63)

1. A method for switching between multiple brandings of a remote desktop client operating on a secure boot device, the secure boot device storing a plurality of brandings for a user, the method comprising:

initiating an operating system from the secure boot device at the remote desktop client, the secure boot device comprising a portable storage device readable by the remote desktop client;

receiving credentials including a user identification and a password;

receiving a selection of a first branding among the plurality of brandings, each of the plurality of brandings associated with a different entity from which a user may receive authorization to operate the remote desktop client;

based on verification of the received credentials, booting, from the secure boot device, a desktop of the operating system in the selected first branding;

receiving a selection of a second branding different from the first branding from within the desktop; and

performing a desktop reset, wherein the desktop reset does not re-start the operating system initiated from the secure boot device and results in execution of the desktop in the second branding without requiring the user to re-enter credentials to operate the remote desktop client in the second branding,

wherein the desktop executed in the first branding presents the user with access to a first set of remote desktop client resources and the desktop executed in the second branding presents the user with access to a second set of remote desktop client resources that are different from the first set of remote desktop client resources, and

wherein access to the first and second sets of remote desktop client resources requires use of different sets of security parameters.

2. The method of claim 1 , wherein performing the desktop reset does not re-boot the operating system.

3. The method of claim 1 , wherein each branding is associated with a different context.

4. The method of claim 3 , wherein each context depends on a role of the user.

5. The method of claim 4 , wherein each context is associated with a particular branding and one or more application scripts, wherein each branding and application script is stored in the secure boot device.

6. The method of claim 1 , wherein the desktop reset further comprises:

shutting down a desktop of the remote desktop client; and

restarting the desktop of the remote desktop client in the selected branding.

7. The method of claim 1 , wherein the desktop reset further comprises:

shutting down the desktop based on receiving a shutdown command;

displaying a credentials screen from the secure boot device;

receiving credentials including a user identification and a password; and

based on verification of the received credentials, booting, from the secure boot device, the desktop in the selected branding.

8. A secure system for switching between multiple brandings of a remote desktop client operating on a secure boot device, the secure boot device storing a plurality of brandings for a user, the system comprising:

a client computer having a secure boot device connected thereto;

a remote server communicatively connected to the client computer via a communications network;

a trusted set of processing modules stored in the secure boot device that, when executed on the client computer, cause the client computer to:

initiate an operating system from the secure boot device at the client computer, the secure boot device comprising a portable storage device connected to and readable by the client computer;

receive credentials including a user identification and a password;

receive a selection of a first branding among the plurality of brandings, each of the plurality of brandings associated with a different entity from which a user may receive authorization to operate the remote desktop client;

based on verification of the received credentials, boot, from the secure boot device, a desktop of the operating system in the selected first branding;

receive a selection of a second branding different from the first branding from within the desktop; and

perform a desktop reset, wherein the desktop reset does not re-start the operating system initiated from the secure boot device and results in execution of the desktop in the second branding without requiring the user to re-enter credentials to operate the remote desktop client in the second branding,

wherein the desktop executed in the first branding presents the user with access to a first set of remote desktop client resources and the desktop executed in the second branding presents the user with access to a second set of remote desktop client resources that are different from the first set of remote desktop client resources, and

wherein access to the first and second sets of remote desktop client resources requires use of different sets of security parameters.

9. The secure system of claim 8 , wherein performing the desktop reset does not re-boot the operating system.

10. The secure system of claim 8 , wherein each branding is associated with a different context.

11. The secure system of claim 10 , wherein each context depends on a role of the user.

12. The secure system of claim 11 , wherein each context is associated with a particular branding and one or more application scripts, wherein each branding and application script is stored in the secure boot device.

13. The secure system of claim 8 , wherein the desktop reset further comprises:

shut down a desktop of the remote desktop client; and

restart the desktop of the remote desktop client in the selected branding.

14. The secure system of claim 8 , wherein the desktop reset further comprises:

shut down the desktop based on receiving a shutdown command;

display a credentials screen from the secure boot device;

receive credentials including a user identification and a password; and

based on verification of the received credentials, boot, from the secure boot device, the desktop in the selected branding.

15. A non-transitory computer storage medium comprising computer-executable instructions stored in a memory of a secure boot device operating on a remote desktop client and including a trusted set of processing modules which, when executed, cause a computing system to:

initiate an operating system from the secure boot device at the remote desktop client, the secure boot device comprising a portable storage device readable by the remote desktop client;

receive credentials including a user identification and a password;

receive a selection of a first branding among a plurality of brandings, each of the plurality of brandings associated with a different entity from which a user may receive authorization to operate the remote desktop client;

based on verification of the received credentials, boot, from the secure boot device, a desktop of the operating system in the selected first branding;

receive a selection of a second branding different from the first branding from within the desktop; and

perform a desktop reset, wherein the desktop reset does not re-start the operating system initiated from the secure boot device and results in execution of the desktop in the second branding without requiring the user to re-enter credentials to operate the remote desktop client in the second branding,

wherein the desktop executed in the first branding presents the user with access to a first set of remote desktop client resources and the desktop executed in the second branding presents the user with access to a second set of remote desktop client resources that are different from the first set of remote desktop client resources, and

wherein access to the first and second sets of remote desktop client resources requires use of different sets of security parameters.

16. The non-transitory computer storage medium of claim 15 , wherein performing the desktop reset does not re-boot the operating system.

17. The non-transitory computer storage medium of claim 15 , wherein each branding is associated with a different context.

18. The non-transitory computer storage medium of claim 17 , wherein each context depends on a role of the user.

19. The non-transitory computer storage medium of claim 18 , wherein each context is associated with a particular branding and one or more application scripts, wherein each branding and application script is stored in the secure boot device.

20. The non-transitory computer storage medium of claim 15 , wherein the desktop reset further comprises:

shut down the desktop based on receiving a shutdown command;

display a credentials screen from the secure boot device;

receive credentials including a user identification and a password; and

based on verification of the received credentials, boot, from the secure boot device, the desktop in the selected branding.

Assignments (8)
AMENDED AND RESTATED PATENT SECURITY AGREEMENT Recorded Jun 27, 2025
From: UNISYS CORPORATION; UNISYS HOLDING CORPORATION; UNISYS NPL, INC.; UNISYS AP INVESTMENT COMPANY I
To: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL TRUSTEE
Reel/Frame 071759/0527 →
SECURITY INTEREST Recorded Jun 14, 2021
From: UNISYS CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 056531/0150 →
RELEASE OF SECURITY INTEREST Recorded Oct 28, 2020
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: UNISYS CORPORATION
Reel/Frame 054231/0496 →
RELEASE OF SECURITY INTEREST Recorded Nov 9, 2017
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: UNISYS CORPORATION
Reel/Frame 044416/0114 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 23, 2017
From: RAJCAN, STEVEN L; MOHR, MATTHEW; TROCKI, JIM; VALLEVAND, MARK K
To: UNISYS CORPORATION
Reel/Frame 043924/0523 →
SECURITY INTEREST Recorded Oct 6, 2017
From: UNISYS CORPORATION
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 044144/0081 →
PATENT SECURITY AGREEMENT Recorded Apr 27, 2017
From: UNISYS CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL TRUSTEE
Reel/Frame 042354/0001 →
SECURITY INTEREST Recorded Jun 3, 2016
From: UNISYS CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 038792/0820 →
Continuity (8)
Continuation In Part 13105154 · May 11, 2011
Continuation In Part 11714598 · Mar 6, 2007
Provisional Application 62266068 · Dec 11, 2015
Provisional Application 62266053 · Dec 11, 2015
Provisional Application 62266063 · Dec 11, 2015
Provisional Application 61389511 · Oct 4, 2010
Provisional Application 61389535 · Oct 4, 2010
Related Publication 20170169226A1 · Jun 15, 2017
Cited By (1)
US 12,289,308