Comments on: Exchange Management Shell Export Mailbox to PST script

By: Matt Shadbolt

Matt Shadbolt — Wed, 10 Mar 2010 21:48:14 +0000

Ah of course, I did know that the shell needs to be 32-bit but didn’t put that in my original post. Updated.

By: Fernanda

Fernanda — Wed, 10 Mar 2010 14:35:14 +0000

I ran the shell as administrator and the problem did not resolve.
However, another error message appeared.
I had to install the admin tools for exchange on my desktop because this command has to run on 32-bit computer.
And now it runs ok.

Thanks for the help.

By: Matt Shadbolt

Matt Shadbolt — Wed, 10 Mar 2010 07:29:48 +0000

So it looks like the account your running the EMS shell from doesn’t have permissions to write to that directory. You need to run the shell as a user who has Exchange Admin group membership, and an account that has access to that logs directory?

In the shell you are running EMS from, are you able to create a text file?

By: Fernanda

Fernanda — Tue, 09 Mar 2010 12:07:45 +0000

I just create the directory and another error appeared:
“Cannot open the log file ‘C:\Program Files\Microsoft\Exchange Server\Logging\MigrationLogs\export-Mailbox20100309-090258-6492356.log’.”
I think this command seems to create a log file and open it but, when I come to the folder, the file is not there.

By: Matt Shadbolt

Matt Shadbolt — Mon, 08 Mar 2010 22:24:55 +0000

Does it work if you create the directory?

By: Fernanda

Fernanda — Mon, 08 Mar 2010 14:34:18 +0000

When running the script, the prompt shows the following error:”The log file directory ‘C:\Program Files\Microsoft\Exchange Server\Logging\MigrationLogs’ does not exist.”

Is there a solution for this?

By: mattshadbolt

mattshadbolt — Fri, 15 May 2009 04:36:40 +0000

Good stuff. It’s likely your .NET runtime version is old. Glad you’ve got it working though

By: Dennis

Dennis — Wed, 13 May 2009 19:03:56 +0000

Well a couple things. I believe the issue may have been machine related. My xp machine was the issue as it runs fine on another xp machine and also a vista machine. I can in fact run this without having to use the Get-item cmdlet.

Thanks

By: mattshadbolt

mattshadbolt — Tue, 12 May 2009 23:36:31 +0000

What happens when you run (line by line):

$CurrentHostName = hostname
$CurrentProfile = Gwmi Win32_ComputerSystem -Comp $CurrentHostName
“Logged On As User: ” + $CurrentProfile.UserName

When yo ucall $CurrentProfile.UserName you should receive the DOMAIN\Username your currently logged in with.
I haven’t tested different user permissions, however I don’t think recipient admin will work… I have a feeling you need to have Server Administrator rights or more.
One other thing – are you running Exchange 07 SP1? And are you running the EMS from XP or Vista?

By: Dennis

Dennis — Tue, 12 May 2009 14:29:04 +0000

The Get-item did work.

I think the issue I have is that it fails when trying to get the current user and password. This is the error I get:

Get-WmiObject : Retrieving the COM class factory for component with CLSID {4590
F811-1D3A-11D0-891F-00AA004B2E24} failed due to the following error: 80040154.
At C:\scripts\exportmbx.ps1:5 char:23
+ $CurrentProfile = Gwmi <<<< Win32_ComputerSystem -Comp $CurrentHostName

What exchange permissions does the user running the script need to be able to add the full access right? I want to give the least permission as possible. Will recipient admin work?