locked
Lync Multi-tenant installation RRS feed

  • Question

  • Hi

     

    We are currently running a R2 standard edition Front-end with consolidated Edge which we would like to upgrade to Lync (side-by-side upgrade).

    Because of how we are organized, we would like to separate our sub companies on our own shared Lync platform (run our own little “hosted OCS”).

    Is this feasible?

    I have read that the documentation for multi-tenant installation is yet to be released.

    Some people also state that there might be a different version of Lync?

     

    Any information regarding multi-tenant installation would be greatly appreciated

     

     

    Monday, December 6, 2010 11:54 AM

Answers

  • This is definitly feasible.

    While I do not see any multi-tenant specific documentation on the Lync Technet documentation, it probably is on it's way. I'm reading through the documentation and I have to say I already saw multiple configuration options that can be used in multi-tenant environments like msRTCSIP-GroupingID and Simple URL Options.

    For the moment I would recommend you to make a list of your requirements for the environment you want to build and see how you can implement it based on the documentation.


    Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be
    • Proposed as answer by Ruben Nauwelaers Tuesday, December 7, 2010 6:36 AM
    • Marked as answer by Ben-Shun Zhu Wednesday, December 15, 2010 10:53 AM
    Monday, December 6, 2010 1:08 PM

All replies

  • This is definitly feasible.

    While I do not see any multi-tenant specific documentation on the Lync Technet documentation, it probably is on it's way. I'm reading through the documentation and I have to say I already saw multiple configuration options that can be used in multi-tenant environments like msRTCSIP-GroupingID and Simple URL Options.

    For the moment I would recommend you to make a list of your requirements for the environment you want to build and see how you can implement it based on the documentation.


    Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be
    • Proposed as answer by Ruben Nauwelaers Tuesday, December 7, 2010 6:36 AM
    • Marked as answer by Ben-Shun Zhu Wednesday, December 15, 2010 10:53 AM
    Monday, December 6, 2010 1:08 PM
  • This is definitly feasible.

    While I do not see any multi-tenant specific documentation on the Lync Technet documentation, it probably is on it's way. I'm reading through the documentation and I have to say I already saw multiple configuration options that can be used in multi-tenant environments like msRTCSIP-GroupingID and Simple URL Options.

    For the moment I would recommend you to make a list of your requirements for the environment you want to build and see how you can implement it based on the documentation.


    Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be

    I can see that there is also a new Active Directory Attribute called msRTCSIP-TenantId (http://technet.microsoft.com/en-us/library/gg398944.aspx). I wonder what that could be? There is not much info provided about that yet.
    Tuesday, December 7, 2010 10:49 AM
  • Depends on how strict you want to be with the tenants.

    The GroupingID will let you partition the address books. The AD Property Sets will keep the presence bubbles from showing in Outlook, etc.

    If you want to be really strict about partioning the Tenants, then you could use the TenantID and install the IncomingFederation/OutgoingFederation server applications on the Front end servers.  This isnt all of it though, because you are going to have to setup the Simple URL's at the Tenant Global scope. (This isnt possible with the existing powershell cmdlet's, so expect to do some direct DB inserts into the XDS)

    As you can see, unless you really know how this beast works at a low level and have the capability to dig deep.. you probably want to stick with GroupingID and Property Sets.

     

     

    Tuesday, December 21, 2010 5:03 AM
  • Thank you for all answers, and a happy new year!

    I agree that the msRTCSIP-GroupingID, Simple URL Options and msRTCSIP-TenantId makes administration and separation easier than with the earlier versions (Not running HMC).

    GroupingID is definitely something that has been missed.

    It seems like we will end up with just locking down the standard install for now.
    It will be interesting to see if it will be possible to create a separate pool per company when the documentation is released without adding dedicated front-end servers.
    Monday, January 3, 2011 2:10 PM
  • I would like to explore using IncomingFederation/OutgoingFederation. Can you point me to any documentation on these applications?

    Thanks.

    Wednesday, June 8, 2011 4:19 PM
  • Would like to check if someone has used the msRTCSIP-TenantId, the technet site does not offer information on its usage.

    Essentially, with msRTCSIP-GroupingID, i can restrict the lookups but if I type the full SIP URI, then i am able to see other users. I would like to restrict this, so all users in a particular OU should be able to see each other but nothing outside that (even if they know the full SIP URI).

    Also, any news on Lync multi-tenancy and when this is being released ?

    Thanks.

     

    Friday, July 22, 2011 2:25 PM
  • Would it be feasible to give each tenant their own overall admin rights for all the various elements?
    Thursday, September 29, 2011 11:42 AM
  • Hi,

    Microsoft Lync Server 2010 Multitenant Pack for Partner Hosting Deployment already released and accessible through Volume Licensing site. https://www.microsoft.com/licensing as "Lync Server 2010 Enterprise MultiTenant Pack for Partner Hosting".

    The Deployment Guide has been published at http://www.microsoft.com/download/en/details.aspx?id=28587.

     


    Best Regards,
    Hany Taha | UC/Voice Infrastructure Consultant | Technical Consultancy Services | Nile.Com | Mobile: +20 (10) 01686836
    • Edited by Hany Taha Monday, January 9, 2012 12:39 PM
    Monday, January 9, 2012 12:38 PM
  • Yes, but Multitenant pack for partner hosting is very specific and inflexible for hosters who already have an existing OU structure of clients. Forcing to move to a "OCS Tenants" OU, no clear migration path for OCS 2007 R2, and having to scale certificates all add to a nightmare for hosters.
    Thursday, February 23, 2012 3:34 PM
  • But is this supported by Microsoft? Will they support my Lync integration if we use this segregation?
    Thursday, February 23, 2012 7:34 PM
  • Ho do you do install "Microsoft Lync Server 2010 Multitenant Pack for Partner Hosting"?


    微软.动态数据中心.统一沟通.实战培训! QQ :LiuJinFeng@msn.com 手机:136 61 90 90 31

    Monday, July 30, 2012 11:31 PM
  • I am currently using msRTCSIP-GroupingID to restrict the lookups of other OUs on our system but if I type the full SIP URI, then i am able to see other users. Is there a way restrict this, so all users in a particular OU should be able to see each other but nothing outside that with out installing multitenant pack?
    Sunday, September 9, 2012 10:56 AM