diff options
author | PMR <pmr@pmr-lander> | 2021-07-13 06:30:40 +0000 |
---|---|---|
committer | PMR <pmr@pmr-lander> | 2021-07-13 06:30:40 +0000 |
commit | 7630fdfdad2fde0e99d489e97b05ce333dddc509 (patch) | |
tree | 228f63bb251e8314f52c664d227534b2fc0436f3 | |
parent | 94ff36fd399cb23d18d5fb21526411f7b972fac1 (diff) | |
parent | c69970e78b0919d6ea738edc1fc5c3f6a5c4ab5b (diff) |
Merge #405613 from ~pieq/oem-qa-checkbox:active-directory-generic
-rw-r--r-- | units/wenshan/jobs.pxu | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/units/wenshan/jobs.pxu b/units/wenshan/jobs.pxu index add042e..03a5eb8 100644 --- a/units/wenshan/jobs.pxu +++ b/units/wenshan/jobs.pxu @@ -20,7 +20,7 @@ _steps: 1. Edit the /etc/systemd/timesyncd.conf file to point to the NTP server, and make sure the Root Distance value is high enough, e.g.: [Time] - NTP=ad.wenshan.biz + NTP=ad.myserver.biz RootDistanceMaxSec=15 2. Restart the time sync service: systemctl restart systemd-timesyncd.service @@ -81,7 +81,7 @@ depends: active-directory/realm-list estimated_duration: 1m _summary: Join a realm _purpose: - Check that the device can join the Active Directory realm (e.g. ad.wenshan.biz). + Check that the device can join the Active Directory realm (e.g. ad.myserver.biz). _steps: 1. Enter the command to join the realm: $ sudo realm join <AD_SERVER> @@ -184,7 +184,7 @@ _steps: 1. Make sure you are connected on the same network as the Active Directory server. 2. During the installation, check "Use Active Directory". - 3. Use the credentials of your Active Directory test user (e.g. user1@wenshan.biz) + 3. Use the credentials of your Active Directory test user (e.g. user1@myserver.biz) _verification: The installation completes and you can log in using your Active Directory credentials. @@ -201,10 +201,10 @@ _steps: 1. In a terminal, switch to super user, then enter the login command: $ sudo -i # login - 2. Enter the AD test user account (e.g. user1@wenshan.biz) + 2. Enter the AD test user account (e.g. user1@myserver.biz) 3. Enter the password of your Active Directory test user (e.g. user1) _verification: - Check that a home directory is created for user user1@wenshan.biz and user + Check that a home directory is created for user user1@myserver.biz and user can type commands on the device (ls, date, etc.). id: active-directory/login-gui @@ -218,7 +218,7 @@ _purpose: _steps: 1. Select “Log Out” or “Switch User…” from the Power Menu > "Power Off / Log Out" entry 2. Select “Not listed?” - 3. Enter username (e.g. user1@wenshan.biz) + 3. Enter username (e.g. user1@myserver.biz) 4. Enter password and press Enter _verification: User can log in and access Ubuntu. @@ -242,11 +242,11 @@ _steps: > Account Policies > Password Policy, modify something (e.g. set "Minimum password length" to a higher value) 4. Open "Active Directory Users and Computers" - 5. Right click on an existing user (e.g. user1@wenshan.biz), select "Properties...", + 5. Right click on an existing user (e.g. user1@myserver.biz), select "Properties...", and in "Account", check "User must change password at next login" . B. On the Ubuntu client (either graphically or in a terminal): - 1. Log in using the user credentials modified in Windows Server (e.g. user1@wenshan.biz) + 1. Log in using the user credentials modified in Windows Server (e.g. user1@myserver.biz) 2. When prompted for a new password, try to type one that does not match the requirements set in step A3 3. Use a password that matches the requirements set in step A3 @@ -270,7 +270,7 @@ _purpose: _steps: 1. Disconnect from the network where the AD server is located 2. Select “Log Out” or “Switch User…” from the Power Menu > "Power Off / Log Out" entry - 3. Enter username (e.g. user1@wenshan.biz) + 3. Enter username (e.g. user1@myserver.biz) 4. Enter password and press Enter _verification: User can log in and access Ubuntu. |