Tag Archives: Skype for Business Server

Deploy Skype for Business Archiving and Monitoring Server


This is an extension of Step by step Skype for Business Server Standard Edition deployment, covers Archiving and Monitoring Server deployment for Standard Edition Server. This post does not cover Call Quality Dashboard.

Archiving server creates Lcslog database to store instant messaging and conferencing data while monitoring server create CDR (call details record) and QoE (quality of experience) databases. Therefore to start with the deployment process, first deploy SQL Server Standard Edition for archiving and monitoring server databases. Features which you need to select are given below:

  • Database Engine Services
  • Reporting Services – Native
  • Management Tools – Basic
    • Management Tools – Complete

Once you are done with SQL server deployment, configure SQL server. By default SQL server uses dynamic port for deployed instance, it is better to use static port.

Open Sql server configuration Manager.

 

Go to the SQL Server Network Configuration > Protocols for “Instance” > Go to the TCP/IP Properties > Select “IP Address” tab and scroll down

 

Remove TCP Dynamic Ports and assign static TCP Port such as 1433 > Apply > OK

 

Go to the SQL Server Services > Restart “SQL Server (Instance)” service.

 

You can expect below error while publishing topology or installing databases if don’t create any rules or disable windows firewall.

Either create firewall rules to open required ports and protocols or disable windows firewall. To disable Windows firewall is not a best practice for production environment. Create Inbound and Outbound firewall rules as given below:

Inbound

Allow Port 80, 443 – TCP and UDP

Allow Port 1433 – TCP

Allow Port 1434 – UDP

Enable Firewall rules which already exists.

Outbound

Allow Port 80, 443 – TCP and UDP

Turn on network discovery & file and printer sharing.

Now, you are done with SQL server configuration.

 

Go to the Skype for Business Server Standard Edition and open Topology Builder.

 

Go to the Standard Edition Server.

 

Right click on SE server and Edit Properties.

 

Select Archiving Server.

 

Click on New to add SQL Server.

 

Write SQL Server FQDN and Instance Name.


 

Now, Select Monitoring Server and drop down for SQL Server. Click OK.

 

Now Publish Topology.

 

Click on Next.

 

Select database.

 

Select database and click on Advance if you want to change database file location. In my case, I am going with default.

 

It will create databases for archiving and monitoring.

Once it is completed successfully, click on Finish.

 

Now, open Skype for Business Server 2015 Deployment Wizard. Click on Deploy Monitoring Report and follow the steps.

 

 

 

 

 

 

Once you are done with the process, you can use monitoring repots or can enable/create archiving policies based on your requirements.

Done J

Step by step Skype for Business Server Standard Edition deployment


Skype for Business Server 2015 deployment steps are as same as it was in Lync Server 2013. In this blog post, I will cover all the steps which are required to install Skype for Business Server. First, have a look on high level deployment steps which will help you to keep your infra ready for successful Skype for Business Server deployment.

1. Domain joined Windows Server 2012/2012R2 with all recent updates. Better to use Windows Server 2012 R2, latest and greatest server operating system.

2. Download and install hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2.

3. Download and Install Silverlight.

4. Install Skype for Business Server prerequisite.

5. Run setup.exe from Skype for Business Server installation media.

6. Prepare Active Directory for Skype for Business Server. If you have Lync Server 2013 infrastructure, no need to update the Active Directory as it will display you “Complete”.

7. Create required DNS records. Assign Skype for Business Server admin rights.

8. Create Share folder and assign required permissions.

9. Install Administrative tools.

10. Prepare first Standard Edition server.

11. Create and Publish topology.

12. Install or Update Skype for Business Server system.

a. Install Local Configuration Store

b. Setup or Remove Skype for Business Server Components

c. Request, Install or Assign Certificates

d. Start Services.

 

I will cover step by step installation process from step 4 onwards.

Insert or map windows server installation media and open Powershell with administrative rights.

Note: In my setup, using D: for installation media. Change drive letter in below powershell cmdlet according to your setup.

Add-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Server-Media-Foundation, BITS -Source D:\sources\sxs

 

 

 

After installation restart server.

Run setup.exe from installation media. Or you can use powershell cmdlet to run the setup.

 

As Skype for Business Server 2015 support SMART setup. Therefore you can use “Connect to the internet to check for updates” otherwise select don’t check for updates right now.

Select Installation Location for Skype for Business Server and follow the steps.

Press “Windows + F key” and search for Skype for Business Server Management Shell and Deployment Wizard.

Open SfB Management Shell or Deployment Wizard to prepare active directory.

If you are using Deployment Wizard then click on prepare schema. (Make sure current user should be member of schema admins)

If using SfB Management Shell then run Install-CsAdServerSchema

Once schema is prepared then run Get-CsAdServerSchema. If you get SCHEMA_VERSION_STATE_CIRRENT as a result, it means you are good to go.

Check Schema Version from ADSI.

Open ADSI (adsiedit.msc) > Connect to Schema > Search for CN=ms-RTC-SIP-SchemaVersion and go to properties and search for schema lower and upper range.

rangeLower    3

rangeUpper    1150

Run “Prepare Forest” from Deployment wizard or run Enable-CsAdForest from SfB Management Shell. (Make sure current user is member of Enterprise Admins)

To verify run “Get-CsAdForest” and if the result comes “LC_FORESTSETTINGS_STATE_READY” then you are good to go. You can also open Active Directory Users and Computers and find group which has been created for SfB.

Run “Prepare Domain” from Deployment wizard or run Enable-CsAdDomain from SfB Management Shell. (Make sure current user is member of Domain Admins)

To verify run “Get-CsAdDomain” and if the result comes “LC_DOMAINSETTINGS_STATE_READY” then you are good to go.

 

Once prepare active directory step is completed successfully.

  • Open Active Directory Users and Computers and make current user member of CSAdministrator
  • Open DNS and create SRV and A records

i) Create _sipinternaltls service location record.

Open DNS Manager and select domain under Forward Lookup Zones. Right click on domain or right click on right pane and select other New Records

Select “Service Location (SRV)” and click on Create Record

Service: _sipinternaltls

Protocol: _tcp

Port number: 5061

Host offering this service: FQDN of your Standard Edition Server (Ex: se02.uc.lab)

ii) Create following Host(A) records

Dailin

Meet

Admin

Sip

Lyncdiscoverinternal

  • Create Share Folder and Assign permissions

Create folder and go to the properties.

Click on Share.

Add local administrators group and assign full rights.


As well as go to the Advanced Sharing…

Add local administrators group and assign Full Control.

 

Now you are ready to start the installation of Skype for Business Server.

Open deployment wizard and click on “Install Administrative Tools”.

Once installtion is done. Press “Windows + F key” and search for Skype for Business Server. Now, you can see Skype for Business Server Topology Builder and Control Panel.

Now click on “Prepare first Standard Edition server” and follow the steps.

 

 

 

 

Press “Windows + F key”, open Skype for Business Server Topology Builder and follow the steps. Please enter the required details as per your environment.

 

 

 

 

 

 

 

 

 

I will cover Archiving and Monitoring Server installation in Part 2.

 

You can define Edge pool later in the topology.

 

Define file share which we created in previous steps.

You can define External Base URL for Web Services as per your requirements. (Ex: SEWeb.domain.com)

 

Right Click on “Skype for Business Server” and go to properties.

Assign “Administrative access URL” and “Central Management Store”. Click on Ok

Right Click on “Skype for Business Server” and “Publish Topology”

 

 

 

Now, it is time to install Skype for Business Server System. Click on “Install or Update Skype for Business Server System”

Click on Run “Install Local Configuration Store” and follow the steps.

 

 

 

Click on Run “Setup or Remove Skype for Business Server Components” and follow the steps.

 

 

 

Now Request and Assign Certificates. Click on Run “Request, Install or Assign Certificates” and follow the steps.

Click on Request.

 

Fill the form as needed. Click on Advanced and follow the steps.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Follow the same process for OAuth Certificate.

Once Certificates are assigned open SfB Management Shell.

Run “Start-CsPool –PoolFqdn <poolfqdn>

Type “Y”

Once, services are running open Skype for Business Control Panel and play with it. J

 

Part 2 of this article will cover Archiving and Monitoring; and Persistent Chat Server deployment.

Windows Fabric and Server Placement – Part II


Part I of this article talks about Windows Fabric basics. In part II, will describe how Lync Server 2013 and Skype for Business is tied together with Windows Fabric. Will call out few best practices which should be taken care while placing Front End Servers in virtualized environment.

In Lync Server 2013 & Skype for Business Server 2015, a pool can have maximum 12 Front End Servers. Lync Server 2013 works with Windows Fabric V1 while Skype for Business works with Windows Fabric V2/V3. As Lync Server 2013 and Skype for Business Server Front End pools uses a distributed systems model which is based on Windows Fabric. In this model, it keeps important users and conference data of each user on as many as three Front End Servers in a FE Pool. With this model a least number of FE servers must be running for the pool to function. There are two loss modes where quorum loss comes in picture for a FE Pool.

Routing group level quorum loss: Every user is assigned to a particular routing group with in a FE Pool and there are three servers in one Routing group where one is a primary replica and another two are secondary replicas. When enough replica servers of a particular routing group become unavailable then it results in routing group level quorum loss.

Total number of servers in the pool Number of servers that must be running for the pool to be started the first time
2 1
3 3
4 3
5 4
6 5
7 5
8 6
9 7
10 8
11 9
12 10

 

Pool level quorum loss: Same as Windows Server Cluster, FE pool needs minimum N/2+1 to make the pool state up and running. In the odd numbers it is automatically taken care while in the even numbers Primary SQL database plays a role of witness. When minimum numbers of server in a FE Pool becomes unavailable, it results in Pool level quorum loss.

Total number of Front End Servers in the pool Number of servers that must be running for pool to be functional
2 1
3-4 Any 2
5-6 Any 3
7 Any 4
8-9 Any 4 of the first 7 servers
10-12 Any 5 of the first 9 servers

 

If organization has plan to deploy Skype for Business Server in virtualized environment, FE Servers placement is a key to make sure minimum impact on FE services in case one host goes down. If you place more than one FE Server on any particular host in virtualized environment that can surely result in routing group level quorum loss or might be result in Pool level quorum loss as well if pool has only four FE Servers and SQL primary database is part of the host which is down.

The above example consider SfB deployment with two physical hosts where each host caters two FE Server and one SQL Back End Server. If only routing group goes down then it can be recovered via Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery cmdlet. Please make sure if two FE Servers in a particular routing group go down, the users belongs to that routing group will be downgraded in limited functionality until FE Servers come back or pool registrar state has been reset.

Back End Server options: Skype for Business 2015


Back End database is a key for any two-tier or three-tier application. It might be deployed independently in the form of database server or as native database managed by application itself. Microsoft SQL server is play an important role with Microsoft UC platform either LCS/OCS or Lync/SfB. Since Lync Server 2013 onwards SQL server is loosely coupled with Back End Servers and most of the activities is used to happen on SQL express edition itself which is part of the Front End Servers. Still, Microsoft Lync Back End Server maintains copy of user persistent data, application data and Central Management Store.

Lync Server 2013 supports SQL Mirror and SQL Failover Clustering (Lync Server 2013 CU1 onwards) for Back End databases. While SQL Server AlwaysOn is not supported with Lync Server 2013.

SQL Server AlwaysOn was first introduced with SQL Server 2012. Now, Skype for Business Server supports all the options.

  • SQL Mirror
  • SQL Failover Clustering
  • SQL AlwaysOn Availability groups
  • SQL AlwaysOn Failover Cluster Instances (FCI)

One concern which always arise “Simple & Cost Effective Solution without performance compromise?” for better ROI with lower TCO. All four options use same SQL Server but edition and storage requirement make difference.

SfBBackend

Database Mirroring is a simplest method for Skype for Business Back End Server which can be easily setup by Lync Server Topology Builder. To achieve automatically failover, deploy witness server. To use Failover Clustering, AlwaysOn Availability groups and AlwaysOn Failover Cluster Instances, you first setup and configure the Back End servers high availability solution.

Planning for In-Place upgrade with Skype for Business


Many organizations might have plan to upgrade their existing Lync infrastructure and waiting for Skype for Business general availability. Skype for Business green field deployment is almost same as it was in Lync Server 2013. If you are planning for in-place upgrade of Lync Server 2013 infrastructure, you will have to consider many best practices. There are a few key recommendations which you should consider while planning for In-Place upgrade.

Before going to talk about the recommendation for in-place upgrade, would like to clear “Skype for Business In-place upgrade only supports vanilla Lync Server 2013 infrastructure”. For more details and options please go through my preceding blog post Skype for Business: In-Place Upgrade and Migration Path.

There are two options for In-Place upgrade:

  1. Migrate-users mode (No user downtime): Basically, this option is only available if organization has more than one Lync Server 2013 pool (Don’t consider paired/secondary/backup pool). With this option administrator has to move all the users from the primary registrar pool to any other Lync Server 2013 pool and upgrade the primary pool. Once FE pool and associated server roles have been upgraded then move the users back to the primary pool. Follow the same process for multiple pools.

  2. Offline mode (Downtime require): You can consider this option if the organization has only single pool or two pools in backup/paired pool configuration. This method requires downtime or you can upgrade Lync Server 2013 infrastructure in non-business hours or weekends. Please make sure entire upgrade process should be occur in one shot and till that time Lync Services will not be available to end users.

For both the options Lync Server 2013 infrastructure should be updated with Lync Server 2013 CU5 before starting the in-place upgrade process.

Below are the key recommendation while planning for in-place upgrade.

  • No in-place upgrade with pool failover option

    Don’t use failover cmdlet to failover the primary pool to backup pool and start in-place upgrade in primary pool. This method is not supported.

  • Don’t start services in mixed mode while upgrading.
  • Don’t unpair the pools before completing upgrade process in paired pool environment.
  • Ensure minimal downtime when the pools are paired with different versions.

Upgrade Order: Inside – Outside

  1. Users pools first
  2. Shared components like Mediation Server, Director etc.
  3. Edge
  4. CMS pool

Skype for Business: In-Place Upgrade and Migration Path


Skype for Business is a first release of Microsoft UC platform which supports In-place upgrade. Now, there is no need to create a new setup if you are planning to update/upgrade your Lync Server 2013 infrastructure. If you are planning to migrate/upgrade your Lync Server 2010 infrastructure to Skype for Business Server, follow the same process as we used to have for Lync Server 2013. If you are getting confuse please have a look to the below visuals for better understanding.

Coexistent:


You can coexist between Lync Server 2013 and Skype for Business Server.

 


You can coexist between Lync Server 2010 and Skype for Business Server.

 

Tri-existence:

Tri existence is not supported.

 

In-Place Upgrade:


You can do in-place upgrade from Lync Server 2013 to Skype for Business Server.

 


You cannot perform in-place upgrade directly from Lync Server 2010 to Skype for Business Server. Follow the standard migration path.

 


If you want to perform in-place upgrade from Lync Server 2010 to Skype for Business Server. First migrate Lync Server 2010 to Lync Server 2013 and then you can do in-place upgrade from Lync Server 2013 to Skype for Business Server.

 

Direct Migration:


You can select the direct migration path from Lync Server 2013 to Skype for Business Server.

Direct migration from Lync Server 2010 to Skype for Business is available but if the customer have coexist environment between OCS 2007 R2 & Lync Server 2010 then they must have to migrate everything to Lync Server 2010 and after that only migration to Skype for Business will be available.

Difference between Lync Server 2010, 2013 & Skype for Business Server


Skype for Business Server 2015 is a next major release after Lync Server 2013. There is no major architecture level change from the previous release. Skype for Business Server is coming up with many improvements and one new server role “Video Interop Server (VIS)” has been added which will work as an intermediary between third-party video teleconferencing system and Skype for Business Server infrastructure.

Below table gives you a high-level overview of difference between Lync Server 2010, Lync Server 2013 & Skype for Business Server roles.

You can collocate Persistent Chat Server role In Lync Server 2013 & Skype for Business Standard Edition. In Lync Server 2010 A/V Conferencing, Archiving & Monitoring Server roles can be deployed as a stand-alone pool or can be collocated with Front End Server. Skype for Business Server SQL Back End supports all the SQL HA options available such as Mirror, Cluster and Always-On while Lync Server 2013 doesn’t support SQL Always-On.

There are many improvements which has been done in Skype for Business, please stay tuned with me to know more about improvements in detail.

 

Skype for Business Server Roles


Skype for Business Server 2015 has all the roles which were part of the Lync Server 2013 and comes with SQL Server 2014 Express edition. The new server role “Video Interop Server” has introduced in Skype for Business Server 2015 which will act as an intermediary between Skype for Business server infrastructure and third-part video teleconferencing systems. In this article, will talk about all the server roles which are part of the Skype for Business Server 2015 and collocation of these server roles. Below is the graphical representation of server roles.

 

Standard Edition Server: Same as Lync Server 2013 Standard Edition Server, Skype for Business Standard Edition Server is basically for small deployments or can be used for branch sites. You can collocate Mediation server or deploy a stand-alone Mediation server according to your design and requirements. Even Persistent chat server also be collocated with Standard Edition Server. Same as Lync Server 2013, if you deploy archiving, monitoring or persistent chat server then you should have dedicated SQL server to deploy their databases.

Front End Server: There are no major changes in Front End Server. Front End Server is a core server role of the entire Skype for Business topology and works in similar way as it was in Lync Server 2013. You can start with minimum three FE servers and can go up to twelve FE servers in a single pool. Same as standard edition server, you can collocate Mediation server with FE pool or can deploy a stand-alone Mediation pool. There are few changes have been done in terms of Windows fabric and services/pool availability which will be written separately in another post. Same as Lync Server 2013, Skype for Business Server Front End pools are the primary store for user and conference data, each user data is replicated among three FE servers and same backed up on Back End Servers.

Back End Server: There are many options which can be used to deploy Back End Servers. Skype for Business support many options to achieve high availability of Back End databases. SQL Server 2012 with SP1 and SQL Server 2014 can be used with SQL Mirror / Failover Clustering or SQL Always-On to deploy Back End Server pool.

Mediation: Same as Lync Server 2013, Mediation server is required to implement Enterprise Voice, Call-via-work, and dial-in-conferencing features. Mediation server works as an intermediary between FE Servers and Enterprise voice setup and facilities signaling and media. In few cases Media can be bypassed but signaling always need Mediation Server component. As discussed earlier, Mediation server can be collocated with FE pool or can be deployed as a stand-alone pool.

Director: Director is still an optional server role or can be deployed as needed. You can have maximum 10 Director Servers in a single pool. Director can simplify your redirection and authentication process if you have multiple pools. It can also save your Front End servers from denial-of-service attack. This role cannot be collocated with any other server role.

Edge Server: Edge Server is require to allow Skype for Business services to those users who are not part of the corporate network, such as users logging remotely. It also allow commination between external/federated users and corporate users. Skype for Business Edge Server works in same way as Lync 2013 Edge Server. This role cannot be collocated with any other server role.

Video Interop Server: This is a new server role which has been introduced in Skype for Business Server. VIP works as an intermediary between Skype for Business infrastructure and third-party video teleconferencing system (VTC) solutions such as Cisco/Tandberg VTC solutions. This is an independent server role cannot be collocated with any other server roles. This role is only required if you need to integrate third party video teleconferencing systems with Skype for Business Server.

Apart from all these roles, there is one more server role which is not part of the Skype for Business Server but it is required if you have to collaborate with external/federated/remote users. Reverse Proxy server is required to share web content such as meeting url etc. The existing reverse proxy server can be used if exist in the environment.

Hardware and Software requirements for Skype for Business Server 2015


Skype for Business server 2015 has almost same Hardware and Software requirements as we had for Lync Server 2013. Skype for Business Server 2015 supports in-place upgrade from Lync Server 2013 because of same H/W profile. This article will provide you all the requirements which is useful for planning to deploy Skype for Business server 2015 in green field environment or brown field environment.

Hardware and software requirements for Skype for Business Server 2015:

Components Standard Edition Server Front End Server Back End Server Persistent Chat Server
CPU 64 bit, 2.26 GHz dual processor with 6 cores each or higher 64 bit, 2.26 GHz dual processor with 6 cores each or higher 64 bit, 2.26 GHz dual processor with 6 cores each or higher 64 bit, 2.26 GHz dual processor with 6 cores each or higher
Memory 32 GB 32 GB 32 GB 32 GB
Disk 2 x 10K RPM disks in RAID1 for OS
6 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
6 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
6 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
6 x 10K RPM disks in RAID 10 for Data
Network 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together
Operating System Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2 Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2 Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2 Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2
Common Prerequisite Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Additional Prerequisite Internet Information Services (IIS)
Windows Media Format Runtime
.NET Framework 3.5

Silverlight

Internet Information Services (IIS)
Windows Media Format Runtime
.NET Framework 3.5

Silverlight

Message Queuing
Components Mediation Server Video Interop Server Directors Edge Server
CPU 64 bit, 2.26 GHz dual processor with 4 cores each or higher 64 bit, 2.26 GHz dual processor with 4 cores each or higher 64 bit, 2.26 GHz dual processor with 4 cores each or higher 64 bit, 2.26 GHz dual processor with 4 cores each or higher
Memory 16 GB 16 GB 16 GB 16 GB
Disk 2 x 10K RPM disks in RAID1 for OS
2 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
2 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
2 x 10K RPM disks in RAID 10 for Data
2 x 10K RPM disks in RAID1 for OS
2 x 10K RPM disks in RAID 10 for Data
Network 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together 1 x dual port GbE NIC teamed together or 2 x single/dual port GbE teamed together
Operating System Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2
Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2 Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2 Windows Server 2012/2012R2 with latest service pack & updates + hotfix KB article 2858668 for windows server 2012 and KB article 2982006 for windows server 2012 R2
Common Prerequisite Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Windows PowerShell 3.0
Microsoft .NET Framework 4.5 with HTTP Activation
Windows Identity Foundation

Remote Server Administration Tools

Additional Prerequisite Internet Information Services (IIS)

You can use below scripts to install additional prerequisites:

Standard Edition / Front End Servers: Add-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Server-Media-Foundation, BITS -Source D:\sources\sxs

Directors: Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client D:\Sources\SxS\

Mediation Server: Add-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, NET-WCF-HTTP-Activation45, Web-Asp-Net45 -Source D:\sources\sxs

Persistent Chat Server: Add-WindowsFeature Net-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, NET-WCF-HTTP-Activation45, Web-Asp-Net45, MSMQ –Source D:\Sources\SxS\

Edge Server: Add-WindowsFeature NET-Framework-Core, Windows-Identity-Foundation, NET-WCF-HTTP-Activation45, Web-Asp-Net45 -Source D:\sources\sxs

What’s new coming up with Skype for Business Server 2015?


I am pleased to write my first blog post on Skype for Business Server 2015. My preceding blog post talks about “Skype for Business” branding. Yes, once again Microsoft has changed the branding of its communication platform and the newer or upcoming version of Microsoft communication platform is “Skype for Business Server 2015” with the countless market value of Skype. Skype for Business Server 2015 will come up with all existing features of Lync Server 2013 with improvements.

If I think about this release and exclusive things which are coming up with Skype for Business Server 2015 then surely In-Place grade is one of them. Let’s talk about key enhancements in series.

1. Now, you can in-place upgrade your Lync Server 2013 infrastructure to Skype for Business Server 2015. In-Place upgrade directly from Lync Server 2010 is not supported.

2. Enhancement with Windows Fabric which will result in better high availability of FE pool and eliminate some known Lync Server 2013 issues.

3. SQL Always on is supported but restricted to single site or network subnet.

4. Now “Cold Start” of FE pools are also supported with new cmdlet Start-Cspool.

5. Server side conversations history is now available which will improve experience on mobile devices.

6. New Smart setup feature which is part of the setup program and will detect & download the updates at the time of installation.

Many more enhancements in terms of user experience, multi factor authentication, centralized logging, patching process, mobile device experience, call data collection and analysis, call via work etc.

Now it is time to introduce new Skype for Business Server 2015 role. Yes, there is a new stand-alone server role which will provide the interoperability between SfB Server and Cisco video teleconferencing (VTC) systems.

Video Interop Server (VIS)

The VIS acts as an intermediary between SfB and VTC, allow users to select Cisco VTC system.

Please stay tuned for more…