<p><span style="font-size:16px"><strong>Custom Account Naming Convention</strong></span></p> <p><strong>Linux Custom Account Naming Convention</strong></p> <p><strong>Naming Requirements:</strong></p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; 1 to 32 characters.</p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; English characters, numbers, _ (underlines), and-(dashes) are allowed.</p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; -(dash) cannot appear at the beginning.</p> <p><strong>The following character strings can be used, but may already exist in the system, it is recommended to use other naming.</strong></p> <p>adm</p> <p>_apt</p> <p>backup</p> <p>bin</p> <p>daemon</p> <p>dnsmasq</p> <p>ftp</p> <p>games</p> <p>gnats</p> <p>gopher</p> <p>halt</p> <p>irc</p> <p>landscape</p> <p>list</p> <p>lp</p> <p>lxd</p> <p>mail</p> <p>man</p> <p>messagebus</p> <p>news</p> <p>nfsnobody</p> <p>nobody</p> <p>ntp</p> <p>operator</p> <p>pollinate</p> <p>postfix</p> <p>proxy</p> <p>qemu</p> <p>root</p> <p>rpc</p> <p>rpcuser</p> <p>saslauth</p> <p>shutdown</p> <p>sshd</p> <p>sync</p> <p>sys</p> <p>syslog</p> <p>systemd-network</p> <p>systemd-resolve</p> <p>tcpdump</p> <p>uucp</p> <p>uuidd</p> <p>vcsa</p> <p>www-data</p> <p>Windows Custom Account Naming Convention</p> <p><strong>Naming Requirements:</strong></p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; 1 to 32 characters.</p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; English characters, numbers, _ (underscore), and-(horizontal) are allowed.</p> <p>&bull;&nbsp;&nbsp;&nbsp;&nbsp; -(dash) cannot appear at the beginning.</p> <p><strong>Cannot contain these characters: &quot;/ \ [ ]:; | =, + *? &lt; &gt;</strong></p> <p><strong>The following accounts are security themes and service accounts built in Windows (not case sensitive) and are not recommended.</strong></p> <p>Administrator</p> <p>Administrators</p> <p>Guest</p> <p>Guests</p> <p>Backup Operators</p> <p>Certificate Service DCOM Access</p> <p>Cryptographic Operators</p> <p>Distributed COM Users</p> <p>Event Log Readers</p> <p>IIS_IUSRS</p> <p>Network Configuration Operators</p> <p>Performance Log Users</p> <p>Performance Monitor Users</p> <p>Power Users</p> <p>Print Operators</p> <p>Remote Desktop Users</p> <p>Replicator</p> <p>Users</p> <p>ANONYMOUS LOGON</p> <p>Authenticated Users</p> <p>BATCH</p> <p>CONSOLE LOGON</p> <p>CREATOR GROUP</p> <p>CREATOR OWNER</p> <p>DIALUP</p> <p>Digest Authentication</p> <p>ENTERPRISE DOMAIN CONTROLLERS</p> <p>Everyone</p> <p>INTERACTIVE</p> <p>IUSR</p> <p>LOCAL SERVICE</p> <p>NETWORK</p> <p>NETWORK SERVICE</p> <p>NTLM Authentication</p> <p>Other Organization</p> <p>OWNER RIGHTS</p> <p>PROXY</p> <p>REMOTE INTERACTIVE LOGON</p> <p>RESTRICTED</p> <p>SChannel Authentication</p> <p>SELF</p> <p>SERVICE</p> <p>SYSTEM</p> <p>TERMINAL SERVER USER</p> <p>This Organization</p> <p>&nbsp;</p> <p><strong><span style="font-size:16px">Disable Root / Administrator Account</span></strong></p> <p>When filling in the system configuration, Ping An Cloud supports users to choose whether to disable the root/administrator account. If the user chooses to disable it, you can log in to an ECS instance with a custom account and password.</p> <p><strong>Procedure</strong></p> <p>1．Log in to the ECS Console.</p> <p>2．In the left navigation pane, click <strong>Instance</strong> to enter the <strong>Instance Management</strong> page.</p> <p>3．In the upperright corner, click <strong>Create </strong>to enter the <strong>Create Instance</strong> page.</p> <p>4．Enter the relevant information, in the <strong>System Configuration, </strong>check the <strong>Disable root or administrator account, enter the Custom Account information, then click Next.</strong></p> <p>5．Click <strong>Purchase</strong> and enter <strong>Confirm Order</strong> page.</p> <p>6．After checking the order information, click <strong>Confirm Open</strong>, then enter the <strong>Payment Result</strong> page.</p>