Prerequisites:

1. Both the controlling and controlled ends need to use the latest version of the client, version v1.3.2 or above.

2. The controlling client must have SOS remote permissions. 

   
   

In many enterprises, office computers do not have administrator rights. However, in IT remote technical support, when performing administrative tasks, the lack of administrator rights on the controlled computer can affect the remote control operations.

DeskIn Enterprise Edition's Solution:

• The SOS endpoint supports running without administrator privileges.

• IT personnel with administrator rights can temporarily elevate the SOS program to run with administrator privileges during the remote session, allowing tasks like installing/uninstalling software and other high-level operations to be carried out successfully.

• After the remote session ends, the elevated privileges are immediately revoked for secure remote control.  

  
  

Supported Side (Controlled SOS Endpoint)

1. Receive link from Control Client

2. Download respective no-installation package

3. Double click to initialize SOS. When there are no administrator privileges, click "No" in the User Account Control pop-up to start.  If no pop-up appears, find the SOS icon in the system tray (bottom-right corner) and double-click to bring it up.

4. On Controller Client side, Enter the 8-digit code on the SOS Support page of the controlling side and wait for the controlled side's consent.

5. After the controlled SOS endpoint clicks "Agree," click Apply System Administrator Privileges in the pop-up window on the taskbar.

Enter the system administrator account and password in the pop-up window (fill in domain information if needed; for local administrator accounts, enter the controlled endpoint's computer name, not \administrator).

Reminder: When entering the local account for the controlled endpoint, you do not need to include the backslash (\\). For example, if the account is administrator, simply enter administrator without the backslash. Do not enter \administrator.

The controlled side (SOS endpoint) will then receive a User Account Control pop-up asking to confirm. Click "Yes." 

Once confirmed, the controlling side will have system administrator privileges to run the controlled desktop program.  

Remote control operations can proceed normally. When applications or operations require system administrator privileges, the controlling side can enter the administrator account and password as needed.

SOS Privilege Elevation Successful!

Notes: Privilege Elevation Verification Account and Password 

1. If using the controlled endpoint's local account and password, ensure the full computer name is provided (no \ needed before administrator, just input administrator).

2. If using domain account and password, the domain suffix needs to be included. 

3. If the controlled endpoint has UAC (User Account Control) enabled, after entering the password, the controlled endpoint must click "Yes" to confirm. If UAC is disabled, there might be no prompt, or privilege elevation could fail. 

4. After successful elevation, if the program goes black and you cannot input the username and password, right-click the program and select Run as different user to enter the corresponding account and password.