Typical Microsoft

Wanted to move mailboxes between two different Exchange server so I wanted to export them to PST

Powershell command is "export-Mailbox" and "import-Mailbox" respectively.

Export-Mailbox: Exchange 2010 Help

Didn't work .. was driving me mental ..

As of Exchange Servicepack 1 they changed the commands to

"New-MailboxExportRequest" and "New-MailboxImportRequest"

New-MailboxExportRequest: Exchange 2010 SP1 Help

Why the *$%£ do they change whole command sets between SP revisions ?!?

When I did my exams (662/663) last month they started to use SP1 questions - so you better study it WELL ...

Find more posts tagged with

Comments

bertieb

They do it on purpose to ensure you stay sharp

varelg

They seem to have "learned" few lessons from the Asterisk project. That was back in the days before Asterisk got forked...
Similar approach. You spend hours on end ironing config files on which the whole project depends and along will come an "upgrade" that is essentially just a syntax refurbishment that breaks everything you created. And the only difference between the current and the older version is syntax. No new functionality...

blargoe

That will be covered on the 70-662b TS: Microsoft Exchange Server 2010 (SP1), Configuring Exam

jibbajabba

The most annoying thing is that I created a lot of scripts to make my life easier, which simply don't work anymore *gutted*

Asif Dasl

Gomjaba wrote: »

The most annoying thing is that I created a lot of scripts to make my life easier, which simply don't work anymore *gutted*

Just use find and replace in notepad. Wouldn't take that long.

Jack2

Asif Dasl wrote: »

Just use find and replace in notepad. Wouldn't take that long.

Or use a utility like wingrep -http://www.wingrep.com/features.htm

To find and replace the changes in a whole directory of file... BAMM..

Asif Dasl

Jack2 wrote: »

Or use a utility like wingrep -http://www.wingrep.com/features.htm

To find and replace the changes in a whole directory of file... BAMM..

Sweet link... rep'd

powerfool

Actually, if you get into UNIX Shell scripting, you will see that it is common to place commands into variables at the beginning of the script; that way, if you have to change a command, it is only done in the variable. Since PowerShell is really trying to go after the UNIX environment fans, it stands to reason that it would be usable here, as well.