In case you don’t realize the way this works is a web part or page that contains the Presence Indicator, calls an Active X controls that calls the ‘name.dll’ on the users local PC which makes a call to the Lync/OCS API
Insure the client machine has the following
- They are using IE or a browser that supports Active X
- Active X is configured to be allowed (At least for zone that SharePoint Sites are in)
- You have installed a supported version of Office and it has all its updates. (Active X and name.dll are installed with Office)
- Has Lync, OCS, or Messenger installed
- Users need to have their SIP address in there SharePoint Profile
- Corrupted DLL on Client machine, try Office repair
- Bug in name.dll, insure that Office and Internet Explorer are up to date
- ActiveX control is not calling into name.dll, insure that SharePoint Sites are in trusted zone and allows the use of Active X controls
- Check that User in Site Collection has SIP address, if not. Then check the SSP, if it does then you need to troubleshoot the sync between Content Database and SSP. http://support.microsoft.com/kb/2388988
- Active Directory user id is missing SIP, add it and wait for User Profile replication.
- Mixed versions of Office Components can cause failure in name.dll, insure that you have the same version of Outlook, Excel, SharePoint Designer and other Office Products.
Plan presence integration (Office SharePoint Server)