ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Exchange Shell command not working

    IT Discussion
    exchange 2016 server 2012 psts
    8
    18
    1.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @Kelly
      last edited by

      @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!

      CloudKnightC 1 Reply Last reply Reply Quote 2
      • CloudKnightC
        CloudKnight @scottalanmiller
        last edited by

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

        Reid CooperR 1 Reply Last reply Reply Quote 1
        • WLS-ITGuyW
          WLS-ITGuy @travisdh1
          last edited by

          @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"

          CloudKnightC 1 Reply Last reply Reply Quote 0
          • CloudKnightC
            CloudKnight
            last edited by

            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-ITGuyW 1 Reply Last reply Reply Quote 0
            • WLS-ITGuyW
              WLS-ITGuy @CloudKnight
              last edited by

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

              CloudKnightC 1 Reply Last reply Reply Quote 1
              • CloudKnightC
                CloudKnight @WLS-ITGuy
                last edited by

                @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!

                1 Reply Last reply Reply Quote 0
                • CloudKnightC
                  CloudKnight @WLS-ITGuy
                  last edited by

                  @wls-itguy this the command I believe:

                  Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
                  
                  1 Reply Last reply Reply Quote 1
                  • Reid CooperR
                    Reid Cooper @CloudKnight
                    last edited by

                    @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?

                    1 Reply Last reply Reply Quote 1
                    • Reid CooperR
                      Reid Cooper
                      last edited by

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

                      PowerShell bash session?

                      CloudKnightC travisdh1T 2 Replies Last reply Reply Quote 3
                      • CloudKnightC
                        CloudKnight @Reid Cooper
                        last edited by

                        @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 🙂

                        1 Reply Last reply Reply Quote 1
                        • travisdh1T
                          travisdh1 @Reid Cooper
                          last edited by

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

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

                          PowerShell bash session?

                          Puny indeed.

                          1 Reply Last reply Reply Quote 0
                          • brianlittlejohnB
                            brianlittlejohn
                            last edited by brianlittlejohn

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

                            dbeatoD 1 Reply Last reply Reply Quote 1
                            • dbeatoD
                              dbeato @brianlittlejohn
                              last edited by

                              @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"

                              1 Reply Last reply Reply Quote 1
                              • 1 / 1
                              • First post
                                Last post