I have an OCS 2007 SE server running on Server 2003 R2 Standard. We have multiple domains in our forest, but they're all configured for use in OCS and the cert is setup properly. I've been deploying Communicator in waves since we have so many users, and up until now the 250 or so users I've deployed it to have all worked fine. When deploying Communicator to their machines I also go into AD and enable their user account to use OCS and verify they're added properly. All of them are setup so their SIP address matches that of their primary SMTP address.
My last wave of deployments included a remote site of about 20 users. All of the users at that site except for one are able to use Communicator. That user encounters an error reading "cannot sign in to communicator because the sign-in address was not found". I verified that her account in AD is setup properly and Communicator is setup properly on her machine. I found another forum thread that suggested removing the user account from OCS and also suggested making sure the user account was deleted from the OCS database. The problem is, she doesn't exist in the database even after enabling her user account to use OCS and waiting for a full AD replication. When I go to the dbo.Resource table I can run queries and find every user except for her. I have added new users since then and I have even deleted existing users (not from AD but from OCS) and confirmed that they're removed from the database and added back when enabling their AD account to use OCS. This user is on the same domain as the other users at this site and her user account is configured verbatim.
Export working user's and non-working user's attributes in a CSV file, and compare. You should be able to see something which might be preventing this user to be OCS enabled. One thing is sure that user's info has to go in the SQL database before it can login in office communicator.
