Background:

Exchange 5.5 SP 4 environment (no laughs/comments ), BES 4.1.2

We are in the process of retiring an older Exchange server and needed to move users to two different servers (company split). Users on the first server had no issues with the migration, however after moving the first user to the second server (an exact image of the first) she complained that she could no longer send mail. We moved her on Friday and her last sent time, according to BES, is 10:54PM on Saturday.

Any thoughts? Permissions are correct throughout the Exchange organization. The BESAdmin has rights to all the servers.

This is what I would do. Check between each step to see if its working.

1. Register handheld on wireless network.
2. Regenerate encryption keys
3. Resend service books from BES.
4. Wipe and reactivate.

If this fails, check the permissions again.

watch this:
support.microsoft.com/kb/912918

You need special permissions on exchange if you apply a newer security patch.

Still not working. I just confirmed that BESAdmin has Send As permissions in AD and Service Admin permissions in Exchange 5.5.

Is there something else I am missing? I re-activated it and it still isn't working.

Is she getting red x's on her sent messages? If so, open them up and see if the error can provide any insight.

Is the user account still exisiting on the old BES server? If so delete it, the do a security wipe of the device. Re-add the user to the new BES. Activate the device/user. You may have to run the handheldcleanup tool on the old server
after removing the user to ensure the BES agent re-scans the address book of the Exc 5.5 server, since it's directory service is local to the mail server.

I have found when moving a mailbox to a different information store, that I must run this command utility on the BB server: Handheldcleanup -u
then I have to reboot the BB server.

you shoud execute a handheld cleanup as this will update the DN of where the users mailbox resides. In addition, the error message the user recieves could point you in the right direction. check in the subject heading of a failed message. can you post?

I had the same issue and a reboot of BES solved the problem.

Looks like this solved the problem, unfortunately. This isn't reall a server that can be rebooted very often, hopefully it won't happen again.