Link to home
Start Free TrialLog in
Avatar of Jorge Ocampo
Jorge OcampoFlag for United States of America

asked on

AD Bulk set User to Exchange Powershell 2007

Hi i am having problems running this script on powershell version

Name                           Value
----                           -----
CLRVersion                     2.0.50727.5485
BuildVersion                   6.1.7601.17514
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

Import-csv C:\Temp\input.csv | % {Set-ADUser $_.User -Office $_.Office -StreetAddress $_.StreetAddress -City $_.City -state $_.state -postalcode $_.postalcode}

i had no problem running on my machine but when i do it on the server no error it just doesnt write the values i would like to do the change in exchange powershell 2007 instead.
Avatar of Muhammad Mulla
Muhammad Mulla
Flag of United Kingdom of Great Britain and Northern Ireland image

Are you doing this with the AD modules imported into Powershell? Try:

Import-Module ActiveDirectory

Open in new window

Avatar of Todd Nelson
What type of server are you running the command from?  If the server does not have RSAT or ADDS features installed, the command won't do anything.

Remember to always precede your command with "Import-Module ActiveDirectory" in PowerShell.
Avatar of Jorge Ocampo

ASKER

import is on if i do a set-aduser to one user the command goes through
You command does not look correct. Assuming there is more than one name in the CSV file, how does this command loop for each name?

Replace "%" with "ForEach-Object" and it should run fine.

Import-csv C:\Temp\input.csv | ForEach-Object {Set-ADUser $_.User -Office $_.Office -StreetAddress $_.StreetAddress -City $_.City -state $_.state -postalcode $_.postalcode}

Open in new window

the following fields in csv user,office,streetaddress,city,state,postalcode
ill try replacing and see
no go would it possible to re-rewrite command for exchange powershell command instead could be because powershell 2.0 is not compatible
PowerShell 2.0 is not compatible?  Provide the error you are getting.

Does it run in PowerShell instead of the Exchange Management Shell?

I have no issues running the command I provided in PowerShell or the Exchange management shell.
ASKER CERTIFIED SOLUTION
Avatar of Guy Lidbetter
Guy Lidbetter
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial