Showing posts with label OCS 2007 R2. Show all posts
Showing posts with label OCS 2007 R2. Show all posts

Thursday, February 16, 2012

Tracking IM usage in OCS 2007 R2

I could not find something generic that comes out of the box from Microsoft to perform retrieve the usage of Instant Messaging by users in my infrastructure setup for some auditing purposes.
The below is a little SQL query which I have written for the purpose to share.



A sample screenshot of the output is as below



 Declare  @user varchar(50)
Declare @ startdate,@enddate datetime

'Replace usersip with your user's SIP address
Set @user = 'usersip'
'Replace mm/dd/yyyy with appropriate dates
set @startdate = 'mm/dd/yyyy'
set @enddate = 'mm/dd/yyyy'

SELECT [SessionIdTime] as 'StartDate'
        ,[SessionEndTime] as 'EndDate'
      ,user1.UserUri as User1
      ,user2.UserUri as User2
      ,[User1MessageCount]
      ,[User2MessageCount]
     
  FROM SessionDetails

  left join dbo.Users user1 on user1.UserId = User1Id
  left join dbo.Users user2 on user2.UserId = User2Id

Where (datediff(hh, convert(date,SessionIdTime),@enddate)< datediff(hh,@startdate,  @enddate)) and user1.UserUri in (@user)

Saturday, February 11, 2012

Using Lync Client for OCS

While the new Lync Client brings a lot of new functions and a complete new look (nice one too J), it isn’t compatible with a OCS 2007 R2 environment. Another downside is that it can’t be installed together with Communicator 2007 on a single machine. This will benefit when a infrastructure is in the midst of migrating from OCS to Lync or when OCS users requires connectivity to both OCS 2007 R2 and Office365 Lync.
Out-of-the-box the client will give you an error message when you try to sign in into an OCS 2007 R2 pool, stating that the version is not correct. This tells me there IS some kind of communication, however, it’s being detected and blocked.
After some research from Google,  it has been found that there is a way to run the Lync 2010 client on a OCS 2007 R2 environment – simply by bypassing a version check. To bypass this check, you have to create a new registry entry:

Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
Name:  DisableServerCheck
Type: DWORD
Value: 1 (00000001)

When this entry has been created, the version check will be skipped, and the Lync Client WILL logon to the OCS 2007 R2 environment. Actually, most of the functions just work fine! IM, Presence, calling (MOC to MOC or MOC to Lync)  and video all as expected.
Of course there are some functions which don’t work correctly. One of these functions is the “Live Meeting” functionality; this is now built-in into the Lync Client, while in the previous version it was a separate client. Installing Lync will uninstall the LiveMeeting plug-ins in outlook as well, disabling you to schedule an old-fashion meeting. The other limitation that came with this workaround is that the address book cannot be synchronized which means that you will not be able to find anyone that was not added to your contacts previously in MOC. (To workaround this you could find the person in outlook and form there initiate a IM session, tedious but workable)

Wednesday, February 8, 2012

OCS contact details not updated!

There will be instances when an OCS user in an enterprise have some details such as title changed in the active directory. The attributes have since been updated i the Exchange GAL. However, the changes are not reflected on the OCS user's properties.

By default, every night at 1:30AM the new address book is updated and at some random time within the first hour of logging in each day the local workstation downloads updates from the day before that are included in the compact delta file. In my opinion this next part is an overlook during the design, there are 2 AD attributes that are NOT included in the compact delta file, "office" and "title".Perhaps the Microsoft Developers did not think this would change often enough to warrant including it in the code, nor will it ever be.


The full and legacy delta files continue to include these attributes. The legacy and full delta files are only downloaded when a NEW galcontacts.db file is downloaded to the workstation. Another loophole in the programming is, even though the local galcontacts.db file displays the correct attributes, it will NOT reflect in MOC unless the user who's title, or whatever, changed has them as well.

Solution:

1) Logoff and close MOC client
2) In Windows 7, navigate to the path C:\Users\<username>\AppData\Local\Microsoft\Communicator\<user sip>
3) Delete the files GalContacts.db and GalCOntact.db.idx
4) Re-launch MOC client. Give a few moments for the files to be re-downloaded.