OCS/LCS Presence status KNOWN and Improperly Homed SIP URI(s)

UPDATED!
Hi all,
all last week, my fellow and I squeeze our brains trying to find the cause of a problem between users presence status of LCS 2005 SP1 and OCS 2007 R2.
In first please we have installed all hotfixes at server level and communicator level without luck. (check the patches below)

• For Office Communicator 2007 to coexist with Office Communications Server 2007 R2, you need to apply the latest update rollup package for Office Communicator 2007. The rollup package is provided in the Microsoft Knowledge Base article 957465. For details, see Knowledge Base article 957465, "Description of the Communicator 2007 hotfix rollup package: December 19, 2008," at http://go.microsoft.com/fwlink/?LinkId=139874.
• For Mediation Server 2007 to coexist with Office Communications Server 2007 R2, you need to apply the update provided in the Microsoft Knowledge Base article 956829. For details, see Knowledge Base article 956829, "Description of the update package for Communications Server 2007 Mediation Server October, 2008," at http://go.microsoft.com/fwlink/?LinkId=139876. In addition, you need a script to associate Mediation Server 2007 with Office Communications Server 2007 R2 to send QoE reports. For details, see “Associate Office Communications Server 2007 or Office Communications Server 2007 R2 Mediation Server with Office Communications Server 2007 R2 Pool” at http://go.microsoft.com/fwlink/?LinkId=144354.
• For Office Communications Server 2007 to coexist with Office Communications Server 2007 R2, you need to apply the update provided in the Microsoft Knowledge Base article 956389. For details, see Knowledge Base article 956389, "Description of the update package for Communications Server 2007: November 2008," at http://go.microsoft.com/fwlink/?LinkId=137299.
• For Office Communicator 2005 to coexist with Office Communications Server 2007 R2, you need to apply the latest update rollup package for Office Communicator 2005. The rollup package is provided in the Microsoft Knowledge Base article 949280. For details, see Knowledge Base article 949280, "Description of the Communicator 2005 hotfix rollup package: December 19, 2008," at http://go.microsoft.com/fwlink/?LinkId=139875.
  

  Important:

  If you apply this update, be sure to first apply the update provided in the Microsoft Knowledge Base article 950614 to ensure that Office Communicator 2005 users can continue to log in to Live Communications Server 2005 SP1 servers. This prerequisite update is provided in the Microsoft Knowledge Base article 950614. For details, see Knowledge Base article 950614, "Description of the update for Live Communications Server 2005 Service Pack 1: September 2008," at http://go.microsoft.com/fwlink/?LinkId=140105.

• For Live Communications Server 2005 with SP1, if you plan to migrate global settings from the System container to the Configuration container, you must apply the update provided in the Microsoft Knowledge Base article 911996. For details, see Knowledge Base article 911996, "Description of the update for Live Communications Server 2005: February 10, 2006, rereleased July 11, 2006," at http://go.microsoft.com/fwlink/?LinkId=132177.
• For audio/video (A/V) conferencing, it is recommended that you apply the update provided in the Microsoft Knowledge Base article 956831. For details, see Microsoft Knowledge Base article 956831, "Description of the update package for Office Communications Server 2007 Audio Video Conferencing Server: October, 2008," at http://go.microsoft.com/fwlink/?LinkId=139896.

The next step was run a DBanalize /report:diag against all LCS 2005' DBs and we found under Improperly Homed SIP URI(s) , several users moved to OCS or to another LCS server, after a complex analysis we run several SQL queries from SQL Server Management Studio Express.

select ResourceId
from dbo.Resource
where UserAtHost like '%user_account%' 

select *
from dbo.HomedResource
where ResourceId= Resource ID (from the lastest query)

And amazingly..we'found these users moved in the LCS DB'tables.

Workaround 1 ....not recommended

Delete the record in the table (do and DB backup first) and be very careful, and you see immediately the presence status fixed.

Workaround 2

Move the user from OCS to the original location, wait for the AD replication and move back to OCS, this will delete the record in LCS database and fix the issue.
To avoid that the user used to moved must be member of RTCDomainUserAdmins group, beside of the necesary to move OCS users

Thank Fabi for your help!!

Be free to contact me at dario.may@gmaill

-Dario