Get-ADUser in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get all users from Active Directory.

PowerShell

Get-ADUser [1]

Drag options to blanks, or click blank then click option'

A-AllUsers

B-Name *

C-Filter *

D-List *

Attempts:

3 left

💡 Hint

Common Mistakes

Using -Name * which is not a valid parameter for listing all users.

Using -AllUsers which does not exist.

Using -List * which is invalid.

The -Filter * parameter tells Get-ADUser to retrieve all users.

2fill in blank

medium

Complete the code to get a user with the username 'jdoe'.

PowerShell

Get-ADUser -Identity [1]

Drag options to blanks, or click blank then click option'

Auser1

BJohn Doe

CJDoe123

Djdoe

Attempts:

3 left

💡 Hint

Common Mistakes

Using the full name instead of username.

Using an incorrect username.

The -Identity parameter accepts the username or distinguished name. Here, 'jdoe' is the username.

3fill in blank

hard

Fix the error in the code to get users with the last name 'Smith'.

PowerShell

Get-ADUser -Filter "[1]"

Drag options to blanks, or click blank then click option'

ASurname -eq 'Smith'

BLast -eq 'Smith'

CLastName -eq 'Smith'

DName -eq 'Smith'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'LastName' which is not a valid property.

Using 'Name' which is the full name, not last name.

The correct property for last name in Get-ADUser filter is Surname.

4fill in blank

hard

Fill both blanks to get users whose account is enabled and have 'Admin' in their title.

PowerShell

Get-ADUser -Filter "Enabled -eq [1] -and Title -like '[2]'"

Drag options to blanks, or click blank then click option'

ATrue

BFalse

C*Admin*

DAdmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'False' for enabled accounts.

Not using wildcards for partial title match.

To filter enabled accounts, use Enabled -eq True. To find titles containing 'Admin', use wildcard *Admin* with -like.

5fill in blank

hard

Fill all three blanks to create a dictionary of usernames and their email addresses for users in the 'Sales' department.

PowerShell

$users = Get-ADUser -Filter "Department -eq '[1]'" -Properties [2]
$userEmails = @{ }
[3]

Drag options to blanks, or click blank then click option'

ASales

BEmailAddress

Cforeach ($u in $users) { $u.SamAccountName = $u.EmailAddress }

Dforeach ($u in $users) { $userEmails[$u.SamAccountName] = $u.EmailAddress }

Attempts:

3 left

💡 Hint

Common Mistakes

Not requesting the EmailAddress property, so emails are missing.

Incorrect loop syntax or assignment inside the loop.

Using wrong department name.

Filter users by department 'Sales'. Request the 'EmailAddress' property. Then build a dictionary mapping usernames (SamAccountName) to emails.

Practice

1. What does the Get-ADUser cmdlet do in PowerShell?

easy

A. Creates a new Active Directory user

B. Retrieves information about Active Directory users

C. Deletes an Active Directory user

D. Modifies an Active Directory user's password

Solution

1. Step 1: Understand the purpose of Get-ADUser

   The cmdlet is designed to fetch or retrieve user information from Active Directory.

2. Step 2: Compare with other cmdlets

   Creating, deleting, or modifying users are done by other cmdlets like New-ADUser or Set-ADUser, not Get-ADUser.

3. Final Answer:

   Retrieves information about Active Directory users -> Option B

4. Quick Check:

   Get-ADUser = Retrieve user info [OK]

Hint: Get-ADUser always fetches user info, not changes [OK]

Common Mistakes:

• Confusing Get-ADUser with New-ADUser
• Thinking it modifies user data
• Assuming it deletes users

2. Which of the following is the correct syntax to get a user by their username using Get-ADUser?

easy

A. Get-ADUser -Identity "jdoe"

B. Get-ADUser -Name "jdoe"

C. Get-ADUser -UserName "jdoe"

D. Get-ADUser -User "jdoe"

Solution

1. Step 1: Identify the correct parameter for a single user

   The -Identity parameter is used to specify a single user by username or distinguished name.

2. Step 2: Check other parameters

   Parameters like -Name, -UserName, or -User are not valid for Get-ADUser to specify a single user.

3. Final Answer:

   Get-ADUser -Identity "jdoe" -> Option A

4. Quick Check:

   -Identity = single user [OK]

Hint: Use -Identity to specify one user by username [OK]

Common Mistakes:

• Using -Name instead of -Identity
• Trying -UserName which is invalid
• Confusing parameter names

3. What will this command output?

Get-ADUser -Filter 'Enabled -eq $true' -Properties EmailAddress | Select-Object Name, EmailAddress

medium

A. List of disabled users with their names and email addresses

B. List of all users with only their names

C. List of enabled users with their names and email addresses

D. Error because EmailAddress is not a valid property

Solution

1. Step 1: Understand the filter condition

   The filter Enabled -eq $true selects only users who are enabled (active).

2. Step 2: Check properties and output

   The command requests the EmailAddress property and selects to display Name and EmailAddress for each user.

3. Final Answer:

   List of enabled users with their names and email addresses -> Option C

4. Quick Check:

   Filter enabled + EmailAddress shown = List of enabled users with their names and email addresses [OK]

Hint: Filter enabled users and add -Properties for extra fields [OK]

Common Mistakes:

• Forgetting to add -Properties EmailAddress
• Assuming it lists disabled users
• Thinking EmailAddress is invalid property

4. You run this command but get an error:

Get-ADUser -Filter "Name -like '*Smith'" -Properties Email

What is the likely cause?

medium

A. The property 'Email' does not exist; it should be 'EmailAddress'

B. The filter syntax is incorrect; should use single quotes inside double quotes

C. Get-ADUser cannot filter by Name

D. Missing -Identity parameter

Solution

1. Step 1: Check the property name

   The correct property for user email is EmailAddress, not Email.

2. Step 2: Validate filter and parameters

   The filter syntax is valid and filtering by Name is allowed. The -Identity parameter is not required when using -Filter.

3. Final Answer:

   The property 'Email' does not exist; it should be 'EmailAddress' -> Option A

4. Quick Check:

   Wrong property name causes error [OK]

Hint: Use correct property names like EmailAddress, not Email [OK]

Common Mistakes:

• Using wrong property names
• Misunderstanding filter syntax
• Thinking -Identity is mandatory with -Filter

5. You want to list all users in the 'Sales' department with their names and phone numbers. Which command will do this correctly?

hard

A. Get-ADUser -Filter 'Department -like Sales' | Select Name, PhoneNumber

B. Get-ADUser -Identity 'Sales' -Properties Phone | Select Name, Phone

C. Get-ADUser -Filter 'Department = Sales' -Properties PhoneNumber | Select-Object Name, PhoneNumber

D. Get-ADUser -Filter 'Department -eq "Sales"' -Properties TelephoneNumber | Select-Object Name, TelephoneNumber

Solution

1. Step 1: Use correct filter syntax for department

   The filter Department -eq "Sales" correctly matches users in Sales department.

2. Step 2: Include correct property and select output

   Use -Properties TelephoneNumber to get phone numbers, then select Name and TelephoneNumber for output.

3. Step 3: Check other options for errors

   Get-ADUser -Identity 'Sales' -Properties Phone | Select Name, Phone uses -Identity incorrectly and wrong property names. Get-ADUser -Filter 'Department -like Sales' | Select Name, PhoneNumber has wrong filter syntax and property names. Get-ADUser -Filter 'Department = Sales' -Properties PhoneNumber | Select-Object Name, PhoneNumber uses '=' instead of '-eq' and wrong property names.

4. Final Answer:

   Get-ADUser -Filter 'Department -eq "Sales"' -Properties TelephoneNumber | Select-Object Name, TelephoneNumber -> Option D

5. Quick Check:

   Filter with -eq + correct property = Get-ADUser -Filter 'Department -eq "Sales"' -Properties TelephoneNumber | Select-Object Name, TelephoneNumber [OK]

Hint: Use -Filter with -eq and add -Properties for extra fields [OK]

Common Mistakes:

• Using wrong filter operators like '='
• Wrong property names like Phone instead of TelephoneNumber
• Misusing -Identity for filtering