Skip to main content

Using Properties with Spaces in the Names

By

This morning my Windows Server 2012 R2 class helped out another IT Pro out on the internet who needed to make some modifications to his Active Directory user accounts based off of information in a CSV file. One of the problems that he had was that the column header in the CSV included a space in the name.  We have three ways to deal with this.

1. Change the column header.  Yes, this would be a manual task every time you receive a new copy of the CSV for processing.  No fun there.  Actually avoiding having objects with spaces in their property names would be better, but we do not always have control over this.

2. Change the property name when the file is read.

1

2

3

4

5

6

7

8

9

ForEach ($User in (Import-CSV -Path E:\PS\Users2.CSV |

    Select-Object -Property *,

    @{N="EM";E={"$($_.{Employee Number})"}))

{

    $Address = $User.EmailAddress

    Get-ADUser -Filter 'EmailAddress -eq $Address' -Properties EmailAddress, EmployeeID |

    Set-ADUser -EmployeeID $User.EM

 

}  

Here the Import-CSV command is piped to Select-Object where we convert the object property Employee Number to EM  Notice the extra curly braces required to get this to work.  On line 7, we use our custom property.

3. Use the property with the space in the name directly in the code.

1

2

3

4

5

6

7

ForEach ($User in (Import-CSV -Path E:\PS\Users2.CSV))

{

    $Address = $User.EmailAddress

    Get-ADUser -Filter 'EmailAddress -eq $Address' -Properties EmailAddress, EmployeeID |

    Set-ADUser -EmployeeID "$($User.{Employee Number})"

 

}

You can see on line 5 that we are using the property with the space in the name.  To get this to work, the actual property name in encased inside of curly braces.

For those of you who have taken my PowerShell classes, you already know my position on spaces when used in variable names.  Same thing applies to spaces in a property name.  Avoid them or be ready to write some extra code.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more