Thursday, July 30, 2015

Skype for Business Server 2015 prerequisites (pre role and with powershell script)


For any other pre Skype for Business 2015 versions, e.g. Lync Server 2013 and the different OS, please refer to the old blog article:
http://lyncuc.blogspot.de/2013/09/lync-2013-server-prerequisites-per.html


Skype for Business 2015 Server Software Prerequisites:


Since the installation of Skype for Business 2015 Server require a modern OS, only the Standard and Data Center version of Windows Server 2012 and 2012 R2 are entitled for an installation.
Both servers having the same prerequisites.
 
Recommendation for Windows Server 2008 R2 is only give for in-place upgrades.


Required HotFixes Windows Server

(please consider the KB 2858668, KB2982006 and KB2533623 for in-place upgrades and fresh installations)
 
Windows Server 2012, KB article 2858668. Download.
Windows Server 2012 R2, KB article 2982006. Download.
Windows Server 2008 R2 KB article 2533623. Download.
Not all HotFixes apply to the different rules, e.g. you only need the 2012 R2 KB2982006 on Skype for Business 2015 Server rules, where the IIS is installed, meaning like the Edge doesn't require this hotfix. 
 
 
Windows 2012/ 2012 R2

All Server Roles require:


Add-WindowsFeature RSAT-ADDS, NET-Framework-Core, NET-Framework-45-Core, NET-Framework-45-ASPNET,  Web-Net-Ext45, NET-WCF-HTTP-Activation45, Windows-Identity-Foundation, Telnet-Client -Source X:\sources\sxs

(-Source X:\sources\sxs, where X should be the drive/ or network location where your Windows Server 2012/2012R2 Server ISO/DVD is found)

The RAST is not required on EdgeServer, but you can install them without any negative impact

On all Frontend Standard and Enterprise Server:

  •   SilverLight (optional)

Add-WindowsFeature 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, Web-Dyn-Compression, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client -Source X:\sources\sxs


 

On all Director:


Add-WindowsFeature 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, Web-Asp-Net45, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client -Source X:\sources\sxs


Video Interop Server:

No more additional prerequisites


Mediation:

No more additional prerequisites

 

Edge:

No more additional prerequisites

pChat:

We need Microsoft Message Queuing (Server and Services)
Add-WindowsFeature MSMQ-Services



 

Additional Information:

Do not install any Winsock Layered Service Providers (LSP) software, on any Front End Servers or stand-alone Mediation Servers. Installing this software could cause poor media traffic performance.
A LSP Software for example it:
Microsoft Internet Security and Acceleration (ISA) Server client software


 

Lync 2013 Survival Branch Server

 
(30.07.2015 SBA under Skype for Business 2015 are not yet available, instead we use the SBA Lync 2013)

In this section regarding the SBS (the equivalent "self-build" SBA:), I assume Windows Server 2012/ 2012 R2 is used:
As written, all server role have requirements in common, therefore to realize the SBA has its Registrar, Lync Frontend Service, the same overall requirements are valid too:

All Server Roles require:

  •  Windows PowerShell 3.0 (is installed by default)
  •  Microsoft .NET Framework 4.5 (http://go.microsoft.com/fwlink/p/?LinkId=268529) Additional Step's after Installation: Select WCF Activation if it isn’t already selected. Then select HTTP Activation, or include in PowerShell
    Add-WindowsFeature NET-WCF-HTTP-Activation45, Web-Asp-Net45
  •  Windows Identity Foundation 3.5 (activate via Server Manager)
    or add via PowerShell
    Add-WindowsFeature
    Windows-Identity-Foundation
Principally said, it is another Server where you can use the first Windows Feature command line at the top of this article.


Wednesday, July 8, 2015

DID (Direct Inward Dial), Pilot Numbers and Extentions in Skype for Business Enterprise Voice

Pilot Number = single phone number, e.g. caught by a hunt-group
A pilot number is the address, extension, or location of the hunt group inside the PBX or IP PBX. It’s generally a blank extension number or one extension number from a hunt group of extension numbers that doesn't have a person or telephone associated with it. For example, you might configure a hunt group on a PBX or IP PBX to contain extension numbers 4100, 4101, 4102, 4103, 4104, and 4105. The pilot number for the hunt group is configured as extension 4100. When a call is received on extension number 4100, the PBX or IP PBX looks for the next available extension number to determine where to deliver the call. In this example, the PBX or IP PBX will use its programmed search algorithm to look at extension numbers 4101, 4102, 4103, 4104, and 4105.

PILOT NUMBER: e.g +49 89 1234 0
Next we talk about the DID/DDI, this is the range assigned to the callee.


DID or DDI = Direct Inward Dialing number
The telco configures how many digits of the telephone number dialled by the caller is sent down to your PBX. Some connections, PRI or BRI, send all digits and some only the part that distincts the number from others, like the four last digits.
Any PSTN subscriber can contact an enterprise user inside or outside the corporate firewall by dialing a Direct Inward Dialing (DID) number associated with that enterprise user.
Direct Inward Dialing is used when your PBX telco connection allows direct dialling to extensions within a PBX, using physical lines (or channels on a PRI) on a shared basis.
So DID ("direct inward dialing") was invented as a way to re-use a limited number of physical phone lines to handle calls to different published numbers. In a business with DID, the phone company uses DID signalling to identify the number they are about to connect to the business's PBX. Historically, this was done by pulsing the last 3 or 4 digits of the number being dialed before connecting the number. The PBX would use these DID digits to switch the call to the right recipient.

PILOT NUMBER: e.g +49 89 1234 0
with a range of 1234-0000 until 1234-9999 possible.
A caller can now DIRECTLY dial to a target user, e.g +49 89 1234 1111


Extension = numbers extension behind the central number
Not like a phone number (like DID), more like an internal identifiy....
also used for internal dialing and AutoAttendants (e.g. Exchange AA)

If we work with extensions, we need for callees an INTERNAL number. The internal number in Skype for Business/ Lync should be in E.164 from, but can be also a shorter number, even a extension.
In PBX, the Auto Attendant can receive an external call, and proxy this call to the internal extension.

Important is, not to be confused with DIAL PLAN and EXTENSIONs!

If we have our Skype for Business real work scenario:
Exchange and Skype for Business is required. Exchange handles the Auto Attendant and will be used for the INTERNAL EXTENSION. Therefore the user needs to be UM enabled. Only than a external Pilotnumber can be assigned to Exchange Auto Attendant and the user can be called from external without a DID.

Difference between, EURO ISDN and NA ISDN
;ext=123 (EU)
x123 (NA)


E.164 maximum length is 15-digits


Recommended link for Lync normaizations between EU and NA formats and how to handle the AD assigend phonnumbers (not the Lync assigned! ones)
http://ucken.blogspot.de/2013/05/viewing-extensions-in-lync-client.html

Tuesday, July 7, 2015

Skype for Business Mobile Client, feature set of Skype for Business for Windows Phone

Finally, this morning it was the day where I had the biggest smile.
The new Skype for Business Mobile Client was released. Amazingly the updates installed over night without actively doing anything.

The naming is not the mobile client, it is:
Skype for Business for Windows Phone, or iPhone and so on.

For me this is a good sign looking forward for all changes coming along with Skype for Business Server. What we can see is the focus on Enterprise Voice, Voice in unified Communication is essential and we need straight forward and simple to use user experiences. we need to have a client which works seamless with the desktop version and features.

Let me introduce you to some new feature in Skype for Business Mobile Client:

First look when the desktop tile is on the main screen:

Form here you can click your tile and will start the new welcome screen:
You are required to confirm the update and will proceed as normal.

Well on the first look it seems not to be different from the old Lync Client and only the Logo has changed.

But this would not what we expect!
First having a look into the About Page, checking the Version Number:
The Version yet is:
6.0.1430.0, called Skype for Business for Windows Phone.

Meetings:
We can see the view and join experience for meeting changed and is a little better to use and view.

 

What we need to recognize is the Call via Work (CvW) feature, but where this is hidden and what could be done here?

Next we need to have a look into the SETTINGS:
 
As we see the Call Forwarding settings have changed and can be controlled form the windows phone client / mobile client.
This is a important feature, but remember, if Call via Work is enabled for a user this configuration is greyed out!
Else, soon we operate natively in Skype for Business Enterprise Voice, the feature is helpful and makes our life more easy.
I also help making the Phone Client "quiet", by forwarding a call to another number/ user.
 
Since we need to have a Exchange Server with proper configured EWS (Exchange Web Service), we can now query the Outlook WORK HOURS! this is good for a very much controlled FORWARD configuration and helps making the systems more user friendly.


 
One new feature and finally it's there. We can use the FORWARD Option will all possible contacts, it is searching the:
- DEVICE (email and contacts)
- Skype for Business ADDRESS BOOK
 
Next look I'm looking more closer to the FORWARD CALL settings.
I can see the configured Mobile Number is in, this helps using a reliable network for phone call, since the mobile network is mostly more suitable for voice calls.
 
As said earlier, the entire Skype for Business Address Book can be searched. also the Contacts in S4B Phone Client. Here you can see the result of a Address Book and Call History test.
Michael has an account with one of our customers and he is in my conversation history, therefore he can becomes visible.
Remember same as with the Desktop Client, your CANNOT forward calls OUTSIDE your organization!
 
 
Showing the Device Contacts. I'm having all my contacts sync from 3 email accounts and here they are all! Perfect !!
 
 
Interestingly I found a good part of how we can configure the Skype for Business Mobile Policies. Especially here the Voice settings. This is not the same as the Wi-Fi required option for Voice/ Video, it is more related to the BEST USER EXPERIENCE.
If we are in an area of bad network coverage, we can set our best quality calling based on the three options:
 
VoIP always
All calls will be transmitted over the best data network choice. 1st WiFi, 2nd CELLULAR
 
VoIP over WiFi only
All call must use WiFi network, if the network isn't available outbound calls are NOT working. Inbound experience is different, here inbound calls are receive if the WiFi networks is not accessible via Cellular / phone, it will also change the call forwarding settings to simultaneous ringing to your mobile number.
 
Cellular
All voice call must use the normal cellular network, you mobile plan. this feature activates the call forward to simultaneously ringing to your mobile phone.
 
Some might now ask, I thing we had something similar with Lync. No we hadn't, because this feature now exactly controls the behavior. Therefore e.g. your do not receive a Skype call and a cellular call at the same time on your mobile anymore!
 
 
 

Btw the starting behavior hasn't changed and the client is still slow!

Friday, July 3, 2015

MVP's explain: Upgrade Lync to Skype for Business and Exchange in WebCast

KEMP & Fujitsu @ Allgeier Webcast Windows Server 2003 Migration präsentiert von Skype for Business MVP Thomas Poett und Exchange MVP Siegfried Jagott

 

Please ask questions in regards either to my corporate email, the contact form on my blog or simply post a question here.