Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
EXE Custom Command w/ Two- or Multi-Party SessionType? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi all -

    I am working on a custom application that we would like to deploy to the desktops within our company.  We would like to allow the user to launch an application and invite other contacts to launch the same application on their desktops.  According to the Communicator 2007 Deployment Guide, what I'm attempting sounds possible, though it's not working so far.

    According to the document, you can define two types of applications:

    *  Applications that apply only to the current user and are launched on the local machine.

    *  Applications that involve additional users, such as an online collaboration program, and must be launched on each user's machine.


    In the registry update, I have defined the ApplicationType to be Executable ("0"), and specified a SessionType of Two-Party Session ("1").  This is my sample reg update, which differs from the example given on page 24 of the Deployment Guide only in the path and application name:

    Code Snippet

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\{0002DF01-0000-0000-C000-000000000046}]
    "Name"="Local Application"
    "HelpMessage"="The Local Application is not installed. Contact the Help Desk for more information."
    "ApplicationType"=dword:00000000
    "SessionType"=dword:00000001
    "ApplicationInstallPath"="C:\\HelloOCS.exe"
    "Path"="C:\\HelloOCS.exe %user-id% %contact-id%"
    "ExtensibleMenu"="ConversationWindowActions;MainWindowRightClick"


    When using ApplicationType of Executable and SessionType of Two- or Multi-Party as above, the custom action appears in the proper menus, but does not launch on the machine of the first user, nor does the selected contact receive any notification or invitation at all.  Specifying a session type of Local ("0") launches the application on the originator's desktop, so I know there's no problem with the reg entry or the application.

    From local testing, I think that an Executable ApplicationType and Two/Multi-Party is not a valid option, and that Two/Multi-Party sessions are only valid for online collaboration scenarios where the ApplicationType is Protocol (where the value would be "1" and a URL would be launched instead of a locally installed application). 

    Can anyone here confirm that this is the case?  I belive that the document is unclear on this, and the example provided on page 24 will not work at all.

    Thanks for any assistance,

    Bill


    Friday, February 1, 2008 10:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Just in case anyone runs into the same trouble I was having and happens upon this thread, the problem seems to be that the example in the Communicator Deployment Guide on page 24 is incorrect.  The example shows the user-id and contact-id parameters included in the "Path" key:
    "Path"="C:\\cltest.exe %user-id% %contact-id%"

    And in the table above the example, the description for "Path" states:
    Full path to be launched along with any parameters, including the default parameter of %user-id% and %contact-id%.


    In my local testing, this causes the whole thing to break.  I changed my sample reg update in the original above to remove the parameters from the "Path" entry, and the application is launched on both the originator and invited contact. 
    Thursday, February 7, 2008 2:43 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Just in case anyone runs into the same trouble I was having and happens upon this thread, the problem seems to be that the example in the Communicator Deployment Guide on page 24 is incorrect.  The example shows the user-id and contact-id parameters included in the "Path" key:
    "Path"="C:\\cltest.exe %user-id% %contact-id%"

    And in the table above the example, the description for "Path" states:
    Full path to be launched along with any parameters, including the default parameter of %user-id% and %contact-id%.


    In my local testing, this causes the whole thing to break.  I changed my sample reg update in the original above to remove the parameters from the "Path" entry, and the application is launched on both the originator and invited contact. 
    Thursday, February 7, 2008 2:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You are right. This worked for me too! Thanks!

     

    Thursday, February 14, 2008 1:06 PM