Need help with an PowerShell command to extract user attributes

Hello, what I need to do is get a CSV file with two columns - the first with a list of all users in AD, and the other column with the value of the AD attribute 'userSharedFolder' for that user.

I'm a PowerShell learner.  Here's what I have so far...

Get-ADUser –Filter * -prop cn,userSharedFolder | select cn,userSharedFolder  > \\server\share\IT\Scripts\AD\Ldrive.csv

Now, all the info is there in the resulting CSV, but there are a few formatting issues.  Firstly, the output is not on separate columns in Excel - it's all on the same column, just with loads of white space between the username and the userSharedFolder.  How do I get them onto separate columns, with no white space?  Secondly, I have some usernames that have a leading zero, but Excel sees it fit to remove this digit.  Can you stop this from happening at the script level, or would this be an Excel thing?

Any other tips to improve the above command would be welcomed.

Thanks.
meirionwylltSenior Desktop EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

footechCommented:
Instead of redirecting to a file with > \\server\share\IT\Scripts\AD\Ldrive.csv (which is equivalent to piping to Out-File), pipe to Export-CSV instead.
Get-ADUser –Filter * -prop cn,userSharedFolder | select cn,userSharedFolder  | Export-CSV \\server\share\IT\Scripts\AD\Ldrive.csv -notype

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
meirionwylltSenior Desktop EngineerAuthor Commented:
Hi, thanks for that.  What I have now are lines of CSV with one cell on each row, in the following format...

cn,"userSharedFolder"

I'm guessing the existence of the comma is a Delimiter issue isn't it.  Am I able to modify the command to make Excel treat this as two columns?  I realise I can do an Insert Object from within Excel but I was just wondering if there is a way to do this from the command.

Also, is there a way of removing the quotes around the userSharedFolder entries?

Thanks.
AntzsInfrastructure ServicesCommented:
I have been using the attached script and you could extract any AD Attribute info you need.  Give it a try.

Just need to key in the $path, $SearchBase and $ADServer

Credit to the author who is listed in the powershell script.
Export_AD_Users_to_CSV.v1.0.txt
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Get the Guide
footechCommented:
Export-CSV puts quotes around every field.  This ensures that even if the field includes the same character which is used as the delimiter the field isn't broken up.  When you open the file in Excel you won't see the quotes (when it's parsed properly).
Add the following parameter to Export-CSV.
-Encoding ASCII

Open in new window

Excel doesn't parse the .CSV correctly when the file has certain encodings.  ASCII/ANSI, UTF8 and others work fine.  Unicode and some others don't.  I believe I posted a long time ago the results from testing all encodings, but I don't have them in front of me.

I'm not sure why your instance appears to be generating a file with the encoding that Excel doesn't handle well.  I can't remember if there was a change in different PS versions in this regard.  Or maybe there a difference due to regional settings in Windows.
meirionwylltSenior Desktop EngineerAuthor Commented:
Adding the -Encoding ACSII parameter and then using Excel's 'Text to Columns' button (rather than doing an import) has given me what I need, because it gets rid of the quotes and when I select Text rather than General it keeps the leading zero as well.  Thanks.

Anthony - I tried the script you posted but it kept throwing the error...

Select-Object : A parameter cannot be found that matches parameter name 'Path'.
At \\server\share\IT\scripts\AD\Export_AD_Users_to_CSV.v1.0.ps1:95 char:12
+ Export-Csv -Path "$csvfile" -NoTypeInformation
+            ~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Select-Object], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.SelectObjectCommand

As a test I changed line 30 to...

$csvfile = "C:\TG\AllADUsers_$logDate.csv"

just to get rid of any possibility of problems with UNC paths and/or spaces in the path.  But it still gave the same error.

Although I've now been able to achieve what I wanted in my original post, I can see the benefit of using this script in the future so it would be nice to get this working.  Do you know what might be the problem?  I have full permissions to both the UNC path and the local folder.

Thanks.
AntzsInfrastructure ServicesCommented:
Just change those in the red box.  It should work.

Sript
meirionwylltSenior Desktop EngineerAuthor Commented:
Okay I know what's happening here.  I was doing the above three things correctly, but the problem was when I was editing the Select-Object section.  I had to fiddle with this section to add the 'userSharedFolder' label.  In order to keep the resulting spreadsheet clean I hashed out everything I didn't want.  Among the lines that I didn't want was the final 'lastlogondate' line, which has a pipe at the end of it, which is crucial to the script being able to run.

This was my mistake of course, but this script should be slicker.  The '@Label...' entries should all be on their own individual lines, which would allow them to be switched off and on as required.  The same is true for the $_.GivenName entry - you also can't hash this out without breaking the whole script.

But until I figure out how to do that I'll just delete the rows from Excel.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.