TEAM AWESOME ... Re-united and it feels so good!

In my geographical area there are a few network and IT professionals that make up "TEAM AWESOME". In my complete oddness I thought that I had invited the last outstanding member. I found out recently that I had not invited her to post on the blog.

Please welcome Nicole Johnson!

Have fun Njo and we look forward to hearing from you.

Generational Differences Thought.

So I was discussing the generational differences in regards to technological advancement.

While we were talking the following statement was uttered.

"Generation Y doesn't create anything, they only modify." (TM)

Though it's possible you could argue creation of a modified item is still creation ... it gets metaphysical.

Import-Mailbox ... Still no love.

So as any of you who read this blog know a client of ours has been having Import-Mailbox cmdlet issues. We opened a case with Microsoft only to find out we knew more about the error than the tech assigned to us. Below are the steps that we went through.

PSS Call.

Checked permissions and verified error.

Installed support tools on S6 and added "transition" account to have send-as and receive-as.

replicated information and logged off.

Logged back on and tried again. Same error.

Created new account and granted most of the same rights except for Exchange View only Admin.

Proceeded to test Import-Mailbox cmdlet with the same parameters.

Ran BOTH Import and Export cmdlets and got the same error. PSS asked for more time to research the issue.

Attempted to re-run process with a different user. Result was the same.

Opened ADSIEDIT and manually forced permissions on the config,services,exchange, ORG container.

Logged off and then back on.

Tried an import and then an export GUESS WHAT....SAME Error DUH!

PSS then asked Technician to run Export-Mailbox on the exchange server itself. This again did not work.

Create Test user and try export SAME error.

Mail-Enable new user and try to open OWA.

This process repeated itself a number of times ...all of them resulted in the SAME MAPI error.

But the below manual process works fine. It's just manual and takes forever.

****Able to successfully move mail via profile migration steps:

Add transition user to full access on the mailbox.

Create a new profile for transition that uses migrating user's mailbox.

Open PST and manually DRAG in the old messages.

Contact User and verify that old content has been properly migrated into the Mailbox.

This is a manual process and will take SOME time to complete.

Manual Process is as follows:

For the manual migration process exmerge must take place first. 

To perform this EXmerge.

Use powershell to grant access with Add-MailboxPermission -Identity -User -AccessRights Fullaccess

Create a new outlook profile while logged into your machine with the migration account.

Copy PST file to your local drive.

Open outlook.

Open the PST drag and drop all items from the PST into the Mailbox according to where they go.

Verify with user that process is successful.

Move on to the next mailbox in the list.

Going to speak with the client tomorrow to see if they got resolution.

Talk to you next time,

C-SQD

Import-Mailbox cmdlet Error.

So in working for a client they had a need to import Exchange 2003 mailboxes cross-forest. This seemed pretty straight-forward according to Microsoft's articles on TechNet and so forth. However as we are all aware things rarely go as planned.

According to MS the process is as follows:
1) Exmerge out the mailbox to a PST.
2) Copy the PST over to a client machine since you cannot Import on an Exchange Server.
3) Open the Exchange Management Shell and run Import-Mailbox ...
4) Be happy since it worked.

Well steps 3 and 4 are kind of a no go for me.

I have verified that the account that I am using has Full Access to the mailbox. Also the account is an Exchange Org Admin and an Exchange Server Admin. This account is a local admin on the client and server as well.

According to all the documentation this should be relatively easy and work once all these are set. But alas I have now had to call PSS. Let's see what they can come up with and where we go from here.

The error that I continuously get is here:
because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error:MAPI or an unspecified service provider.ID no: 00000000-0000-00000000, error code: -1056749164


C-SQD

Question?

Do you think that cloud computing and distributed computing resource solutions that are federated are new thoughts?

Haven't these ideas been kicking around for decades?

Post a comment.