Microsoft has announced some more information about the Surface hub
- Orders begin July 1, 2015 click here
- Shipping ~September 2015
- Top prince 20K
https://blogs.office.com/2015/06/10/get-ready-for-surface-hub-to-transform-your-meetings/
Microsoft has announced some more information about the Surface hub
https://blogs.office.com/2015/06/10/get-ready-for-surface-hub-to-transform-your-meetings/
Requires a plugin
Now download the 6.18MB plugin (installs quickly & smoothly)
A couple things I noticed: (Below)
New IM notification in tasks
Audio Call
Emoticons!
Some things Skype for Web does not do currently:
NOTE: SQL Server 2016 CTP may/may not be supported in live environment. this is a lab scenario.
The Skype for Business Monitoring role requires installing Full SQL Server. (SQL EXPRESS will not cut it). For our lab we will use SQL Server 2016 (CTP). Put SQL CD in place and run Setup.exe.
Product Key: Next
License Terms: Next
Microsoft Update: Next (you can get past)
Setup Role = SQL Server Feature Installation
Feature Selection. Below are the SQL features we need:
Instance Configuration: (no picture)
Check “Named Instance”.
NAMED INSTANCE: MONITOR
Instance ID = MONITOR
Server Configuration: (below)
NOTE:SQL should run as system account
NOTE: No password required.
Database Engine Configuration:
Reporting Services Configuration:
Now click Install (15minute install/wait time)
When done test SQL Reporting Services by running “Reporting Services Configuration Manager” (from Start menu)
Click “Connect”
Sure enough, it is running!
Open Skype for Business Topology Builder. Drill down to your Standard Edition Front End (as shown below) then right click and Edit Properties.
Next we want to add a Monitoring role to this topology by going to General, scrolling down to and selecting “Monitoring (CDR and QoE metrics)” and then click New.
We will type input our Front End as the FQDN (as shown), select “Named Instance” and give it the name “MONITOR” (we will later install a SQL instance with this name) and click OK, Ok.
Ok | OK
Action | Topology | Publish.
Run the below PowerShell command: Install-CsDatabase –LocalDatabases (~5min on my lab)
Run the Skype for Business Deployment Wizard again and click “Deploy Monitor Reports”
The Monitoring database & SQL Server Reporting Services (SRSS) Instance should be auto filled for you
Specify credentials to access monitor SQL database. (for this lab I used domain Administrator)
x
When you click Next, the report will be deployed…
Progress…and…Completed.
Great, the reports are deployed!
You will be presented with the URL (highlighted in the picture above) or you can go to the Skype for Business Server Control Panel | Home | (Top Actions) to open the Skype for Business Monitoring Report main page.
Monitoring Reports has been successfully installed!
Skype for Business Server has 2 new reports: Conference Join Time & Media Quality Comparison. click here
For additional community reports to add to your Skype for Business Monitoring Server, take a look at the Skype for Business (Lync) Community Monitoring Reports Repository: http://bit.ly/lyncreports
Read the Entire “Skype for Business Server 2015 Step by Step” Series
Installing Skype for Business Server 2015 Standard Edition Front End
Enabling Skype for Business Server Enterprise Voice Features
Installing Skype for Business Server Monitoring Role
Lync Server 2013 to Skype for Business Server 2015 In Place Upgrade
In this step by step we will look at enabling Enterprise Voice features in Skype for Business Server 2015.
To enable our users for Ent. Voice lets open the Skype for Business Server Control Panel. Now click on Users. To save on CPU no users are shown by default so just click on Find to show all your currently enabled Skype for Business users.
Now we will see a list of Skype for Business enabled users. Note in the Telephony column that our users are enabled for “PC-to-PC only”. Let’s changed that by double clicking on a user to edit.
Now we can change a few setting
Now click “Commit”.
Now you can repeat this step for each user. (or use Powershell). Now if we give our Lync clients a few minutes a new “Phone” tab will show up inside our Skype for Business client! (NOTE: there is no need to log out or do anything on the Lync client side. This will automatically show up. Took about 5 minutes on my lab)
Alright, now our users are enabled for Enterprise Voice (EV).
If we click on the Phone Tab/Button we will see our phone dial pad. From here we can make our first “Voice” call. If we click the “Check” button Lync will call the Lync Audio Test Service. Go ahead.
Hey, it looks like EV works!
To enable the call Park feature go to Voice Features | Call Park | New
Configure a Park using the below example. In our example we are making 5 parking “slots” or spaces so we can park up to 5 calls. We could make this the amount we want to, but for this lab we’ll make it 5.
Now click “Commit”
Now we need to enable Call Park in the Voice Policy”. Go to Voice Routing | Voice Policy | Enable call park | Ok
Select Global” policy | Commit all | Ok
Now let’s call another Lync user and test our new Park feature. After we are connected, hover over “Call” then click “Transfer Call” and then “Parking Lot”
{picture of parking a call}
Once the call is Parked, you will be notified which of the “slot” the call is in. In the below case it is in #500. Anyone on Lync with Ent. Voice enabled can pick up this call Parked by dialing #500. You can click “COPY” to IM this to someone or verbally.
{picture of parked call from user that parked the call}
Some Quick notes about Call Park
Since we probably don’t want to be walking around dialing things like “tel:+18005551003;ext=1003” to reach another extension, (I suspect our users would suspect us of being insane? ;-) we need to make a Normalization rule that turns “1003” into “tel:+18005551003;ext=1003” for us automatically.
In the Lync Control Panel we’ll make this new Normalization Rule under “Dial Plan”. To do this Click “Voice Routing” | “Dial Plan” | select the “Global” dial plan | “Edit” | “Show Details” as shown below.
Now under “Associate Normalization Rules” click “New”.
Now define the New “Normalization Rule” like below.
To save this “Normalization Rule” click “OK” | “Commit” | “Commit All” | Ok | Close
Note: The normalization rule we just setup will only take care of extensions in the 1000-1999 range. In our lab exercises we’ll make sure we stay in that range, but if you to a little “exploring” just be aware.
Because of the way Lync Server is designed the changes we made above will take some time to propagate out to all the clients if we just let the process happen normally. We can “push” this process by taking the below steps on each client we want to test “right now”.
Now you should be able to dial Lync user’s by their Ent. Voice 4 digit extension number.
Unassigned Numbers allow you to play a message to a caller when they dial an unassigned number. There isn’t a Skype for Business Control Panel method to make an Unassigned Number announcment, so we’ll do that using Powershell and then finish using the SfBS Control Panel
The first thing we need to do to create a “Unassigned Number” is to create an announcement. This requires Powershell New-CsAnnouncement command. Here is an example:
New we will define the new Unassigned Number in SfBS CP. After filling the form below click OK. Then “Commit all”
http://technet.microsoft.com/en-us/library/gg398522
Quick Notes About Unassigned Number