10997B Lab Ak 03
10997B Lab Ak 03
5. Click the Previous button.
3. Click the Connectors tab.
4. In the Connectors tab, double-click Adatum.com.
6. Click Containers.
User name: Administrator
Password: Pa55w.rd
Domain: Adatum.com
22. Click Next.
25. Click Next.
31. To save the rule, click Add, and then close the Synchronization Rules
Editor window.
7. Click Add a group.
1. In the Microsoft 365 admin center, verify that you can see groups that are synced with
your on-premises Active Directory and that you can see the following groups created
in cloud:
Production
Accounts
5. Click Delete group.
Result: After completing this exercise, you should have created users and groups in
Office 365 and managed user licenses.
1. On the navigation menu in the Office 365 admin portal, point to Settings, and
then click Security & privacy.
Note: You would not do this in the real world. This is a classroom example that allows
you to verify the policy applied in the next exercise task.
4. On the upper-right side of the window, verify that the notification appears
with the following information: Time to change your password. Your
password will expire in 13 days.
Note: It might take a several minutes before the password change notification
appears. You can safely proceed with other tasks in this lab even if you don't get
notification.
Note: You have now verified that your password policy is applied. In a real-world
scenario, after you verified that the password policy was applied, you would need to
increase the number of days before the password expired, according to your
organizational policy.
Result: After completing this exercise, you should have configured the Office 365
password policy and validated the policy.
2. In the Windows PowerShell prompt, type the following command, and then
press Enter:
CD C:\Labfiles\Mod03\
3. At the Windows PowerShell prompt, type the following command, and then press
Enter:
Set-ExecutionPolicy Unrestricted
5. At the Windows PowerShell prompt, type the following command, and then
press Enter:
.\Mod3_CreateProblem.ps1
Note: Wait until the script completes and notice the following changes.
This Windows PowerShell script will make the following changes in AD DS:
Klemen Sic. Adds the "@" character to the beginning of "Adatum" for
the UserPrincipalName attribute.
11. Click the ERROR column to sort the character errors to the top of the list.
Note: Ignore top-level domain errors, which cannot be fixed by the IdFix tool.
12. In the Klemen Sic row, verify the proposed solution in the UPDATE column, and then
in the ACTION column, select EDIT.
13. In the Lara Raisic row, verify the proposed solution in the UPDATE column, and then
in the ACTION column, select EDIT.
14. In the Logan Boyle row, verify the proposed solution in the UPDATE column, and
then in the ACTION column, select EDIT. In the Update column for Logan Boyle,
type [email protected].
15. In the Maj Hojski row, verify the proposed solution in the UPDATE column, and then
in the ACTION column, select EDIT.
16. On the toolbar, click Apply.
17. In the Apply Pending dialog box, click Yes. Notice the COMPLETE status in
the ACTION column, which indicates successful writes.
18. Switch to File Explorer, and in the C:\Deployment Tools\IdFix folder, double-
click Verbose <date> <time>.txt to view the updated transactions in the transaction
log.
19. Switch back to the IdFix tool.
20. On the toolbar, click Query.
21. Click in the UPDATE column to locate the Maj Hojski error, replace the string
with [email protected], and then in theACTION column, select EDIT.
22. For An Dung and Ngoc Bich, select EDIT in the ACTION column.
23. On the toolbar, click Apply.
24. In the Apply Pending dialog box, click Yes.
25. On the toolbar, click Query, and then verify that the errors are corrected. If you see
other errors present, correct them using the same method.
Note: Where there are format and duplicate errors for distinguished names,
the UPDATE column either contains the same string as the VALUE column, or
the UPDATE column entry is blank; in either case, this means that IdFix cannot
suggest a remediation for the error. You can either fix these errors outside of IdFix or
manually remediate them within IdFix. You can also export the results and use
Windows PowerShell to remediate a large number of errors.
Result: After completing this exercise, you should have troubleshot synchronization
issues with user objects in Office 365.