<div>
if you could upload csv and script, we can find out the issue
</div>

<div>
There is no script, it runs in Active Directory Module for Windows Powershell using the below which as I say imports the user but no telephone number and doesn't place it in the ou specified in the CSV. 
 
Import-Csv .\test.csv | New-ADUser -Enabled $True -AccountPassword (ConvertTo-SecureString M5aeq -AsPlainText -force) 
 
And the contents of the csv are: 
 
givenName,name,telephonenumber,ou 
test company,test company,01702 123456,OU=SarkContacts,DC=domain,DC=net
</div>

<div>
Add two columns to the csv, SamAccountName (limited to 20 characters, should not contains spaces, unique in the domain) and UserPrincipalName. 
Then use something like this (password could come individually per user from the csv as well): 

<pre><code class="code-10 nolinks" id="code-20-42759460-1">$password = 'M5aeq'
Import-Csv .\test.csv | ForEach-Object {
	$ADUserArgs = @{
		SamAccountName =		$_.SamAccountName
		UserPrincipalName =		$_.UserPrincipalName
		AccountPassword =		ConvertTo-SecureString -AsPlainText $Password -Force
		Name =					$_.Name
		GivenName =				$_.GivenName
		DisplayName =			&quot;$($_.Name), $($_.GivenName)&quot;
		OfficePhone =			$_.telephonenumber
		ChangePasswordAtLogon = $true
		Path =					$_.OU
		Enabled =				$true
	}
	&quot;User '$($_.SamAccountName)'&quot; | Write-Host
	New-ADUser @ADUserArgs
}
</code></pre>
</div>

IT Professional

Albert Widjaja

<div>
The cmdlet is incomplete 
csv file should contains SamAccountName, given name, last name, OU location and telephone number etc with headers 
Example: 
csv file should contains all below fields as headers and with values 
 

<pre><code class="code-10 nolinks" id="code-20-42759462-1">$Users = Import-Csv C:\new\users.csv

#Processing each user
Foreach ($User in $Users) {
 try {
 $saMAccountName = $user.SamAccountName

 $ADuser = Get-ADUser -LDAPFilter &quot;(sAMAccountName=$saMAccountName)&quot;
 
 if ($ADUser -eq $null) {
 New-ADUser -SamAccountName $saMAccountName -UserPrincipalName $($user.SamAccountName + &quot;@domain.com&quot;) -Name (&quot;$($user.FirstName) $($User.LastName)&quot;) -DisplayName (&quot;$($user.FirstName) $($User.LastName)&quot;) -GivenName $user.FirstName `
 -Surname $user.LastName -Enabled $true -PasswordNeverExpires $false -AccountPassword (ConvertTo-SecureString &quot;pass@123&quot; -AsPlainText -Force) -ChangePasswordAtLogon $true -Path $user.TargetOU -Manager -MobilePhone $User.phone
 }
 }
catch {$error[0].ToString() }

}
</code></pre>
</div>

<div>
AFAIK New-ADUser does not take over more than the user name or SamAccountName from pipeline, that is why everything else is ignored, and you need to run something like oBdA showed - setting properties individually in a loop.
</div>

<div>
The original issue is, the CSV is not formatted correctly. 
First, it uses comma as delimiter. Also, OU filed uses comma to separate its fields. You should change the csv delimiter and use the -delimiter parameter of import-csv. 
New-AdUser does not have an telephonenumber parameter. Change the name to OfficePhone an it should load the value as the property is passed by name through the pipe 
From: <a href="https://docs.microsoft.com/en-us/powershell/module/addsadministration/new-aduser?view=win10-ps" rel="ugc nofollow">https://docs.microsoft.com/en-us/powershell/module/addsadministration/new-aduser?view=win10-ps</a>
<blockquote></blockquote>
<blockquote>
 
[...] 
Method 3: Use the Import-Csv cmdlet with the New-ADUser cmdlet to create multiple Active Directory user objects. To do this, use the Import-Csv cmdlet to create the custom objects from a comma-separated value (CSV) file that contains a list of object properties. Then pass these objects through the pipeline to the New-ADUser cmdlet to create the user objects. 
[...] 
-OfficePhone 
Specifies the user's office telephone number. This parameter sets the OfficePhone property of a user object. The LDAP display name (ldapDisplayName) of this property is telephoneNumber. 

</blockquote>
</div>

"Batchelor", Developer and EE Topic Advisor

Qlemo

<div>
Correct, the comma delimiter is another issue of many. 
I've looked up the cmdlet description now, and it accepts objects from pipeline. The properties need to be named exactly like the parameter names you would use for New-ADUser, so either add columns and change headings accordingly, or use a loop as oBdA did to map attributes between both.
</div>

<div>
Apologies everyone as this is all new to me I'm not quite understanding. 
 
As i said at the end of my first message I really wanted them as contacts but didn't think it could be done but I've been playing and managed to get them in as contacts but don't understand this -delimiter to get the other values imported as only the first entry in the CSV is uploaded. 
 
current import string imports them as contacts in the container I want: PS C:\scripts&gt; Import-Csv .\test.csv | New-ADObject -Type contact -Path &quot;ou=sarkcontacts,dc=domain,dc=net&quot; 
 
CSV file: 
samaccountname,name,homephone 
test company,test company,01702 123456 
mark,mark,07889123456
</div>

<div>
Import-csv uses comma as delimiter between fields. 
your csv file is using comma to separate fields BUT ALSO OrganizationalUnit field uses comma to separate path fields: 
 

<pre><code class="code-1 nolinks" id="code-20-42759586-1">givenName,name,telephonenumber,ou
test company,test company,01702 123456,OU=SarkContacts,DC=domain,DC=net
</code></pre>
 
In your last post you pasted a different example: noo OU field therefore no comma inside a field therefore no issue. 
 
You can use a different separator and specify it via -delimiter parameter to import-csv 
 

<pre><code class="code-1 nolinks" id="code-20-42759586-2">givenName|name|OfficePhone|organizationalunit
test company|test company|01702 123456|OU=SarkContacts,DC=domain,DC=net
</code></pre>
 

<pre><code class="code-1 nolinks" id="code-20-42759586-3">import-csv .\test.csv -delimiter &quot;|&quot; | new-aduser blah
</code></pre>
</div>

<div>
If I add the -delimiter in the string I get this error: 
 
Import-Csv : A positional parameter cannot be found that accepts argument '.\te 
st.csv'. 
At line:1 char:11 
+ Import-Csv &lt;&lt;&lt;&lt;&nbsp; .\test.csv -delimiter &quot;|&quot; New-ADObject -Type contact 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: InvalidArgument: (:) [Import-Csv], ParameterBind 
&nbsp; &nbsp;ingException 
&nbsp; &nbsp; + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell 
&nbsp; &nbsp;.Commands.ImportCsvCommand
</div>

<div>
The other way is keep the commas, and enclose (at least) the OU in double quotes: 

<pre><code class="code-1 nolinks" id="code-20-42759602-1">givenName,name,telephonenumber,ou
test company,test company,01702 123456,&quot;OU=SarkContacts,DC=domain,DC=net&quot;
</code></pre>
but it is better to use a delimiter you are certain does not appear in your data.
</div>

<div>
You'Ve missed a pipe operator. It is 

<pre><code class="code-1 nolinks" id="code-20-42759604-1">Import-Csv .\test.csv -delimiter &quot;|&quot; | New-ADObject -Type contact
</code></pre>
</div>

<div>
PS C:\scripts&gt; Import-Csv .\test.csv -delimiter | New-ADObject -Type contact 
Import-Csv : Missing an argument for parameter 'Delimiter'. Specify a parameter 
&nbsp;of type 'System.Char' and try again. 
At line:1 char:33 
+ Import-Csv .\test.csv -delimiter &lt;&lt;&lt;&lt;&nbsp; | New-ADObject -Type contact 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: InvalidArgument: (:) [Import-Csv], ParameterBind 
&nbsp; &nbsp;ingException 
&nbsp; &nbsp; + FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.Im 
&nbsp; &nbsp;portCsvCommand
</div>

<div>
You still didn't type what we posted. Please check again.
</div>

<div>
For contacts, you don't need (can't use) the SamAccountName. 
It works the same way as I used above: you use a loop and you set the properties you want. 
You can happily use a regular comma separated csv, provided that fields which include the delimiter are enclosed in double quotes. In fact, all fields should be enclosed in double quotes (Excel does that when you save as csv, so does PowerShell's Export-Csv). 
To find the attributes/properties you set, enable &quot;Advanced View&quot; in the ADUC console, then open the properties of a contact. You'll find a tab &quot;Attribute Editor&quot;, where you can identify the properties you can set. 
The additional properties (the ones that New-ADObject doesn't support directly in the command line) need to be added to the $otherAttributes variable. 

<pre><code class="code-1 nolinks" id="code-20-42759618-1">&quot;givenName&quot;,&quot;name&quot;,&quot;homephone&quot;,&quot;ou&quot;
&quot;test company&quot;,&quot;test company&quot;,&quot;01702 123456&quot;,&quot;OU=SarkContacts,DC=domain,DC=net&quot;
&quot;marky&quot;,&quot;mark&quot;,&quot;07889123456&quot;,&quot;OU=SarkContacts,DC=domain,DC=net&quot;
</code></pre>
<pre><code class="code-10 nolinks" id="code-20-42759618-2">Import-Csv .\test.csv | ForEach-Object {
	$contactArgs = @{
		Name =			$_.Name
		DisplayName =	&quot;$($_.Name), $($_.GivenName)&quot;
		Path =			$_.OU
	}
	$otherAttributes = @{
		GivenName =		$_.GivenName
		HomePhone =		$_.homephone
	}
	&quot;User '$($_.Name)'&quot; | Write-Host
	New-ADObject -Type Contact @contactArgs -OtherAttributes $otherAttributes
}
</code></pre>
</div>

<div>
Qlemo 
 
 
PS C:\scripts&gt; Import-Csv .\test.csv -delimiter &quot;|&quot; New-ADObject -Type contact 
Import-Csv : A positional parameter cannot be found that accepts argument 'New- 
ADObject'. 
At line:1 char:11 
+ Import-Csv &lt;&lt;&lt;&lt;&nbsp; .\test.csv -delimiter &quot;|&quot; New-ADObject -Type contact 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: InvalidArgument: (:) [Import-Csv], ParameterBind 
&nbsp; &nbsp;ingException 
&nbsp; &nbsp; + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell 
&nbsp; &nbsp;.Commands.ImportCsvCommand 
 
PS C:\scripts&gt;
</div>

<div>
oBdA 
 
When I save in Excel as a csv I don't get it in double quotes....
</div>

<div>
Excel will do that for fields that contain the delimiter (or line feeds). 
Export-Csv does it for every field.
</div>

<div>
Andrew you keep typpng it wrong. Can't ypu paste it? 
 
 
-delimiter &quot;|&quot; | new-aduser
</div>

<div>
PS C:\scripts&gt; Import-Csv .\test.csv -delimiter &quot;|&quot; | New-ADObject -Type contact 
&nbsp;-Path &quot;ou=sarkcontacts,dc=domain,dc=net&quot; 
New-ADObject : The input object cannot be bound to any parameters for the comma 
nd either because the command does not take pipeline input or the input and its 
&nbsp;properties do not match any of the parameters that take pipeline input. 
At line:1 char:52 
+ Import-Csv .\test.csv -delimiter &quot;|&quot; | New-ADObject &lt;&lt;&lt;&lt;&nbsp; -Type contact -Path 
&nbsp;&quot;ou=sarkcontacts,dc=domain,dc=net&quot; 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: InvalidArgument: (@{givenName,&quot;na...&quot;01702 12345 
&nbsp; &nbsp;6&quot;}:PSObject) [New-ADObject], ParameterBindingException 
&nbsp; &nbsp; + FullyQualifiedErrorId : InputObjectNotBound,Microsoft.ActiveDirectory.Ma 
&nbsp; &nbsp;nagement.Commands.NewADObject 
 
New-ADObject : The input object cannot be bound to any parameters for the comma 
nd either because the command does not take pipeline input or the input and its 
&nbsp;properties do not match any of the parameters that take pipeline input. 
At line:1 char:52 
+ Import-Csv .\test.csv -delimiter &quot;|&quot; | New-ADObject &lt;&lt;&lt;&lt;&nbsp; -Type contact -Path 
&nbsp;&quot;ou=sarkcontacts,dc=dwdsl,dc=net&quot; 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: InvalidArgument: (@{givenName,&quot;na...,&quot;0788912345 
&nbsp; &nbsp;6&quot;}:PSObject) [New-ADObject], ParameterBindingException 
&nbsp; &nbsp; + FullyQualifiedErrorId : InputObjectNotBound,Microsoft.ActiveDirectory.Ma 
&nbsp; &nbsp;nagement.Commands.NewADObject
</div>

<div>
You can't create a contact with the properties you want by piping a csv to New-ADObject. 
There's no way around a loop, as described in <a href="https:#a42759618" rel="ugc">https:#a42759618</a>
</div>

<div>
I give up as I don't understand
</div>

<div>
There's a sample csv and a script in <a href="https:#a42759618" rel="ugc">https:#a42759618</a> 
What is it you don't understand?
</div>

<div>
you can hire somebody to work for you and make you understand script and user creation
</div>

<div>
oBDA 
 
On the assumption I simply copy and paste the script it doesn't work. 
 
PS C:\scripts&gt; Import-Csv .\test.csv | ForEach-Object { 
&gt;&gt;&nbsp; &nbsp; &nbsp;$contactArgs = @{ 
&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Name =$_.Name 
&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;DisplayName =&quot;$($_.Name), $($_.GivenName)&quot; 
&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Path =$_.OU 
&gt;&gt;&nbsp; &nbsp; &nbsp;} 
&gt;&gt;&nbsp; &nbsp; &nbsp;$otherAttributes = @{ 
&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;GivenName =$_.GivenName 
&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;HomePhone =$_.homephone 
&gt;&gt;&nbsp; &nbsp; &nbsp;} 
&gt;&gt;&nbsp; &nbsp; &nbsp;&quot;User '$($_.Name)'&quot; | Write-Host 
&gt;&gt;&nbsp; &nbsp; &nbsp;New-ADObject -Type Contact @contactArgs -OtherAttributes $otherAttributes 
 
&gt;&gt;&nbsp;} 
&gt;&gt; 
User 'A C Solutions' 
New-ADObject : Cannot bind parameter 'OtherAttributes' to the target. Exception 
&nbsp;setting &quot;OtherAttributes&quot;: &quot;Object reference not set to an instance of an obje 
ct.&quot; 
At line:12 char:61 
+ &nbsp; &nbsp; New-ADObject -Type Contact @contactArgs -OtherAttributes &lt;&lt;&lt;&lt;&nbsp; $otherAttr 
ibutes 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: WriteError: (:) [New-ADObject], ParameterBinding 
&nbsp; &nbsp;Exception 
&nbsp; &nbsp; + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.ActiveDirectory 
&nbsp; &nbsp;.Management.Commands.NewADObject 
 
User 'mark' 
New-ADObject : Cannot bind parameter 'OtherAttributes' to the target. Exception 
&nbsp;setting &quot;OtherAttributes&quot;: &quot;Object reference not set to an instance of an obje 
ct.&quot; 
At line:12 char:61 
+ &nbsp; &nbsp; New-ADObject -Type Contact @contactArgs -OtherAttributes &lt;&lt;&lt;&lt;&nbsp; $otherAttr 
ibutes 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: WriteError: (:) [New-ADObject], ParameterBinding 
&nbsp; &nbsp;Exception 
&nbsp; &nbsp; + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.ActiveDirectory 
&nbsp; &nbsp;.Management.Commands.NewADObject 
 
PS C:\scripts&gt;
</div>

<div>
You save the csv as test.csv, and the script as Import-Contacts.ps1 or whatever.ps1 in the same folder. 
You open a PS console, &quot;cd&quot; into the folder where you saved the files, and run .\Import-Contacts.ps1 
I just copied both files back from here, adjusted only the target OU, and it worked just as it should. 
In $contactArgs, you can specify one or more of the following properties/arguments on the left-hand side of the &quot;=&quot; sign: 
Description, DisplayName, Name, Path 
On the right-hand side of the &quot;=&quot;, you need to specify the respective column name of the csv, or whatever you want to set the property to (like DisplayName, which is built from the Name and GivenName columns). 
In $otherAttributes, you can specify other settable properties (see the description in <a href="https:#a42759618" rel="ugc">https:#a42759618</a>&nbsp;on how to find the names) on the left-hand side of the &quot;=&quot; sign. 
Right-hand side same as in $contactArgs
</div>

<div>
As Mahesh said I could pay someone to do this, so have posted on another site for someone to do this as clearly I'm still doing something wrong. 
 
 
PS C:\Users\Administrator&gt; cd C:\scripts 
PS C:\scripts&gt; .\Import.ps1 
File C:\scripts\Import.ps1 cannot be loaded because the execution of scripts is 
&nbsp;disabled on this system. Please see &quot;get-help about_signing&quot; for more details. 
 
PS C:\scripts&gt; Set-ExecutionPolicy RemoteSigned 
 
 
 
PS C:\scripts&gt; .\Import.ps1 
User 'A C Solutions' 
New-ADObject : Cannot bind parameter 'OtherAttributes' to the target. Exception 
&nbsp;setting &quot;OtherAttributes&quot;: &quot;Object reference not set to an instance of an obje 
ct.&quot; 
At C:\scripts\Import.ps1:12 char:58 
+ &nbsp; &nbsp; New-ADObject -Type Contact @contactArgs -OtherAttributes &lt;&lt;&lt;&lt;&nbsp; $otherAttr 
ibutes 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: WriteError: (:) [New-ADObject], ParameterBinding 
&nbsp; &nbsp;Exception 
&nbsp; &nbsp; + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.ActiveDirectory 
&nbsp; &nbsp;.Management.Commands.NewADObject 
 
User 'mark' 
New-ADObject : Cannot bind parameter 'OtherAttributes' to the target. Exception 
&nbsp;setting &quot;OtherAttributes&quot;: &quot;Object reference not set to an instance of an obje 
ct.&quot; 
At C:\scripts\Import.ps1:12 char:58 
+ &nbsp; &nbsp; New-ADObject -Type Contact @contactArgs -OtherAttributes &lt;&lt;&lt;&lt;&nbsp; $otherAttr 
ibutes 
&nbsp; &nbsp; + CategoryInfo &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: WriteError: (:) [New-ADObject], ParameterBinding 
&nbsp; &nbsp;Exception 
&nbsp; &nbsp; + FullyQualifiedErrorId : ParameterBindingFailed,Microsoft.ActiveDirectory 
&nbsp; &nbsp;.Management.Commands.NewADObject 
 
PS C:\scripts&gt;
</div>

<div>
Experts-exchange also offers paid help. 
<a href="https://www.experts-exchange.com/live/" rel="ugc">https://www.experts-exchange.com/live/</a>
</div>

<div>
<div class="content wysiwyg-content">
Importing users into AD 
 
In Active Directory Module for Windows Powershell I'm using Import-Csv .\test.csv | New-ADUser -Enabled $True -AccountPassword (ConvertTo-SecureString M5aeq -AsPlainText -force) which works to a point, I'm not getting the import of the telephonenumber and it's not placing in the Organizational Unit specified in the csv file. 
 
givenName,name,telephonenumber,ou 
test company,test company,01702 123456,OU=SarkContacts,DC=domain,DC=net 
 
I would of preferred to import them as Contacts but I don't thing that can be done with the above method. 
 
Regards 
Mark
</div>
</div>

Importing users into AD

In Active Directory Module for Windows Powershell I'm using Import-Csv .\test.csv | New-ADUser -Enabled $True -AccountPassword (ConvertTo-SecureString M5aeq -AsPlainText -force) which works to a point, I'm not getting the import of the telephonenumber and it's not placing in the Organizational Unit specified in the csv file.

givenName,name,telephonenumber,ou
test company,test company,01702 123456,OU=SarkContacts,DC=domain,DC=net

I would of preferred to import them as Contacts but I don't thing that can be done with the above method.

Regards
Mark

Import Users into AD with Active Directory Module for Windows Powershell

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.