Monday, April 18, 2016

Skype for Business Online to On-Premise Migration

In this Blog we will see how to migrate Skype for Business Online to Lync / Skype for Business On-Premise.

Current situation 

Customer looking to utilize current on-premise IP Telephony solution. So we have decided to have Lync Hybird solution so that Lync on-premise users can leverage existing on-premise IP telephony.

Before proceeding further you have to deploy full fledged Lync on-premise solution. Here i would think that you have already one.along with Lync environment you also needs to ahve Dir Sync server has we are setting up hybrid with O365. your current On-premise AD need to be extended to O365 Azure AD in order to synchronize password with O365.

Below are the required components in order to build Hybird.

1) On-Premise Domain services
2) Dir Sync / AD Connect
3) Complete Lync /SFB  On-Premise Environment

Below are the steps needed to specifically enable Hybrid and move users back to on-premises.

Lync On-Premise Side

Set-CSAccessEdgeConfiguration -AllowOutsideUsers 1 -AllowFederatedUsers 1 -UseDnsSrvRouting -EnablePartnerDiscovery $true

 Skype for Business Online

Download and install Skype for Business online Powershell ( https://www.microsoft.com/en-us/download/details.aspx?id=39366 )

Import Powershell Skype for Business Online.

Import-Module SkypeOnlineConnector $cred = Get-Credential $CSSession = New-CsOnlineSession -Credential $cred Import-PSSession $CSSession –AllowClobber.

Enable your tenant for Shared SIP Address Space

Set-CsTenantFederationConfiguration -SharedSipAddressSpace $True

Remove existing Lync/Skype for Business Hosting Rule

Get-CSHostingProvider -Identity <SFB Online> | Remove-CSHostingProvider

Recreate Skype for Business Online Provider with Hybrid Specific Configuration

New-CSHostingProvider -Identity SFBOnline -ProxyFqdn "sipfed.online.lync.com" -Enabled $true -EnabledSharedAddressSpace $true -HostsOCSUsers $true -VerificationLevel UseSourceVerification -IsLocal $false -AutodiscoverUrl https://webdir.online.lync.com/Autodiscover/AutodiscoverService.svc/root

Update External/Public DNS Records

Edge Names (SIP Access/Web Conference/ AV  FQDNs)
External Web Services FQDN
Dialin FQDN
Meeting FQDN
LyncDiscover FQDN
SRV _sipfederationtls._tcp.domain.com
SRV _sip._tls.domain.com


Enable Test User

Enable-CsUser -Identity <account> -SipAddress <sipaddress> -HostingProviderProxyFqdn "sipfed.online.lync.com" –verbose

Skype for Business Online Side 

Login to Skype for Business online Powershell.

Move-CsUser -Identity <UPN> -Target <FE Pool Name> -Credential $cred -HostedMigrationOverrideURL https://admin0f.online.lync.com/HostedMigration/hostedmigrationservice.svc

Hope this is help Full :)
   

Friday, April 15, 2016

Skype For Business Cloud Connector Edition Released


Current Solution

If any organization wanting to leverage the enterprise grade PBX functionality offered by Skype for Business, must deploy the on premise environment hybrid mode with O365 solution, Skype for Business Server.So that users Homed in On-Premise SFB can leverage enterprise voice capabilities.

With Current release of CCE you will not required entire Skype for Business environment for PSTN Capability.

What is Skype for Business Cloud Connector Edition ( CCE)

Skype for Business Cloud Connector Edition is a package of virtual machines for deployment within an organization's infrastructure that enables public switched telephone network (PSTN) connections with Microsoft's Cloud PBX service.

"With Cloud Connector Edition, you deploy a set of packaged VMs that contain a minimal Skype for Business Server topology -- consisting of an Edge component, Mediation component, and a Central Management Store (CMS) role. You will also install a domain controller, which is required for the internal functioning of Cloud Connector. These services are configured for hybrid with your Office 365 tenant that includes Skype for Business Online services."

Read here for More detailed information Technet Article 

To Download CCC Link to Download

Tuesday, April 5, 2016

Moving On-Premise Lync User's to O365 cloud

In this Blog we will moving users to O365 cloud.

Before actually moving user's to Office 365, Please check with users are synchronized to O365 and licenses are assigned to particular migrating users.

Step 1

Open the new Lync Management Shell session and launch the remote session. We have to add the –AllowClobber parameter so that the Lync Online module's cmdlets are able to overwrite the corresponding Lync Management Shell cmdlets:

$credential = Get-Credential
$session = New-CsOnlineSession -Credential $credential
Import-PSSession $session -AllowClobber 

Step 2

Open the O365 Lync Admin Center  by going to Service settings | Lync | Manage settings in the Lync Admin Center, and copy URL, for example, https://admin0e.online.lync.com.

Step 3

Add the following string to the URL /HostedMigration/hostedmigrationservice.svc which we have copied earlier.

https://admin0e.online.lync.com/HostedMigration/hostedmigrationservice.svc 

Step 4

The following Command will move users from Lync on-premises to Lync Online.

Move-CsUser -Identity ramesh@contoso.com –Target sipfed.online.lync.com -Credential $creds-HostedMigrationOverrideUrl https://admin0e.online.lync.com/HostedMigration/hostedmigrationservice.svc
Step 5

To check if user moved to Lync Online use the below command
Get-CsUser | fl DisplayName,HostingProvider,RegistrarPool,SipAddress command.

Saturday, April 2, 2016

Configuring Azure VM with Multiple NIC's

The below instructions below will help you create a VM with Multiple NIC in Azure.

In Order to Run the Blow Commands you have you install the Azure Poweshell follow this

https://azure.microsoft.com/en-us/documentation/articles/powershell-install-configure/


To create a VM with multiple NICs, follow the steps below:

Select a VM image from Azure VM image gallery. Note that images change frequently and are available by region.

Step 1

$image = Get-AzureVMImage -ImageName $imagename

$image = Get-AzureVMImage `
    -ImageName "a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-R2-20150726-en.us-127GB.vhd"

Step 2
Create a VM configuration.

$vm = New-AzureVMConfig -Name "Edge2nics" -InstanceSize "Large" -Image $image

Step 3
Create the default administrator login.

Add-AzureProvisioningConfig –VM $vm -Windows -AdminUserName “ramesh123” -Password “password123”

Step 4

Set the configuration of the “default” NIC

Set-AzureSubnet -SubnetNames "Subnet-2" -VM $vm

Set-AzureStaticVNetIP -IPAddress "10.0.1.74" -VM $vm

Step 5

Add additional NICs to the VM configuration.

Add-AzureNetworkInterfaceConfig -Name "Ethernet2" -SubnetName "Subnet-1" -StaticVNetIPAddress "10.0.0.14" -VM $vm

Step 6

Create the VM in your virtual network

New-AzureVM -ServiceName "easyedge02" –VNetName “Lync” –VM $vm


To Update New IP Address for Existing VM which is already with Dual NIC configured

Get-AzureVM -ServiceName Easyedge01 -Name Lyncedge1 | Set-AzureStaticVNetIP -IPAddress "10.0.0.12" | Update-AzureVM



Step by Step Skype for Business Edge Deploment

In this Post will cover Skype for Business Edge server Step by Step

Topology Builder

Logon to the Front-End server and start the Topology Builder. Instead of creating a new topology download the topology from an existing deployment and store the file on the local hard disk.

1) Expand the topology tree and click on “Edge Pools”

2) Right Click “Edge Pools” then select “New Edge Pool”



Click next to define New Edge pool.



Define the Edge Pool



Select Features, Select the features you want to deploy and click next





Select IP Options and Click on Next.



External FQDNs” For each Edge services enter the external URL of it as in the screenshot below



Enter Internal IP Address and Click Next.



Enter External IP Address and click on Next.



Click Next



Click Next.



Select Publish Topology to Publish the Topology



Click On Finish.



Now that we published the new changes to the CMS database, we need to export those configurations to a file that we will be using on the Skype For Business Edge server to install the edge role.

Start a  Skype For Business Management Shell and using the following command line export the CS-Configuration to a ZIP file

To Export Configuration file.




Configuring and Installing Edge server

In order to install the Skype for Business edge server we will have to change the Netbios name as we are not going to join the system to domain




Install the pre-requisites in edge server

Add-WindowsFeature NET-Framework-Core, Windows-Identity-Foundation, NET-WCF-HTTP-Activation45, Web-Asp-Net45



Insert Skype for Business ISO and run Setup.exe.

Accept License Agreement and click on OK.







Click on Next to install Administrative tools





Select Run Install Local Configuration Store



Select Import and import the edge configuration file by selecting browse button. and Click Next.





Click on Finish.



Click next to install the Server components.



Click on Finish




Select Internal & External Certificate Request.



Import Certificate.Click Next



Click Next




Click on Finish





Click on Assign the certificate.




Once certificate Assigned. Start services.

Hope this will be Help Full :) 

Friday, February 26, 2016

Backup and Restore Lync 2013

In this Blog we will see Different important things which we need to take backup as part if Lync infrastructure.

1) Topology

The Topology is one the most important one for any Lync installations. the Topology it as all the information like Site,Pools,Server,gateways,databases etc... With out this information we will not able to restore any thing we have to re-install gain if that information is not available.

Backing up Topology

1) Open Topology Builder

Select Download Topology from Existing deployment.



Then Click on OK and select the path where you want to Save the file.

The Above steps are to Back up the existing Topology.

Here are the below steps to Restore the topology.

1) Open the Topology Builder

2) Select Open Topology From a local file and click on ok. select the file which you have stored previously. and then click on OK.



Try Publishing the Topology. Check if topology published with errors .





 2) Configuration Information 

Configuration information is and entire back of Configuration on CMS ( Central Management Store )

a) Open Lync power shell with Administrative rights

b) Type Export-CsConfiguration –FileName "C:\Backup\LyncBackUp.zip".




C) The file will be stored in the C:\Backup location.

To restore the Back up Configuration

a) Open Lync power shell with Administrative rights

b) Type Import-CsConfiguration –FileName "C:\Backup\LyncBackUp.zip" -LocalStore

Once the Above command is successful. Open the Deployment Wizard and Click on Install or Update Lync system

Check if all are showing Green Check mark. If not run the same.

Back and Restore LIS ( Location Information Store )

1) Open the Lync Powershell with Administrative rights

2) Type the command Export-CsLisConfiguration -FileName C:\Backup\Lisbackup.bak



 3) Lisbackup file will be stored in C:\Backup folder.

Follow the Below steps to Restore the Lis

1) Open the Lync Powershell with Administrative rights

2) Type the command Import-CsLisConfiguration -FileName C:\Backup\Lisbackup.bak

3) Once it is imported type the command "Publish-CsLisConfiguration"

Backup and Restore RGS ( Response Group Service )

1) Open the Lync Powershell with Administrative rights

2) To get the RGS defined aplication server name Get-CsService -ApplicationServer

3)  Export-CsRgsConfiguration -Source ´ApplicationServer:lyncrgsapp.Contoso.com"´-FileName "C:\Backup\lyncRgs.zip"

3) It will back the RGS information ( queues, agent groups, workflows, holiday sets and business hours etc..) to C:\Backup


To Restore RGS

1) Open the Lync Powershell with Administrative rights

2) Import-CsRgsConfiguration –Destination´"ApplicationServer:lyncrgscapp.Contoso.com"´-FileName "C:\Backup\lyncRgs.zip"

3) Restart the Response Group services.



Wednesday, February 10, 2016

Different Levels of Integration between Exchange and Lync.


Lync 2013 and Exchange can be integrate several levels to provide the end user with the best experience. The integration is done both at the client and server levels. To fully integrate Lync and Exchange, there are several tasks that need to be done at the server level, using the following tools:


  •  Lync 2013 Management Shell 
  • Exchange 2013 or 2010 Management Shell 
  • Lync 2013 Control Panel 
  • Exchange 2013 Administrative Centre or the Exchange 2010 Management Console 
  • Lync 2013 OCSUmUtil tool 


 The Above tools will allow you to configure the integration between Lync 2013 and Exchange

  Depending on the Lync and Exchange versions, the integration features available will be different, and the following table highlights these differences:













As shown in the table, to have all the available Lync and Exchange integration features, you need to have both Lync 2013 and Exchange 2013.

 At a client level, the integration between the Outlook and Lync clients differs depending on the Lync and Exchange versions.

You need Lync 2013 and Exchange 2013 to be able to have the Unified Contact store etc..

There are more features that you can use when integrating Outlook with the Lyncclient, and these features are available with Lync 2013 and both Exchange 2013 and 2010.

  These features, provided by the Exchange Web Services, are the following:

  • Read or delete items in the conversation history folder in Outlook 
  •  Listen to or delete voicemail items 
  • Display extended free busy information and meeting subject and location 
  •  Read or delete Lync missed call notifications in your inbox