Link to home
Start Free TrialLog in
Avatar of irm-is
irm-is

asked on

BPOS

Hello,
My company signed up for Microsoft BPOS a few months ago and we have been migrating our users' mailboxes throughout this time.  All migrations were successful (granted some had issues but all good in the end) until we got to the last user.
His migration actually went very well, no error message and finished very fast.  The problem comes when we try to set him up next day.  The first time connecting, BPOS uses the Microsoft On Line Services Signon application to configure the user's new Outlook profile, Office Communicator and other sevices that we signed up for.  Outlook fails to configure his profile.  We tried it on different computers (domain and non domain) with the same result.
Microsoft first told me that something is wrong with this user's account on my domain but I quickly disputed that with the following reasons: 1) he is able to logon to the signon application successfully, 2) he is able to logon to Communicator successfully with the same account, 3) he is able to logon to OWA and mail is flowing there and lastly 4) his migration completed without error.  It is only Outlook that's having issue.
Has anyone seen this?  Any help would be greatly appreicated.
Thanks
Kit
Avatar of mingano
mingano

If you haven't already switch to NON-cached mode.  See if that works.

Also try to connect using the /safe switch (from the run prompt type outlook/safe) to see if he can get in that way.

If that works then make sure you delete any existing .ost files (presuming that you have verified all of his data to be intact by the way) and switch back to cached mode.
Avatar of irm-is

ASKER

Hi mingano, thanks for your advice.  We had try that before but it doesn't help.

Kit
ASKER CERTIFIED SOLUTION
Avatar of mingano
mingano

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of irm-is

ASKER

Hi Mingano,
I thought I would try to configure the user again today to see if anything changed.  Surprised, it just magically worked.  I wonder if Microsoft just quietly fix the problem in the back.  I'm going to give you the points anyway since you did try to help me.
Thanks
Kit