locked
Live Meeting User Account via Pilocy RRS feed

  • Question

  • Is there going to be a mechanism of defining the Server and Advnaced Connections Settings for Live Meeting?  The ADM Template for Communicator allows this but I don't see an option for the Live Meeting Accounts?

     

    Thanks!

    Thursday, May 17, 2007 3:47 PM

Answers

  • Listed below is the registry settings that are shared between the Communicator and LiveMeeting client and server name is one of them.  There is not going to be a mechanism to automatically populate the account settings.  This is from the OCS_Console_deployment guide.

     

    The registry keys listed below in Table 2 are shared between the Microsoft Office Live Meeting client and Microsoft Office Communicator. When you install one client, these registry keys are created and provisioned for both clients.

    Table 2.   Registry keys shared between Microsoft Office Communicator and the Microsoft Office Live Meeting client  

                                                                Registry Key                     

    Description

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressExternal

    Specifies the server name or IP address used by a federated contact when connecting from outside the external firewall.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressInternal

    Specifies the server name or IP address used by the client when connecting from inside the organization’s firewall.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerSipUri

    Specifies the SIP URI used by the client when connecting to Office Live Meeting, the Conferencing Add-in for Microsoft Office Outlook, and Office Communicator.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\Transport

    Defines the network protocol used by the client: Transmission Control Protocol (TCP), or Transport Layer Security (TLS).

     

     

    Louis H

    Thursday, May 24, 2007 8:18 PM

All replies

  • We are checking on this and will post here once we find out.
    Thursday, May 24, 2007 5:57 PM
  • Thanks!  I'm eager to get this resolved.
    Thursday, May 24, 2007 6:03 PM
  • Listed below is the registry settings that are shared between the Communicator and LiveMeeting client and server name is one of them.  There is not going to be a mechanism to automatically populate the account settings.  This is from the OCS_Console_deployment guide.

     

    The registry keys listed below in Table 2 are shared between the Microsoft Office Live Meeting client and Microsoft Office Communicator. When you install one client, these registry keys are created and provisioned for both clients.

    Table 2.   Registry keys shared between Microsoft Office Communicator and the Microsoft Office Live Meeting client  

                                                                Registry Key                     

    Description

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressExternal

    Specifies the server name or IP address used by a federated contact when connecting from outside the external firewall.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressInternal

    Specifies the server name or IP address used by the client when connecting from inside the organization’s firewall.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerSipUri

    Specifies the SIP URI used by the client when connecting to Office Live Meeting, the Conferencing Add-in for Microsoft Office Outlook, and Office Communicator.

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\Transport

    Defines the network protocol used by the client: Transmission Control Protocol (TCP), or Transport Layer Security (TLS).

     

     

    Louis H

    Thursday, May 24, 2007 8:18 PM
  • All-

     

    I have navigated to

     

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressInternal

    The correct SIP and InternalAddress are set in the registry.

     

    However, if I attempt to open up live meeting it is unable to connect to the internal server because the internal server address is not populating in the fields.

     

    Any ideas why the address would not be entered in the field even though it is set via policy (Communicator ADM GPO). The settings are working for the communicator client.


    Thanks!


     

    Tuesday, October 2, 2007 9:42 PM
  • How does this registry key get populated from the GPO.

     

    HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\

     

    We set "Specify Server and Transport" in the GPO Computer Configuration. Does this need to be set in the GPO User Configuration to populate \UcClient correctly?

     

    Thanks

    Friday, October 5, 2007 7:11 PM
  •  

    I ended up actually adding a registry setting via GPO to add this.

     

    Thanks for the response.

    Monday, October 8, 2007 1:56 PM
  •  

    Does anyone have the exact code they used to make the custom adm template?
    Thursday, October 25, 2007 10:58 PM
  • from another post..

     

    Seems microsoft has released an adm for LiveMeeting

    http://support.microsoft.com/?kbid=948741#appliesto

     

     

    You can request the hotfix by contacting Microsoft Support or buy using the online request page: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=948741

     

    solved my issues....

    Tuesday, September 9, 2008 8:11 PM