Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Creating a Binding Relationship

Updated on 2024-10-23 GMT+08:00

Scenario

To restrict the application scenarios of a desktop, the administrator can bind the MAC address of a terminal to a desktop so that only the bound terminal can be used to log in to the desktop.

Constraints

This feature is not applicable to Android mobile terminals and Android TCs.

Prerequisites

Procedure

  1. Log in to the console.
  2. In the navigation pane, choose Policies > Terminal and Desktop Binding.

    The terminal-desktop binding list is displayed.

  3. Record the binding relationship.

    You can manually enter binding relationships or enter binding relationships in batches based on the number of binding relationships.
    • Manual Entry

      If a small number of desktops need to be bound to terminals, you can manually enter the information.

      1. Click Manual entry.
      2. On the displayed page, enter the MAC address, desktop name, and description, as shown in Figure 1.
        NOTE:
        • The MAC address format is xx-xx-xx-xx-xx-xx.
        • One MAC address can be bound to multiple desktops.
        • A desktop can be bound to multiple MAC addresses.
        • Information cannot be entered if there are more than 8,000 binding relationships.
        Figure 1 Entering binding information
      3. If multiple terminals need to be bound, click Add Rows to add binding information.
      4. Click OK.
    • Batch Entry

      If a large number of desktops need to be bound to terminals, you can batch enter the information.

      1. Click Batch Entry.
      2. On the displayed page, click Download Template.
      3. Open the downloaded template and enter the serial number, MAC address, desktop name, and description, as shown in Figure 2.
        NOTE:
        • The MAC address format is xx-xx-xx-xx-xx-xx.
        • One MAC address can be bound to multiple desktops.
        • A desktop can be bound to multiple MAC addresses.
        • The maximum size of a file to be uploaded at a time is 1 MB, and only the .xlsx format is supported.
        • Information cannot be entered if there are more than 8,000 binding relationships. Information of up to 1,000 binding relationships can be entered at a time.
        Figure 2 Batch entering binding information
      4. Save and close the template file containing the binding information.
      5. On the page of batch entering information, click Upload.
      6. Select the file in which the binding information has been filled in 3.d and click Open.

        The system verifies the correctness of the imported information and compares the information with that of the existing binding relationships.

        • If a message indicating successful upload is displayed, the binding relationships in the file have been uploaded to the system. After clicking Close, you can view the uploaded binding relationships on the Terminal and Desktop Binding page.
        • If a message indicating failed upload is displayed, the binding relationships in the file were not uploaded to the system. You can click Details to check the exception cause, modify the uploaded file according to the exception cause, and upload the file again by referring to 3.d to 3.f. If some binding relationships pass the verification, you can click OK to upload the verified binding relationships to the system. If you click Cancel, the batch upload is canceled.

          NOTE:

          If the format of the imported information is correct and the information does not conflict with the existing binding relationships in the system, but the system still displays a message indicating that the upload fails, click Upload Again to try again. If the upload still fails, submit a service ticket for technical support.

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback