%3CLINGO-SUB%20id%3D%22lingo-sub-56966%22%20slang%3D%22en-US%22%3EPlanning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56966%22%20slang%3D%22en-US%22%3E%3CP%3EUnderstanding%20how%20to%20establish%20a%20hybrid%20connection%20between%20Skype%20for%20Business%20on%20premises%20and%20online%20can%20be%20challenging%20when%20customers%20use%20multiple%20forests.%20The%20Skype%20for%20Business%20product%20group%20has%20worked%20hard%20the%20last%20couple%20of%20months%20to%20unblock%20additional%20scenarios%20and%20make%20the%20existing%20documentation%20clearer.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThe%20authoritative%20documentation%20can%20be%20found%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt603995.aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%26nbsp%3Bbut%20we%20wanted%20to%20include%20a%20quick%20summary%20in%20this%20blog%20article%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFor%20either%20a%20single%20user%20forest%20or%20multiple%20user%20forest%20deployment%2C%20there%20must%20be%20a%20single%20deployment%20of%20Skype%20for%20Business%20Server.%3C%2FLI%3E%0A%3CLI%3ELync%20Server%202010%2C%20Lync%20Server%202013%20and%20Skype%20for%20Business%20Server%202015%20are%20supported%20in%20this%20topology%20(please%20note%20that%20availability%20of%20features%20depends%20on%20server%20version%20you%20are%20using).%3C%2FLI%3E%0A%3CLI%3EExchange%20can%20be%20deployed%20on%20premises%20only%2C%20in%20hybrid%20or%20online%20only.%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%20can%20be%20deployed%20in%20one%20or%20more%20forests%2C%20which%20may%20or%20may%20not%20include%20the%20forest%20containing%20Skype%20for%20Business%20Server.%20For%20details%20on%20support%20for%20and%20limitations%20with%20co-existence%20between%20Exchange%20and%20Skype%20for%20Business%20in%20various%20combinations%20of%20on-premises%20and%20online%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fea22beb9-c02e-47cb-836d-97a556969052%23feature_support%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EFeature%20Support%3C%2FA%3E%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj721919.aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EPlan%20to%20integrate%20Skype%20for%20Business%20and%20Exchange%3C%2FA%3E.%3C%2FLI%3E%0A%3CLI%3EExchange%20Server%202013%20and%20Exchange%20Server%202016%20are%20supported%20in%20this%20topology.%3C%2FLI%3E%0A%3CLI%3ECloud%20PBX%20is%20supported%20in%20complex%20forest%20scenarios%20(as%20long%20as%20all%20Cloud%20PBX%20requirements%20are%20met%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt455212.aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt455212.aspx%3C%2FA%3E).%3C%2FLI%3E%0A%3CLI%3EWe%20used%20to%20state%20that%20%E2%80%9Ccentral%20forests%E2%80%9D%20were%20not%20supported.%20Since%20the%20definition%20of%20central%20forest%20was%20quite%20ambiguous%2C%20we%20replaced%20it%20with%20the%20following%20wording%20and%20hope%20to%20unlock%20additional%20scenarios%3A%20%3CEM%3EWhen%20Skype%20for%20Business%20Server%20is%20deployed%20in%20one%20forest%20(a%20resource%20forest)%20but%20provides%20functionality%20to%20users%20in%20one%20or%20more%20other%20forests%20(account%20forests)%2C%20users%20in%20other%20forests%20must%20be%20represented%20as%20disabled%20user%20objects%20in%20the%20forest%20where%20Skype%20for%20Business%20Server%20is%20deployed.%20An%20identity%20management%20product%2C%20such%20as%20Microsoft%20Identity%20Manager%2C%20needs%20to%20be%20deployed%20and%20configured%20to%20provision%20and%20synchronize%20the%20users%20from%20the%20account%20forests%20into%20the%20forest%20where%20Skype%20for%20Business%20Server%20is%20deployed.%20Users%20must%20be%20synchronized%20into%20the%20forest%20hosting%20Skype%20for%20Business%20server%20as%20disabled%20user%20objects.%20They%20cannot%20be%20synchronized%20as%20Active%20Directory%20contact%20objects%2C%20because%20Azure%20Active%20Directory%20Connect%20will%20not%20properly%20sync%20contacts%20into%20Azure%20AD%20for%20use%20with%20Skype.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ERegardless%20of%20any%20multi-forest%20configuration%2C%20the%20forest%20hosting%20Skype%20for%20Business%20server%20can%20also%20provide%20functionality%20for%20any%20enabled%20users%20that%20exist%20in%20the%20same%20forest.%3C%2FEM%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ECall%20to%20action%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EGet%20familiar%20with%20the%20updated%20TechNet%20documentation%3C%2FLI%3E%0A%3CLI%3EIf%20you%20are%20in%20complex%20forest%20scenario%20and%20were%20blocked%20from%20Skype%20for%20Business%20Hybrid%2C%20reevaluate%20your%20situation%20based%20on%20the%20updated%20documentation%3C%2FLI%3E%0A%3CLI%3EAny%20questions%20or%20feedback%3F%20Discuss%20with%20us%20in%20our%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fsofcommunity%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ECommunity%3C%2FA%3E.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-56966%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPlan%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EReadiness%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20Academy%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125451%22%20slang%3D%22en-US%22%3ERe%3A%20Planning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125451%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3BNadir%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyes%20Thomas%20is%20correct..%20your%20scenario%20is%20covered%20in%20the%20text%20he%20has%20repasted%20-%20this%20is%20the%20issue%20why%20I%20asked%20about%20lcssync.dll%20as%20this%20is%20how%20this%26nbsp%3B%3CSPAN%3Emetaverse%20rules%20extension%20dll%20works%20(it%20creates%26nbsp%3Bcontact%20objects)%20and%20I%20guess%20you%20are%20using%20that.%20Without%20the%20source%20code%20you%20would%20need%20to%20rewrite%20a%20new%20DLL.%20After%20more%20testing%20I%20found%20that%20actually%20you%20can%20modify%20the%20rules%20in%20AADConnect%20so%20it%26nbsp%3Bcan%20pick%20up%20and%20project%20Lync%20user%20contact%20objects%20as%20well%20-%20problem%20is%20that%20it%20probably%20isn't%20a%20good%20idea%20to%20start%20messing%20with%26nbsp%3Bthe%20rules%20in%20AADC%20even%20though%20MS%20do%20give%20you%20access%20(via%20the%20Synchronisation%20Rules%20Editor).%20Writing%20a%20new%20DLL%20from%20scratch%20needs%26nbsp%3BMicrosoft%20Visual%20Basic%26nbsp%3B.NET%20or%20C%23%20skills%20so%20not%20a%20simple%20task.%20Hopefully%20when%20everyone%20moves%20to%26nbsp%3BTeams%20this%20complexity%20will%20all%20go%20away!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112842%22%20slang%3D%22en-US%22%3ERe%3A%20Planning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112842%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F47644%22%20target%3D%22_blank%22%3E%40NADIR%20KHAN%3C%2FA%3E%2C%20isn't%20this%20covered%20here%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EWhen%20Skype%20for%20Business%20Server%20is%20deployed%20in%20one%20forest%20(a%20resource%20forest)%20but%20provides%20functionality%20to%20users%20in%20one%20or%20more%20other%20forests%20(account%20forests)%2C%20users%20in%20other%20forests%20must%20be%20represented%20as%20disabled%20user%20objects%20in%20the%20forest%20where%20Skype%20for%20Business%20Server%20is%20deployed.%20An%20identity%20management%20product%2C%20such%20as%20Microsoft%20Identity%20Manager%2C%20needs%20to%20be%20deployed%20and%20configured%20to%20provision%20and%20synchronize%20the%20users%20from%20the%20account%20forests%20into%20the%20forest%20where%20Skype%20for%20Business%20Server%20is%20deployed.%20Users%20must%20be%20synchronized%20into%20the%20forest%20hosting%20Skype%20for%20Business%20server%20as%20disabled%20user%20objects.%20They%20cannot%20be%20synchronized%20as%20Active%20Directory%20contact%20objects%2C%20because%20Azure%20Active%20Directory%20Connect%20will%20not%20properly%20sync%20contacts%20into%20Azure%20AD%20for%20use%20with%20Skype.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ERegardless%20of%20any%20multi-forest%20configuration%2C%20the%20forest%20hosting%20Skype%20for%20Business%20server%20can%20also%20provide%20functionality%20for%20any%20enabled%20users%20that%20exist%20in%20the%20same%20forest.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109191%22%20slang%3D%22en-US%22%3ERe%3A%20Planning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109191%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Thomas%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20good%20work%2C%20Thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20are%20using%20FIM%20to%20sync%20users%20object%20from%20user%20forest%20to%20resource%20foest%20(where%20Lync%20server%202013%20is%20deployed)%20as%20Contact%20object.%20is%20there%20still%20limitation%20with%20Azure%20AD%20connect%26nbsp%3Bto%20Sync%20Contact%20object%20form%20resource%20forest%20to%20Azure%20AD%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58125%22%20slang%3D%22en-US%22%3ERe%3A%20Planning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58125%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Anthony%2C%20unfortunately%20the%20Resource%20Kit%20is%20provided%20as%20is.%20While%20I%20will%20try%20to%20find%20out%20if%20there%20are%20any%20changes%20planned%2C%20we%20would%20expect%20customers%20with%20such%20complex%20environments%20to%20have%20the%20skills%20required%20to%20create%20the%20rules%20themselves.%3C%2FP%3E%0A%3CP%3Ehth%2Cthomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57368%22%20slang%3D%22en-US%22%3ERe%3A%20Planning%20Multi-Forest%20Environments%20for%20Hybrid%20Skype%20for%20Business%20deployments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57368%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Thomas%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20this%20useful%20summary.%20The%20main%20issue%20here%20is%20that%20the%20tool%20for%20synchronising%20contacts%20for%20hybrid%20is%20contained%20within%20the%20'Skype%20for%20Business%202105%20Resource%20Kit%20Tools'%20download.%20The%20tool%2C%20LCSSync%20provides%20a%20metaverse%20rules%20extension%20DLL%20called%20'lcssync.dll'.%20This%20contains%20provisioning%20rules%20for%20copying%20users%20from%20the%20user%20forest%20into%20the%20resource%20forest%20but%20they%20are%20provisioned%26nbsp%3Bas%20Contacts%2C%20not%20disabled%20user%20objects.%20Is%20there%20any%20plans%20based%20on%20the%20information%20above%20to%20now%20reissue%20this%20DLL%20(or%20even%20just%20provide%20the%20source%20code%20so%20we%20can%20modify%20it%20ourselves)%20so%20it%20follows%20the%20advice%20given%20above%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Understanding how to establish a hybrid connection between Skype for Business on premises and online can be challenging when customers use multiple forests. The Skype for Business product group has worked hard the last couple of months to unblock additional scenarios and make the existing documentation clearer.


The authoritative documentation can be found here but we wanted to include a quick summary in this blog article:

 

  • For either a single user forest or multiple user forest deployment, there must be a single deployment of Skype for Business Server.
  • Lync Server 2010, Lync Server 2013 and Skype for Business Server 2015 are supported in this topology (please note that availability of features depends on server version you are using).
  • Exchange can be deployed on premises only, in hybrid or online only.
  • Exchange Server can be deployed in one or more forests, which may or may not include the forest containing Skype for Business Server. For details on support for and limitations with co-existence between Exchange and Skype for Business in various combinations of on-premises and online, see Feature Support in Plan to integrate Skype for Business and Exchange.
  • Exchange Server 2013 and Exchange Server 2016 are supported in this topology.
  • Cloud PBX is supported in complex forest scenarios (as long as all Cloud PBX requirements are met: https://technet.microsoft.com/en-us/library/mt455212.aspx).
  • We used to state that “central forests” were not supported. Since the definition of central forest was quite ambiguous, we replaced it with the following wording and hope to unlock additional scenarios: When Skype for Business Server is deployed in one forest (a resource forest) but provides functionality to users in one or more other forests (account forests), users in other forests must be represented as disabled user objects in the forest where Skype for Business Server is deployed. An identity management product, such as Microsoft Identity Manager, needs to be deployed and configured to provision and synchronize the users from the account forests into the forest where Skype for Business Server is deployed. Users must be synchronized into the forest hosting Skype for Business server as disabled user objects. They cannot be synchronized as Active Directory contact objects, because Azure Active Directory Connect will not properly sync contacts into Azure AD for use with Skype.
    Regardless of any multi-forest configuration, the forest hosting Skype for Business server can also provide functionality for any enabled users that exist in the same forest.

Call to action

  • Get familiar with the updated TechNet documentation
  • If you are in complex forest scenario and were blocked from Skype for Business Hybrid, reevaluate your situation based on the updated documentation
  • Any questions or feedback? Discuss with us in our Community.

 

5 Comments
Established Member

Hi Thomas,

 

thanks for this useful summary. The main issue here is that the tool for synchronising contacts for hybrid is contained within the 'Skype for Business 2105 Resource Kit Tools' download. The tool, LCSSync provides a metaverse rules extension DLL called 'lcssync.dll'. This contains provisioning rules for copying users from the user forest into the resource forest but they are provisioned as Contacts, not disabled user objects. Is there any plans based on the information above to now reissue this DLL (or even just provide the source code so we can modify it ourselves) so it follows the advice given above?

Microsoft

Hi Anthony, unfortunately the Resource Kit is provided as is. While I will try to find out if there are any changes planned, we would expect customers with such complex environments to have the skills required to create the rules themselves.

hth,thomas

New Contributor

Hi Thomas,

 

Another good work, Thanks.

 

we are using FIM to sync users object from user forest to resource foest (where Lync server 2013 is deployed) as Contact object. is there still limitation with Azure AD connect to Sync Contact object form resource forest to Azure AD?

 

Microsoft

@NADIR KHAN, isn't this covered here?

 

When Skype for Business Server is deployed in one forest (a resource forest) but provides functionality to users in one or more other forests (account forests), users in other forests must be represented as disabled user objects in the forest where Skype for Business Server is deployed. An identity management product, such as Microsoft Identity Manager, needs to be deployed and configured to provision and synchronize the users from the account forests into the forest where Skype for Business Server is deployed. Users must be synchronized into the forest hosting Skype for Business server as disabled user objects. They cannot be synchronized as Active Directory contact objects, because Azure Active Directory Connect will not properly sync contacts into Azure AD for use with Skype.
Regardless of any multi-forest configuration, the forest hosting Skype for Business server can also provide functionality for any enabled users that exist in the same forest.

Established Member

Hi Nadir,

 

yes Thomas is correct.. your scenario is covered in the text he has repasted - this is the issue why I asked about lcssync.dll as this is how this metaverse rules extension dll works (it creates contact objects) and I guess you are using that. Without the source code you would need to rewrite a new DLL. After more testing I found that actually you can modify the rules in AADConnect so it can pick up and project Lync user contact objects as well - problem is that it probably isn't a good idea to start messing with the rules in AADC even though MS do give you access (via the Synchronisation Rules Editor). Writing a new DLL from scratch needs Microsoft Visual Basic .NET or C# skills so not a simple task. Hopefully when everyone moves to Teams this complexity will all go away!