Step- by- step Guide Enabling Split- domain within Office 3. Lync Online. In my previous post I walked through the process of registering a Lync Phone Edition handset directly with Lync Online, I also promised I’d re- visit this and provide a similar walk through for a split domain configuration. Introduction to “Split- domain”Prior to the Wave 1. Office 3. 65 the only option for Lync split tenancy would be the process of deploying Lync on- premises and Federating with Lync Online, there was/is a drawback with the approach. Namely your on- prem Lync accounts are utilising a SIP namespace that is say fabrikam. Split domain support within the Lync 2. Edge Server (and respectively Lync Online 2.

Lync Online share the same SIP namespace (see illustration below) This illustrates a Lync Online user hosted within Office 3. Internet) and an on- premises homed user registering either via the Internet (over the Lync 2. Edge) or internally via the Lync Front End (Microsoft support either Lync 2. Front End Servers, but the Edge can be must be 2. Correction: Lync 2. Lync 2. 01. 0 Edge Servers are supported, for 2.

While my outlook was not working, I clicked “Send to E-mail” on a Office Communicator conversation window. After 2 days, I repaired my outlook by running scanpst. Before you install any Microsoft Office 2013 product, verify that your computer meets or exceeds the minimum system requirements for the product. Microsoft word 2007 download free full version, Microsoft Office 2007, Microsoft Office Word 2007 12.0.6504.5000, Word To Go - Document Writer for Microsoft Office. Health insurance giant Anthem Inc.

Dial-in Conferencing is a new audio option for audio conferences that are hosted on Office Communications Server 2007 R2. The dial-in option provides a cost-efficient. Force the Communicator 2007 R2 Address Book to instantly update on both x86 and x64 machines. Hi David, This functionality has recently been deprecated by Microsoft, for more information on this see here – Adam.

Edge the February CU must be applied and Lync 2. In both instances the users share the contoso. SIP namespace. Split- domain Deployment Microsoft’s Tech.

Net documentation is obviously always a good place to start, but I decided that there would be value in adding some more detail to the process. Also at time of writing there are some minor typos within the Power.

Shell commands – I’ve informed Microsoft that this needs updating. First up you need to configure your Office 3. ADFS, I won’t cover this process here but there are some great guides/blog posts on this from other MVPs (one I’d recommend from Tim Harrington here). I will however say that this process has become a lot more streamlined within Windows Server 2.

I’d recommend (where possible) the deployment of both the ADFS (a service that can be added via 2. Server Manager) and Windows Azure Active Directory Sync Tool (often referred to as “Dir. Sync”) on this platform versus Windows Server 2.

Also not that the appropriate Office 3. ADFS, at time of writing Lync Plan 3 incorporates this capability (alternatively you can purchase an E3 which also includes Lync Plan 3). One last note, if your tenancy has not been upgraded to Wave 1. Once your domain is authorised for use with Office 3. ADFS is configured you can start the split- domain configuration. Step 1. Enable Federation within your Office 3.

Within Lync Administration, Organisation and External Communications. Now is also a good time to activate/license the users you wish to move into Lync Online. Step 2. Configure your Lync 2.

Edge Server for Federation, the following cmdlet should be executed via you Front End: (if not already enabled which may be the case is Remote Worker/Federation is already deployed)Set- Cs. Access. Edge. Configuration - Use. Dns. Srv. Routing - Allow. Outside. Users 1 - Allow.

Federated. Users 1 - Enable. Partner. Discovery 1. Step 3. Federate with Office 3. Lync Online configured as an existing hosting provider run the following cmdlet: Set- Cs. Hosting. Provider - Identity Lync.

Online - Enabled. Shared. Address. Space $true - Hosts.

OCSUsers $true - Verification. Level Use. Source.

Verification - Autodiscover. Url https: //webdir. Autodiscover/Autodiscover. Service. svc/root.

If Lync Online is not configured as an existing hosting provider run this cmdlet instead: New- CSHosting. Provider - Identity Lync.

Online - Proxy. Fqdn “sipfed. Enabled $true - Enabled. Shared. Address. Space $true - Hosts. OCSUsers $true - Verification. Level Use. Source. Verification - Is. Local $false - Autodiscover.

Url https: //webdir. Autodiscover/Autodiscover. Service. svc/root. This is effectively where the magic happens, note the new “Enable.

Shared. Address. Space” switch this is utilised specifically for split- domain capability within Office 3. Step 4. Enable your Office 3.

I can’t provide any magic Power. Shell. Alas at time of writing this means a calling into Office 3. Note: Once this is complete Lync- to- Phone is no longer available, this is a shame in my opinion and I hope to see this change. Step 5. Move your “chosen” Lync users into Lync Online, once your tenancy is enabled you can complete your mission and move users. To make this happen you’ll need to enable Power.

Shell connectivity for Office 3. Microsoft Online Services Sign- In Assistant (Download: here) – in my case I installed this on my Lync Front End.

Next input your Office 3. Lync Server Management Shell$creds=Get- Credential. Before you can move your chosen user you’ll need to locate your hosted migration service URL, this can be achieved by logging into the Office 3. Lync Administration Center. Within the address bar you’ll notice your admin URL (see mine below)This URL should be appended with: /Hosted. Migration/hostedmigrationservice.

The resulting URL would therefore in my case be: https: //admin. Hosted. Migration/hostedmigrationservice. Adobe Acrobat Setup Has Detected A Non. So to move your user the complete command would be: (substituting the SIP URI for the on- premises Lync user you would wish to move)Move- Cs. User - Identity < sipuri@fqdn.

Target sipfed. online. Credential $creds - Hosted. Migration. Override. Url https: //admin.

Hosted. Migration/hostedmigrationservice. To verify the move was successful, run the following cmdlet: Get- Cs. User - Identity sipuri@fqdn. The hosting provider should be as follows: The other (and more gratifying) way of validating a successful move would be via the Lync Online Administration Center. Once you’ve successfully registered your Lync client with Office 3.

Lync Phone Edition handset. In my next article I’ll focus on Hybrid Exchange and Lync Phone Edition – stay tuned!

Microsoft Windows is a registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with windows.