M3 Exchange 5.5/PST importing

[Kavey]

I've been scanning the forums, and haven't found anything similar to this yet. I'm attempting to use test some migration of Exchange 5.5 users to Zimbra M3_436. So far, my attempts have been less than promising. The Import from profile feature crashes, and no logs are generated. The import from PST results in:

09-01-2006 15:37:46 [1472]: Creating / starting worker thread

09-01-2006 15:37:46 [1472]: Dispatching work to worker thread

09-01-2006 15:37:46 [1476]: Worker thread started

09-01-2006 15:37:46 [1476]: Work arrived...C:\downloads\srk.pst skramer

09-01-2006 15:37:46 [1476]: Logging on to zimbra server

09-01-2006 15:37:46 [1476]: Using default store

09-01-2006 15:37:47 [1476]: Replicating folder hierarchy

09-01-2006 15:37:47 [1476]: COM Exception: 80004005

09-01-2006 15:37:47 [1476]: Logging on to zimbra server

09-01-2006 15:37:47 [1476]: Using default store

09-01-2006 15:37:47 [1476]: Replicating folder hierarchy

09-01-2006 15:37:47 [1476]: COM Exception: 80004005

09-01-2006 15:37:47 [1476]: Logging on to zimbra server

09-01-2006 15:37:47 [1476]: Using default store

09-01-2006 15:37:47 [1476]: Replicating folder hierarchy

09-01-2006 15:37:47 [1476]: COM Exception: 80004005

09-01-2006 15:37:47 [1476]: Logging on to zimbra server

09-01-2006 15:37:47 [1476]: Using default store

09-01-2006 15:37:47 [1476]: Replicating folder hierarchy

09-01-2006 15:37:47 [1476]: COM Exception: 80004005

Before the utility crashes. I'm assuming the Migration wizard is only for Exchange 2000+ installs as when I try it it results in not being able to select any mailboxes.

One other thing to note. After upgrading from M2 to M3, my administrator account (admin@server) doesn't use a local password anymore. I do have the server setup to authenticate from AD, but in M2 the admin account was still authenticating local, althought the other accounts were authenticating from AD. I had to create an admin account on my AD just so I could log in with it.

Thanks.

[Kavey]

I forgot to mention I'm using an Outlook 2000 client for both the profile and the PST creation.

[bobby]

After upgrading from M2 to M3, my administrator account (admin@server) doesn't use a local password anymore

thanks for the bug report. i think we have a bug filed on this (Bug 5106: always fall back to local auth for admin UI); you can run zmprov mcf zimbraAuthFallbackToLocal TRUE and then it will use the local password settings if the user is not found in the remote auth server. keep in mind that will be true for all users, not just admin.

one proposal you can see in our bug is to also have a separate zimbraAdminAuthFallBackToLocal key

[bobby]

according to the developers, "COM Exception: 80004005" translates to "permission denied". do you have administrator acccess to the pc where the profile and pst are located? did you take a look at the zimbra migration wizard.pdf; there are some other contingencies regarding permissions.

did you get the migration wizard from the new M3 server? exchange 5.5 should be supported.

depending on the privacy of the pst causing the errors, you could send it to us for testing...

[Kavey]

I downloaded the wizard and import utility from the Server according to the docs, so I assume they are for M3, since I downloaded them after upgrade. Both file names end in M3_436.

I will have to double check the guide and make sure I followed all the steps closely.

As for the PST, I'm sorry, but I can't send you this particular PST since it belongs to one of our VPs and might contain sensetive data, but I'll try and see if I can create another PST of non-sensetive data, test it, and send it for testing if need be.

As for the rest of the question, yes I have full administrator access on that system. Logged in as Administrator at the time. When attempting to import that PST, the tool apparently is able to create a new Outlook profile, and add the PST, it just fails to read any data.

I can actually open this profile with my Outlook 2000 client and see the PST with no issues.

The Migration Wizard runs, but appears to just pull the names from Active Directory. I can see all the users and groups from the Windows 2000 server, but I can't import any Exchange 5.5 mailboxes. Maybe I missed something. I'll comb over the documentation again.

[Kavey]

Is it possible that the migration utility sees AD and assumes it's Exchange 2000/2003? We do have Windows 2000 Server on AD, and Exchange 5.5 LDAP is running on a different port.

[Kavey]

After playing with the migration utility some this morning, I'm able to build the Base DN to what I'm assuming is appropiate. The filter section I'm less familiar with. Regardless I'm unable to select any mailboxes. I'm still not positive it's pulling the info from Exchange 5.5. I think it's defaulting to port 389 which would be AD. I believe the backup port for Exchange 5.5 LDAP is 390.

[sam]

A couple clarifications/questions:

I incorrectly told Bobby 8004005 means permission denied, it means MAPI_E_CALL_FAILED which is a generic error used in many situations. Mapi error codes are listed here:
http://support.microsoft.com/default...b;en-us;238119

When running ZCSMigWiz, you must be logged in to the domain you want to import from with a DomainAdministrator account that is also an Exchange Service Admin (for Exchange 5.5). We haven't tested mixed-mode configurations which it sounds like you have.

We have not tested any of these tools with Outlook 2000 only Outlook 2003. For Exchange 2000/2003 we have tested running on the Exchange server.

What version of Windows are you running the tool on? We have tested on XP SP2, Server 2000 SP4 and Server 2003 SP1. We have verified you cannot run the tool on the Exchange 5.5 server running NT4 because WinHttp 5.0 library is no longer available from Microsoft.

How was the PST generated? Is it a PST that was used in an IMAP/POP Outlook profile? Is it a PST that was created by archiving data from an Exchange account? How can we generate a similiar PST to try and reproduce the error here?

[Kavey]

Migration:

I tried it with 3 different accounts, including the Domain Administrator account. All accounts are Exchange 5.5 Administrators too.

The tool was running on a Windows 2000 SP4 with an Outlook 2000 client. (I believe it has been upgraded to SP3). All Windows computers in our network are Windows 2000 SP4, and the servers are Windows 2000 server. I'll have to verify the SP4, but at the very least they are SP3.

PST/Profile import:

The PST was generated via export on an Outlook 2000 client from the Exchange 5.5 account. I'm probably guessing it's the Outlook 2000 client that's the problem. I don't have 2003 available to me.

[sam]

Kavey, thanks.

Can you provide us information about your topology? IE, what are you domains, what version(s) are your domain controllers, what version of windows server are they on, what domain is your exchange 5.5 server in, are there any exch2k/3 servers, are you running the active directory connector, etc. Ideally, we would like to get enough information to replicate your environment here.

If you dont want this information on the forums PM me.