Okay, first off, I have only 2 running messaging agents: 1 and 2
I already explained this on this
thread but, I'll re-state again,
We have more than a dozen Exchange servers spread geographically across the world and we only have 3 BES (at least that what I know of- some IT guys just installs test BES machines sometimes) in our WAN. But only one BES is under mu control (the one in asia pacific).
Anyways, I know that this is not advisable, as stated in hdawg's article here
And, as stated as well in that above article, we (me and my Exchange admin) edited the registry of our BES to have 10 messaging agents..
Now just this morning MAGT2 seem to have "failed" and no matter how we restart the services and the whole server itself- MAGT2 users seem to still can not send/receive and do lookups. Before a server restart would actually force the MAGT to restart.
I also tried this
to manually restart the MAGT to no avail.
So we tried going into EDIT PROPERTIES of one user from MAGT2 and went into Advanced and changed the value to TRUE to allow to use another MAGT. After that the user went to MAGT 300- then all of a sudden everything works! Well just for this user.
My question is:
As a workaround:
1. Do we have to manually change users from MAGT 2 to MAGT 300 - no "batch transfer" of some sort?
And to permanently resolve the issue:
2. How do I actually "revive" MAGT 2? Is there still a way?
I can give you some log entries upon request..