{"id":76,"date":"2013-10-18T22:12:33","date_gmt":"2013-10-18T22:12:33","guid":{"rendered":"http:\/\/www.edrockwell.com\/blog\/?p=76"},"modified":"2026-07-02T16:57:33","modified_gmt":"2026-07-02T16:57:33","slug":"how-to-import-ad-users-from-csv-file","status":"publish","type":"post","link":"https:\/\/www.edrockwell.com\/blog\/how-to-import-ad-users-from-csv-file\/","title":{"rendered":"How To: Import AD Users from .csv file"},"content":{"rendered":"

I had a project that required me to make over 40 domain accounts. I decided that it was time to create all the domain accounts with a Powershell script. The script I came up with uses an import csv file with all the accounts and info I needed in it. Make sure you take the time to plan a naming convention for your AD accounts. In this case, they were a type of service account for many different environments. To keep it quick, I decided to not auto-gen the passwords so I simply put them in the csv file and removed them when I was done. Well, it took me a day or so to figure out my script to create ad accounts because I had problems…<\/p>\n

My troubleshooting was a bit flawed but I didn’t know it until the very end (After running for all the users). I was having problems with the script ending in error . This is a very generic error. I knew that my accounts had spaces in them for $GivenName $Surname and $Name. So, I went through the trouble making sure that my variable properties with spaces had “” around them. Yes, that’s a pair of double quotes. My Display name I wanted to use had GivenName and Surname in it with a space. So it looks like this: Displayname = ($User.”GivenName”+” “+$User.”Surname”). The quotes around “GivenName” allowed me to use two names in the GivenName column of the .csv file and the same for “Surname”. This way I can create an account that looks like: First Second Third Forth. In other words, my “GivenName” in my CSV was First Second so I had to put “” around it in the script so it would read it as one word. What I missed is after everything was put together, the fields were over 20 characters. Well, the limit on Windows 2008 Account “Names” is 20 characters. Until I ran my script and found that it didn’t create about 1\/2 of them, I started analyzing the .csv file to figure out why it didn’t work. I found out that the ones that didn’t get created are the ones that were over 20 characters. <\/p>\n

Here is the script. You will notice that I’ve got a comment in the script for the .csv file’s header fields. You can add to them or remove as needed. I think it’s easier to view the powershell references on Microsoft’s site. Here is the link to Set-ADUser cmdlet: http:\/\/technet.microsoft.com\/en-us\/library\/ee617215.aspx. For each property, you need it in the script and in the .csv file. If there are special characters or spaces. Remember to use the “” around it in the script. Also, make sure you are not exceeding the field length in AD for each property. The sAMAccountName (pre-Windows 2000 logon name) is limited to 20 characters for user objects. This is what got me a few times \ud83d\ude41<\/p>\n

Let me know if you need anything below explained! I’ll answer all comments on this the same day if I can.<\/p>\n

\r\n# REQUIRE DA ACCOUNT  \r\nif (! ($ENV:USERNAME).ToUpper().EndsWith(\"ADM\"))\r\n{\r\n\tthrow \"SCRIPT MUST BE RUN WITH ADMIN ACCOUNT\"\r\n}\r\n\r\n# IMPORTING AD MODULE\r\nif (! @(get-module -name ActiveDirectory).count) \r\n{\r\n\timport-module ActiveDirectory\r\n}\r\n\r\n# GETTING USERS FROM CSV FILE\r\n\r\n### NOTE: The Account Column CAN NOT be more than 20 characters or it will fail on them!\r\n\r\n$Users = Import-CSV C:\\CreateADUsers.csv \r\n# columns are: GivenName,Surname,Name,Account,Password,Department,Description\r\n\r\n\r\n# CREATING USERS\r\n# If you don't have two word attributes, you can remove some of the \"\" below after the $User.\r\nforeach($User in $Users)\r\n{\r\n\t$Params = @{\r\n\t\tSamAccountName = $User.Account\r\n\t\tName = $User.\"Name\"\r\n\t\tGivenName = $User.\"GivenName\"\r\n\t\tSurname = $User.\"Surname\"\r\n\t\tDisplayname = ($User.\"GivenName\"+\" \"+$User.\"Surname\")\r\n\t\tUserPrincipalName = ($User.Account+\"@domain.com\")\r\n\t\tDepartment = $User.\"Department\"\r\n\t\tDescription = $User.\"Description\"\r\n\t\tPath = \"OU=Your OU,DC=domain,DC=com\"\r\n\t\tPasswordNeverExpires = $true\r\n\t\tAccountPassword = (ConvertTo-SecureString $User.Password -AsPlainText -Force)\r\n\t\tEnabled = $true\r\n\t}\r\n\tnew-ADUser @Params\r\n}\r\n<\/pre>\n
I’m a seasoned Systems Administrator with experience starting in the early 90’s when 286 computers with 20 and 30 Mhz processors running Windows 3.1 which was the newest operating system. <\/p>\n
…and that’s the way Ed does it \ud83d\ude42   — Thanks Scott J. for that \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
I had a project that required me to make over 40 domain accounts. I decided that it was time to create all the domain accounts with a Powershell script. The script I came up with uses an import csv file with all the accounts and info I needed in it. Make sure you take the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[39,40,21],"class_list":["post-76","post","type-post","status-publish","format-standard","hentry","category-powershell","tag-add-aduser","tag-import-users-in-ad","tag-powershell-2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t