One thing that I hear out from customers is that the default timeout behavior of the Lync client is too short.  10 seconds to be exact.  The timeout I’m referring too is when the incoming IM toast pops up and the client auto accepts the IM.  This behavior was a big sore spot when introducing mobile devices where the client would auto-accept an incoming IM before the recipient could actually launch the mobile client.  This resulted in lost IM history or dual IM conversations and was an unpleasant experience for the user.

So today I just learned from a fellow colleague (thanks Chris!!!) that the desktop client behavior can be modified through a registry setting.

In seconds (10-30):

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator]
“IMToastTimeout”=dword:0000000a
“IMToastNoAutoAcceptTimeout”=dword:0000000f

4,356 views
1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 3.00 out of 5)
Loading...

Requirements

  1. Need access to the Adminpak.msi located on the Windows 2003 Server CD-ROM in the …\i386 directory. You can also download from www.microsoft.com/downloads.
  2. Access to the …\Exchsrvr\bin directory on your Exchange 2003 Server.
  3. Windows XP client

Procedure

  1. Open a command prompt.
  2. Change to the directory where the adminpak.msi file is located.
  3. Enter the following command: “msiexec /i adminpak.msi ADDLOCAL=FeADMgmtConsole /qb“.
    This will load the DSA tool along with DNS, AD Sites and Services and AD Domains & TrustReference article “http://support.microsoft.com/?kbid=314978” for detailed instructions on how to use this command.
    Note: I would recommend using a GPO to restirct access to the DNS and the AD tools to prevent your helpdesk from using these tools. The install also creates a MSC called Active Directory Management located in the Administrative Tools folder which you may want to delete. The install WILL NOT create a shortcut to the ADU&C, ADS&S, ADD&T or DNS tools in your Administrative Tools directory…you’ll have to create them on your own. The install will only load the snap-ins.
  4. Copy the following DLLs from your Exchange 2003 server (Default location: C:\Program Files\ExchSrvr\Bin) to your local c:\windows\system32 directory.
      address.dll
      escprint.dll
      exchmem.dll
      glblname.dll
      maildsmx.dll
      pttrace.dll
  5. Open a command promt (or use the one from Step 1).
  6. Change to the c:\windows\system32 directory.
  7. Enter the command: regsvr32 maildsmx.dll.
  8. Done.

Now you can create a custom MMC with only the ADU&C snap-in. This snap-in will have full access to the Exchange Tabs and Tasks with a minimal footprint on the client. One who is so inclined could even package it up as an MSI and publish it to their helpdesk staff via a GPO.

32,076 views
1 Star2 Stars3 Stars4 Stars5 Stars (2 votes, average: 5.00 out of 5)
Loading...

Tired of looking at all those misspelled cmdlet and parameter names in Word.  Use this PowerShell script to add all the Lync cmdlets and parameters into your own custom dictionary.  Very useful for double checking that your cmdlets and parameters are spelled correctly.

UPDATE: (5/8/2012) Modified to include parameters.

Prerequisites: You will need to have the Lync Core Components installed.  Don’t forget to apply the latest updates as well.

#Title: Create-LyncCusomtDic.ps1
#
#Purpose: To parse all the Lync PowerShell cmdlets and parameters and add them to the Microsoft Word CUSTOM.DIC file.
#
#Author: Matt Wade
#
#Version: 2.0
#
#Date: 5/8/2012

Import-Module Lync #You will need to install the Lync Core Components to get this module.  Don't forget to apply the latest CU as well.
$commands = Get-Command -module lync
$mydict = get-content (((Get-Item Env:Appdata).Value) + "\Microsoft\UProof\CUSTOM.DIC")
$newdictentries = @()

foreach ($command in $commands)
{
    if ((($mydict -contains ($command.Name)) -eq $false) -and (($newdictentries -contains ($command.name)) -eq $false))
    {
        $newdictentries += ($command.Name)
    }
    if (($command.Parameters -ne $null) -and ($command.Parameters.Keys.Count) -gt 0)
    {
        foreach ($parameterkey in $command.Parameters.Keys)
        {
        if ((($mydict -contains $parameterkey) -eq $false) -and (($newdictentries -contains $parameterkey) -eq $false))
        {
            $newdictentries += $parameterkey
        }
        }
    }
}
if ($newdictentries.count -gt 0)
{
    $mydict += $newdictentries
    $mydict = $mydict |sort-object
    $mydict
    Copy-Item -Path (((Get-Item Env:Appdata).Value) + "\Microsoft\UProof\CUSTOM.DIC") -Destination (((Get-Item Env:Appdata).Value) + "\Microsoft\UProof\CUSTOM.BAK")
    $mydict | Out-File (((Get-Item Env:Appdata).Value) + "\Microsoft\UProof\CUSTOM.DIC")
}
927 views
1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)
Loading...

Small tool for OCS 2007 R2 and Lync Server 2010 which allows an administrator to import contacts into the database. Importers are included for AIM, Yahoo Messenger, Windows Live Messenger, and for generic text based lists. This tool is provided as-is and is not supported by Microsoft support.

Click here to download…

389 views
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...
Page 3 of 8112345678910...203040...Last »