Migrated mailbox from Exchange 2003 to 2010 - cannot use OWA or ActiveSync

First thing to check is that the users have permission inheritance enabled. You will need to use the Security tab in ADUC to check that. If not, enable it. Then wait an hour or so for the permission to be seen by Exchange, or restart the information store (although that will kick everyone out).

Next thing to check is that they aren't a member of a protected group such as Administrators. That can stop things from working correctly as well.

Simon.

Simon -
Already did that.    I have OWA working - I disabled forms based authentication.   Weird.   Set to Basic and now the user works.   However, ActiveSync still a problem if you lived on the old server.    Rebooting it, will see what happens.  
This is behind an ISA server - if I am inside, and go to https://mailserver/Microsoft-Server-ActiveSync I get a http 501/505.   Outside, I get a 403.

Also to be clear -
I have a mailbox made with 2010.    Gets ActiveSync mails fine.   The mailboxes that are older from the old 2003 environment will not attach to ActiveSync even though they are migrated over to the 2010 server.     Mailboxes live on 2010 server.

The ISA is the unknown issue for me - as I don't have any sites with that product in use (I have never deployed it myself). Therefore you don't know if the problem is with Exchange or with the ISA configuration.

Usually I would suggest running a test account through the Test tool from Microsoft - http://exrca.com/ to see what that returns, however it isn't wise to do that with a live account.

There must be something different between the two account types.

Simon.

I have done the exrca.  

It fails ActiveSync with a 403 error.    

HOWEVER,

2010 Account still sends/receives mail just fine.  
2003 Account cannot.

I am currently checking ADSI Edit to see if there is some kind of stark difference.   The only thing that I see at the moment is that when i double click on the user, I don't see a folder for the device like I do on my other guy that works.

So far I have gone into ADSI Edit and pretty much made sure all values identical.   Meaning, no missing ones.     Still no go.

There is nothing else I have to suggest, because I suspect it is ISA that is the cause, or at least making troubleshooting difficult. While ISA is there you are very limited on what you can do, because you are unable to verify if it is ISA or Exchange with the problem.

Simon.

Because I solved it myself with the help of MS