• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Exchange Shell, all cmdlet not recognized

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2010] >> Migration >> Exchange Shell, all cmdlet not recognized Page: [1]
Login
Message << Older Topic   Newer Topic >>
Exchange Shell, all cmdlet not recognized - 2.May2010 10:41:23 AM   
andrew73

 

Posts: 5
Joined: 13.Aug.2008
Status: offline
Hi guys,
I've installed Exchange 2010 in a 2003 exchange environment, setup works fine but  when I try to open many menů in Console it shows me errors on cmdlet not recognized.
For example when I try to open "Configure Organization" for change domain controller it say me this error:

"get-organizationalUnit" not recognized as cmdlet...

Then I have opened EX Shell and many command does not recognized.

But if I run windows PowerShell, I can run any get- command fine  (also get-organizationalUnit), only message that I recieved from powershell just started is:

Microsoft.Exchange.Management.PowerShell.Setup, C:\Program Files\Microsoft\Exchange Server\V14\bin\Exchange.format.ps1x
ml: file ignored because present in "Microsoft.Exchange.Management.PowerShell.E2010".
In riga:24 car:34  +    Import-Module <<<<  $_.Name -ErrorAction SilentlyContinue   + CategoryInfo          : InvalidOperation: (:) [Import-Module], RuntimeException  + FullyQualifiedErrorId : FormatXmlUpateException,Microsoft.PowerShell.Commands.ImportModuleCommand

Seems that Exchange Management Shell open wrong file format instead powershell.

thanks for any support
Andrea
Post #: 1
RE: Exchange Shell, all cmdlet not recognized - 5.May2010 10:10:34 AM   
clementrosario

 

Posts: 126
Joined: 13.May2007
Status: offline
After migration we have to add the user to the RoleGroup.
add-rolegroupmember "Oraganization Management" -member "contoso\administrator"

Similarly add other rolegroup like Server Management, & Recipient Management

Enable remote powershell to the user account.

Set-user -identity "contoso\administrator" -remotepowershellenabled: $true

(in reply to andrew73)
Post #: 2
RE: Exchange Shell, all cmdlet not recognized - 5.May2010 3:42:34 PM   
andrew73

 

Posts: 5
Joined: 13.Aug.2008
Status: offline
Thanks for your answer.
I have found the problem, seems that windows 2008 register last credentials used from others tool as Outlook and use it for Exchange (!)
I have to open control panel, account and remove last credentials used. Is very strange but I don't any idea for this behaviour

(in reply to clementrosario)
Post #: 3
RE: Exchange Shell, all cmdlet not recognized - 6.May2010 1:57:10 PM   
clementrosario

 

Posts: 126
Joined: 13.May2007
Status: offline
Replication take a time frame of 15 days in an Exchange 2003 existing environment.
So we have to change the outlook profile pointing to the new server.

(in reply to andrew73)
Post #: 4
RE: Exchange Shell, all cmdlet not recognized - 9.Jun.2017 7:20:40 AM   
bloggeranjalitomar

 

Posts: 52
Joined: 22.Sep.2016
Status: offline
I agree with clementrosario's suggestion to check the permission.

Before you run the cmdlet, you need to have these permissions "Compliance Management", "Organization Management" and "Records Management".

You can use get-rolegroupmember cmdlet to check if you have these permission.

Get-RoleGroupMember

Visit : http://exchangeserver.tumblr.com/

(in reply to clementrosario)
Post #: 5
RE: Exchange Shell, all cmdlet not recognized - 5.Aug.2017 7:58:30 AM   
armias1

 

Posts: 35
Joined: 18.Aug.2015
Status: offline
The software easily recovers corrupted edb database and create the PST file.

Important features of the software

Restores damaged EDB files
Extracts EDB files from BKF files directly
Recovers mailboxes, public folders, and archive mailboxes from EDB files
Retrieves deleted items from mailboxes
Extracts attachments from emails
Saves retrieved data in Outlook PST files, production Exchange, and Office 365
Migrates data between Exchange/Office 365 and Exchange/Office 365
Performs need-based recovery/migration of mailboxes, folders, and item
Provides search option to find specific items quickly and easily
Offers preview of both the source data and the destination data on the same window
Provides instant copy-paste and drag-drop facility to move items from the source to the destination
Generates Operation Logs to provide the details of the performed tasks
Supports all versions of Exchange Server, MS Outlook, and Windows OS
Read more and free downlaod click here : https://exchangeserverrepair.blogspot.com

(in reply to bloggeranjalitomar)
Post #: 6

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2010] >> Migration >> Exchange Shell, all cmdlet not recognized Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter