While I don't doubt what metiCkOne has said, there has to be something else in metiCkOne's build that is different as this is happening to all our D1 users and it's not an exchange server active sync issue. I've created new sync policies, edited policies, removed all phones from the mailbox and have flashed my phone back to stock so many times it's getting sickening and it still has the same issue. But, this is all on exchange 2010, so it could be 2007 is different as I haven't tested that. I do know that 2003 doesn't support the phones so it's not an issue...Interesting. I'm running metiCkOne's odexed rooted FRG22D, and continue to be getting all my Exchange email and calendar related goodies with no change at all to my Droid's login processes. It's like nothing changed anywhere.
And metiCkOne has made it very clear he left both FRG01B and FRG22D completely virgin with the exception of rooting, busyboxing and adding his name to the build (and deodexing with the deodexed version). The only major system level thing I have done is install a Chevy kernel.
I'm still convinced there has to be some feature, probaby for security, that my Exchange server doesn't have turned on, that FRG22D has this problem with. I've never used entry-security on my Droid, so perhaps it has something to do with that too.
I have to think, though, that Verizon is aware of this Exchange issue and is looking at it closely by now. It's affecting you and your institution very heavily, and it must be doing the same for others too.
Btw, I've never received FRG22D in either the patch or the full form as an OTA from Verizon. Perhaps still to come, perhaps not, because I'm using it already in the metiCkOne version???
On a side note, from what I have heard, Moto is coming out with another patch to fix this in the next 30 days, so we'll see.
It is kind of fun trying to find a work around though, in a twisted sort of way