Phonetic attributes in Active Directory

Sometimes you come across a user account or maybe a resource that is named in a way that is not common to your native language. When users search for this resource they may have some difficulty. In Active Directory there is now several phonetic attributes to help your users out.

ms-DS-Phonetic-First-Name
Contains the phonetic given name or first name of the person.

ms-DS-Phonetic-Last-Name
Contains the phonetic last name of the person.

ms-DS-Phonetic-Department
Contains the phonetic department name where the person works.

ms-DS-Phonetic-Company-Name
Contains the phonetic company name where the person works.

ms-DS-Phonetic-Display-Name
The phonetic display name of an object. In the absence of a phonetic display name the existing display name is used.

To test this I manually populated the ms-DS-Phonetic-First-Name attribute with Bbrraadd for the user named Brad. In Active Directory Users and computers, I did a search for the name Bbrr. It returned the correct users.

I tested this in PowerShell with the following command.

Get-ADUser –filter ’Name –like “Brad”’

I received several user objects with the first name of brad. I then tried the phonetic name.

Get-ADUser –filter ’Name –like “Bbrr*”’

I received nothing. I then changed the attribute for the search.

Get-ADUser –filter ’msDs-PhoneticFirstName –like “Bbrr*”’

I then received only the Brad account with the Phonetic name. With PowerShell, you must still specify the exact property you are looking for when search for users when you use the Phonetic attributes.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all. Take a look at the drive mapping below. The red triangle is what threw us off. It is not an error. It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle. This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the

Jason Yoder, MCT

Search This Blog