Solved

New-MailboxExportRequest cmdlet not available on 2010

Posted on 2014-02-20
5
1,728 Views
Last Modified: 2014-03-29
I have an exchange 2010 server on SBS 2011 all service packs and hotfixes for both the OS and exchange have been installed.
- I am opening Powershell as administrator
- I have successfully run New-ManagementRoleAssignment for the admin account.
- While I'm not that far along, I have created a share and added exchange trusted user account to the share with full rights.

Cmdlet is not available.

I found one thread that says to add-pssnapin Microsoft* but that doesn't load (assembly is built by a runtime newer...)

Any suggestions to get this cmdlet recognized?
0
Comment
Question by:davebird
  • 3
  • 2
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39875198
" Powershell as administrator"

That is your mistake.

Run Exchange Management Shell as Administrator. It is in the Exchange group on the Start Menu. Powershell does not mean EMS.

Simon.
0
 

Author Comment

by:davebird
ID: 39875208
Sorry, syntax error.  Running exchange management shell.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39875262
What command did you run to grant yourself permissions to do the new-mailboxexportrequest?

Are you sure that you are on SP3 for Exchange 2010? It doesn't install via Windows Update.

Simon.
0
 

Accepted Solution

by:
davebird earned 0 total points
ID: 39875437
Fair questions.  
Did windows update to get latest hotfixes and netframeworks etc.
Downloaded Exchange2010-SP3-x64.exe and installed
After reboot, Windows downloaded an exchange rollup 4 and installed.
From:
- Start, all programs, Microsoft Exchange Server 2010, and then Exchange Management Shell
- right click on the exchange management shell and run as administrator
- Once the PS prompt shows, the title bar shows Machine: <machine name.domain>
In the EMC, Get-ExchangeServer reports version 14.3 (Build 123.4)

------------------
That being said, while I was looking for the get-exchangeServer cmdlet, I found a thread that had a user load Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 because he was using PS (as you said in your first response) rather than EMC.  
I loaded it in the EMC.  
Command is available.  Export worked.  I'm a happy camper.
Pride forces me to share, while I hear laughing and "yea right", I really am using the EMC shell. ha.  

Thank you for your help.  Would not have run across this solution without running through to verify your questions.  If you'll post the add-pssnapin line as a response, I'll accept it as the solution and close this out.
thanx
0
 

Author Closing Comment

by:davebird
ID: 39963503
Self explanatory
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A quick Powershell script I wrote to find old program installations and check versions of a specific file across the network.
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

735 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question