Exchange Shell command not working

Kelly

@wls-itguy said in Exchange Shell command not working:

@kelly I know crazier things have been needed, but why would I need to install a module on an Exchange 2016 machine when I am running the cmd in Exchange Powershell?

Powershell does what it can to run lean, and that means letting the user determine which modules to load on start.

scottalanmiller

@kelly said in Exchange Shell command not working:

@wls-itguy said in Exchange Shell command not working:

@kelly I know crazier things have been needed, but why would I need to install a module on an Exchange 2016 machine when I am running the cmd in Exchange Powershell?

Powershell does what it can to run lean, and that means letting the user determine which modules to load on start.

Which is hard to believe given how insanely slow and bloated it is!

StuartJordan

@scottalanmiller - it-is-the-insanely-long-commands-that-get-me
Even though they do have tab completion.

WLS-ITGuy

@travisdh1 said in Exchange Shell command not working:

@wls-itguy said in Exchange Shell command not working:

@kelly I know crazier things have been needed, but why would I need to install a module on an Exchange 2016 machine when I am running the cmd in Exchange Powershell?

PowerShell still needs the Exchange2016 module loaded. I know it doesn't make sense being that you're already in "Exchange Poershell".

I seem to slipping on my google-fu as I cannot find the cmdlet to run in "exchange mode"

StuartJordan

I must be the only one that don't like the powershell CLI, I'd rather stick to bash any day of the week..

WLS-ITGuy

@stuartjordan I call it Super DOS. And I F'n HATE IT!

StuartJordan

@wls-itguy said in Exchange Shell command not working:

@stuartjordan I call it Super DOS. And I F'n HATE IT!

haha, I like that....Very True!

StuartJordan

@wls-itguy this the command I believe:

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;

Reid Cooper

@stuartjordan said in Exchange Shell command not working:

@scottalanmiller - it-is-the-insanely-long-commands-that-get-me
Even though they do have tab completion.

And the weird format. Why did they have to make it all so weird?

Reid Cooper

Did this become a... wait for it...

PowerShell bash session?

StuartJordan

@reid-cooper said in Exchange Shell command not working:

Did this become a... wait for it...

PowerShell bash session?

@reid-cooper said in Exchange Shell command not working:

Did this become a... wait for it...

PowerShell bash session?

lol, that has to be the pun of the day

travisdh1

@reid-cooper said in Exchange Shell command not working:

Did this become a... wait for it...

PowerShell bash session?

Puny indeed.

brianlittlejohn

You also need to have export/import permissions granted to your account. They are not granted to anyone by default.

dbeato

@brianlittlejohn said in Exchange Shell command not working:

You also need to have export/import permissions granted to your account. They are not granted to anyone by default.

This is what you need.

First assign your user the Mailbox Export Role
New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "<user name or alias>"

Then make sure the Exchange Subsystem has access to that shared folder and then run your export:
MailboxExportRequest -Mailbox username -FilePath "\\server\PST FOlder\username.pst"