locked
Communicator 2007 Inactivity Period RRS feed

  • Question

  • Does your Office Communicator client prompt you to sign-in in the morning?  If not, you can probably safely ignore this post.  If so, there is a solution. 

     

    Office Communicator is designed to automatically sign-in.  However, if end-users stay logged into Communicator and lock their machines at night, Communicator may sign the user out and prompt for user credentials.  Below is the Microsoft knowledge base article that identifies this issue:

     

    http://support.microsoft.com/kb/918281

     

    To resolve the potential issue, you can either follow the workaround stated in the Microsoft KB article or you can do one of the following:

    1.       Solution 1 (assuming user is running XP SP2)

    a.       Ensure that the version value of the Kerberos.dll file located at C:\windows\system32 is greater than 5.1.2600.2573.  If so, simply start the Security Accounts Manager service.

    2.       Solution 2 (assuming user is running XP SP2)

    a.       Ensure that the version of the Kerberos.dll file located at C:\windows\system32 is greater than 5.1.2600.2573.

    b.      If the version is below 5.1.2600.2573, start the Security Accounts Manager service.

    c.       Install the hotfix to patch the Kerberos.dll file (click the link above).

    3.       Solution 3

    a.       Install XP SP3

                                                                   i.     Our users that have been running XP SP3 have not noticed any sign-in issues. 

    Tuesday, August 26, 2008 8:17 PM

All replies

  • Just to clarify, Communicator is not supposed to sign out after inactivity.  The above actions should be considered if there are sign-out and/or sign-in issues.

    After completing the above steps, Office Communicator 2007 is running like a champ.

    Hope this helps...

    Keenan
    Friday, August 29, 2008 7:39 PM