Re: Exchange server - Mailboxes not accessible
- From: "John Fullbright" <fjohn@donotspamnetappdotcom>
- Date: Mon, 6 Apr 2009 09:52:28 -0700
Basically, for Outlook 2003 and prior, if you move the mailbox and don't
leave the old mailbox server up for a while, the clients have issues
redirecting. By stipping the mail attributes and recreating them, you
simply updated the home MDB attribute.
"Henrik" <Henrik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9568CC2D-CE75-4EEA-93AF-356993FA4842@xxxxxxxxxxxxxxxx
I respnd to my own thread..
Reason/solution
I migrated a server from VMWare GSX to ESX
On the target (now productions erver online) i made some changes.
Problems occurred and I decided todo the migration once again.
Changes made above were registered In AD (such as mailbox stores for each
user etc).
On the second migrated server I one again wre at the original server
without
the changes made on the first migrated srever above.
Spite this, changes made on the first server now shows up on my second
server wre I have NOT made any changes (these or any other changes).
When going in to the various mailbox stores, all original mailboxes are
disconnected from their user accounts.
New mailboxes are starting to show up on the mailbox stores when users are
starting to connect.
Solution
On all users accounts In ADUC, mark them, run exchange task and delete
mailbox (for all users with disconnected mailboxes marked with a red cross
on them).
In Exchange system manager, run clean up agent on all affected mailboxx
stores
One mailbox at a time, right click the mailbox choose reconnect and
connect
to the original account
Outlook should now work without any further actions and no need to
reconfigure mapi profiles.
Some cellphones may need to have new profiles created to be able to sync
thru OMA.
Some issues on my part that I have learned:
Make shure you have established a conntact with external experts sources
to
be alowed to contact in case of need.
Realy important, create a full backup of the server and of Exchange
Remove client / server AV before migration, not only disable
stop all Exchange AV
Remove Windows Defender
After successfull migration, on the new server creat a backup emediatly
Do not make any changes untill you have had the srever In production for a
week or so.
Then, if needed, create a new backup and after that, start to make
changes.
I did the same migration 4 times this weekend before I got It right.
The reason was that my AV (spite configurations related to MS KB articles
regarding exclusions etc ) snapped one Exchange log from me after two
migrations and screwed up my server. I havent found the missconfiguration
yet but I removed the client/server AV completly instead.
For me, problem is solved.
Thanks to anyone that may have given this thread time.
--
//Henrik (Hear), MCP-SBS, SBS Specialist,
"Henrik" wrote:
*************
I need to add the following ..
The created MB Store that I created on the first migrated (target)
server,
now shows up In Exchange on my second migrated server (target), despite
that
the MB Store was not created on the second one. This makes this an AD
question!??
If I try to delete this MB Store I get the error message :
"One or more users currently use this mailbox store. these users must be
moved to a diferent mailbox store or be mail disabled before deleting
this
store.
ID no: c1034a7f
Exchange system manager"
This indicates that users that I moved on the first migrated server that
now
Is not, In AD is still configured that they reside In this Non-existing
but
yet are, MB Store.
The stor ethat is currently not mounted, can not be mounted with the
failure
message:
"At least on of this stores database files is missing. Mounting this
store
will force the creation of an empty database. Do not take this action if
you
intend to restore an earlier backup. Are you sure you want to continue?
Yes/No."
My thoughts:
Answer yes to the latest question above, create new database files, and
the
move all users to this MB store that had its db files created. This moves
all
users that were moved before to the store that AD thinks they allready
resides in.
Any other ideas?
//Henrik
*****************
"Henrik" wrote:
Hi,
I have problems of major kind.
AD 2008, Exchange Ent 2003 SP2 on Win 2003 Std w SP2,
I have migrated an Exchange server from an old virtual solution (VMWare
GSX
to VMWare ESX 3.5i).
I had to do the migration twice because of problems first time and Im
sure
these problems has come and bite in the as after the second shot.
Problems first time:
Mailbox store system mailbox was lost, one MS KB says to create a new
MB
storre and move mailboxes, the delete the current MB Store.
During the move of mailboxes an extensive logging occurs (as designed
probably) wich results In a full disk that makes some logs corrupt and
two
of three of my MB Stores to stop working.
I decide to to the migrationa second time wich now has resulted In a
new
great server except for the fact that no Outlok clients can connect to
Exchange.
I suspect that the creation of a new MB Store on the first migration
affects
the servers that was migrated the second time.
Also I suspect that the fact that alot of mailboxes was moved after the
first time i migrated the server wich, after the second migration, now
recides on their initial MB Store.
What effects Is caused by the creation of a new MB Store and what are
the
effects of the move of mailboxes between MB Stores?
No errors on the Exchange servers system and application logg.
I do not no hiw to fix this and do not know what to do and i urgently
need
to get my exchange server online tomorrow (Sunday 3PM +2 CET).
Pleas Help
Regards
//Henrik (Hear), MCP SBS,
.
- References:
- Exchange server - Mailboxes not accessible
- From: Henrik
- RE: Exchange server - Mailboxes not accessible
- From: Henrik
- RE: Exchange server - Mailboxes not accessible
- From: Henrik
- Exchange server - Mailboxes not accessible
- Prev by Date: RE: Exchange server - Mailboxes not accessible
- Next by Date: Re: Delegation Configuration on the Server
- Previous by thread: RE: Exchange server - Mailboxes not accessible
- Next by thread: Re: Edge & Licensing
- Index(es):
Relevant Pages
|
