Important URL’s for Lync to Skype Connectivity

I am guessing by now everyone that follows Twitter should have seen the flood of tweets around this but I thought I would put together a couple of important links if you didn’t.

Official Provisioning Guide:

Lync Server Provisioning Guide for Lync-Skype Connectivity

For some companies already federated with MSN you may only need to edit your current PIC provider where as others that have never enabled PIC will need to go through the whole PIC enablement process.

From the configuration guide:

To edit a Messenger PIC provider and configure it for Skype, do the following:

1. From a Lync Server Front End Server, open the Lync Server Management Shell.

2. Run the following two commands:

Remove-CsPublicProvider -Identity Messenger

New-CsPublicProvider -Identity Skype -ProxyFqdn federation.messenger.msn.com -IconUrl "https://images.edge.messenger.live.com/Messenger_16x16.png" -VerificationLevel 2 -Enabled 1

3. From a Lync client, you can now select Skype as the PIC provider, and add a Skype client by specifying their MSA account. .

clip_image002

 

Announcements:

Lync Team Blog announcement

Skype Big Blog announcement

Customer comments:

A Customer Perspective: L’Occitane

VoIPNorm

4 comments:

  1. Hi

    Great article i get an error when running this script though saying the following, has anybody else run into this error, is this a Lync 2013 only command as i am running Lync 2010

    New-CsPublicProvider : A parameter cannot be found that matches parameter name
    'IconUrl'.
    At line:1 char:86
    + New-CsPublicProvider -Identity Skype -ProxyFqdn federation.messenger.msn.com
    -IconUrl


    <<<< "https://images.edge.messenger.live.com/Messenger_16x16.png" -VerificationLevel 2 -Enabled 1 + CategoryInfo : InvalidArgument: (:) [New-CsPublicProvider], Par
    ameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Rtc.Management.
    Internal.NewPublicProviderCmdlet

    ReplyDelete
    Replies
    1. Hi Anthony,

      For Lync 2010 remove the IconUrl command and it should work. Seems the IconUrl is 2013 specific.

      Cheers
      Chris

      Delete
  2. Appreciation for nice Updates, I found something new and folks can get useful info about BEST ONLINE TRAINING

    ReplyDelete

Note: Only a member of this blog may post a comment.