Importing .csv into Exchange DL using Powershell

I had this question after viewing Import .csv file into Exchange Distribution Group.
I've got 200 email addresses to put into a newly created DL. I've tried using the script in the above case (making appropriate changes) and I get the attached error. The name of the DL is Blackstone Consultants, the .csv file is BlackstoneGroup.csv and is saved on the hard drive in the temp folder. How can I adjust the script to get it to work?
Error.txt

Kelly Denise HortonConfiguration Management AnalystAsked: 2017-03-23

Who is Participating?

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

Experts Exchange Solution brought to you by

Enjoy your complimentary solution view.

Get every solution instantly with Premium. Start your 7-day free trial.

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.

LVL 6

Pavel NagaevLead email system administratorCommented: 2017-03-24

The term 'Add-DistributionGroupMember' is not recognized as the name of a cmdlet, function, script file, or operable pr
ogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

cmdlet Add-DistributionGroupMember from Exchange Server environment. You should run this script from EMC at Exchange Server or from ISE but at first you need to connect to Exchange server

if (Test-Path $env:ExchangeInstallPath\bin\RemoteExchange.ps1)
{
. $env:ExchangeInstallPath\bin\RemoteExchange.ps1
Connect-ExchangeServer -auto -AllowClobber
}

https://technet.microsoft.com/en-us/library/dd335083(v=exchg.160).aspx
https://www.codetwo.com/kb/how-to-connect-to-exchange-server-via-powershell/

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

Kelly Denise HortonConfiguration Management AnalystAuthor Commented: 2017-03-24

I was logged onto the exchange server and working in Powershell when I got the error.

LVL 71

Chris DentPowerShell DeveloperCommented: 2017-03-25

Ensure you run the Exchange management shell. Otherwise you'll have to import the Exchange tools manually and they're not in an auto-discoverable path. Running PowerShell on the Exchange server is not quite enough.