Prerequisite not satisfied: Before you install Skype for Business Server 2015, you must install an update for Windows Server 2012 R2.

Prerequisite not satisfied: Before you install Skype for Business Server 2015, you must install an update for Windows Server 2012 R2.

When rolling out a Skype for Business 2015 Front End, I ran into the following issue after running the Deployment Wizard Step 2;

Skype for Business Deployment Wizard Error

Prerequisite not satisfied: Before you install Skype for Business Server 2015, you must install an update for Windows Server 2012 R2.  For details about the update, see Microsoft Knowledge Base article 2982006, “IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2” at http://go.microsoft.com/fwlink/?LinkId=519376.

At closer investigation of the Deployment Wizard I could see that KB2982006 is missing from the Windows 2012 R2 OS

The operating system was completely up to date with all latest Microsoft Updates, so in this case I used my trusted steed “PowerShell” to check if all the required windows updates where applied for KB2982006


Get-Hotfix KB2919442,KB2919355,KB2982006

This PowerShell command checks for the required KBs as well as the missing KB2982006

The resolution for installing KB2982006 is a simple one but you are required to use Deployment Image Servicing and Management otherwise known as DISM to install the KB

Resolution Steps

Download the KB to a location on your Server, for this Ill be using a temporary folder on the C: Drive called Patch. PLEASE NOTE: The folder must exist before running the below command.

Launch the Windows PowerShell console.

Type the following command;
expand -F:* C:\Patch\Windows8.1-KB2982006-x64.msu C:\Patch\KB2982006

Now type the following command;
dism.exe /Online /Add-Package /PackagePath:C:\Patch\KB2982006\Windows8.1-KB2982006-x64.cab

If you rerun Get-Hotfix KB2919442,KB2919355,KB2982006 you should now see the KB2982006 hotfix installed.

You will now be able to successfully complete Step 2 of the Deployment Wizard and build your Skype for Business Front End.

Regards

The Author – Blogabout.Cloud

Skype for Business Server  CU List

Skype for Business Server CU List

Being a Skype for Business SME, I also find it annoying searching the internet for the correct version number so heres my list

Skype for Business Server 2015

VersionCumulative UpdateKB Article
6.0.9319.537January 2019 (CU8)KB4464355
6.0.9319.534July 2018 (CU7)KB4340904
6.0.9319.516March 2018 (CU6 HF2)KB4086059
6.0.9319.514January 2018 (CU6 HF1)KB4074701
6.0.9319.510December 2017 (CU6)KB4036312
6.0.9319.281May 2017 (CU5)KB4012621
6.0.9319.277February 2017 (CU4 HF1)KB3207506
6.0.9319.272November 2016 (CU4)KB3199093
6.0.9319.259June 2016 (CU3)KB3149227
6.0.9319.235March 2016 (CU2)KB3134260
6.0.9319.102November 2015 (CU1)KB3097645
6.0.9319.88Sep-15KB3098601
6.0.9319.55Jun-15KB3061059
6.0.9319.0RTMNA

Skype for Business Server 2019

VersionCumulative UpdateKB Article
 
 
Dealing with SQL AlwaysOn in Skype for Business Server 2015/2019 Powershell Style

Dealing with SQL AlwaysOn in Skype for Business Server 2015/2019 Powershell Style

Dealing with a Skype for Business deployment with SQL AlwaysOn isn’t an easy task as there are a number of different elements involved from ensuring your databases are in the correct configuration to security permissions across the nodes.

I did originally create the following script while doing a customer deployment and have improved/modified to ensure I take out most of the headaches involved when deploying your backend databases.

The script runs through the following actions;

  • Check if SQL Instance
  • Check if Failover Clustering Role in configured on the two SQL servers
  • Ask to configure Failover Clustering Role (If required)
  • Convert and backup all Skype for Business Databases
  • Detect Skype for Business Folder on source SQL Server and copy to secondary
  • Configure SQL Server Service for AlwaysOn
    • Repeat task manually on the secondary server

Complete your AlwaysOn Configuration using the SQL Management Studio

Download

Set-SfBSQLDatabases (597 downloads)

Change Log

Version 1.1 – Features

  • Support Skype for Business 2019
  • Support for SQL Server 2014 Enterprise, SQL Server 2016 Enterprise

Video

Reporting Issues

If you identity any issues within running the script please email theauthor@blogabout.cloud

Regards
The Author – Blogabout.Cloud

QuickTips: Install-CsDatabase failed

QuickTips: Install-CsDatabase failed

Deploying Skype for Business and ran into the following error? Well here’s a quick tip to resolve the error.

Error(s)

Install-CsDatabase failed.

System.Management.Automation.CmdletInvocationException: Command execution failed: Requested registry access is not allowed.

Resolution(s)

Remove-CsConfigurationStoreLocation to ensure no corrupt legacy information

Run Skype for Business Topology Builder as Administrator

Once this command has been executed, you will be able to successfully publish the Skype for Business Topology.

Regards

The Author – Blogabout.Cloud

QuickTips: Get-CsManagementStoreLocation did not return a valid connection

QuickTips: Get-CsManagementStoreLocation did not return a valid connection

Deploying Skype for Business and ran into the following error? Well here’s a quick tip to resolve the error.

Error(s)

Topology Builder encountered an issue and cannot publish this topology.

Topology Builder has encountered an unexpected error from Skype for Business Server 2019 Management Shell.

Error Details:

Get-CsManagementStoreLocation did not return a valid connection.

Resolution(s)

Remove-CsConfigurationStoreLocation

Once this command has been executed, you will be able to successfully publish the Skype for Business Topology.

Regards

The Author – Blogabout.Cloud

Collect Skype for Business Online call data with ease – Powershell

Collect Skype for Business Online call data with ease – Powershell

Collecting Skype for Business Online call data has now got a little bit more easier with Get-SFBOCallData.ps1. This script is designed to leverage the cxdcalldata module created by Jason Slane at Microsoft, for information about the please visit the below link.

https://www.powershellgallery.com/packages/CxdCallData/1.2.4.2

The script

Check if cxdcalldata module exists on the client machine

  • Install module, if it doesnt exist
  • If exist, update with latest version located online

Specify report Start and End date

  • Specify Start Date

Specify report Start and End date

  • Specify Start Date

MFA or Not MFA that is the question

If option 2 is selected, there are less steps

  • Prompt for Skype for Business Online Admin details
  • Report is generated and placed on Desktop

If option 1 is selected, there are a lot more steps due to MFA being enabled.

  • Check Skype for Business Online Connector is installed
    • If not, Connector will be downloaded and installed
  • Prompt for User Principal Name of Skype for Business Online Admin Account
  • Provide your password details

  • Authenticate to MFA
    • This will create the MFA session to Skype for Business Online

  • New-CsOnlineSession will be created and all cmdlets will be imported

  • You will be prompted for your Skype for Business Admin Account again, this is a requirement of the powershell module.

  • Reports will now be generated and placed on your desktop

This concludes the process to require the following reports

  1. All Audio Calls
  2. Client Versions
  3. Federated Communications
  4. Federated Communications Summary
  5. User Devices
  6. User Summary

Download Script

Get-SfBOCallData (78 downloads)

Regards,

The Author – Blogabout.Cloud

Configuring Pexip with Office 365 for Scheduling Meetings

Configuring Pexip with Office 365 for Scheduling Meetings

In this article we will look at steps required for configuring your Pexip deployment with Office 365 mailboxes for scheduling meetings. The following process will be step by step using Powershell to complete the configuration of Office 365 with Pexip and at the end of this article will be a complete powershell which will allow quick provisioning with prompts for information.

Please note: The follow steps have been taken from the Pexip website, I have used their article to create an easy to use PowerShell for O365/Exchange Deployments.

Connecting to Office 365


1
2
3
4
5
6
Set-ExecutionPolicy RemoteSigned
$Credential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri <a href="https://outlook.office365.com/powershell-liveid/">https://outlook.office365.com/powershell-liveid/</a> -Credential $Cred -Authentication Basic -AllowRedirection
Import-PSSession $Session
Import-Module MsOnline
Connect-MsolService -Credential $Credential

Creating the service account

The first command lets the administrator type in a password for the service account as a secure string. This password variable is then used in the second command to create a mailbox for the service account. The third command ensures the password of the service account will not expire. The final command terminates the remote session.

For example:


1
2
3
New-Mailbox -Name "Service Account" -MicrosoftOnlineServicesID pexip@pexip.no -Password $password -Alias pexip -FirstName Service -LastName Account -DisplayName "Service Account"

Set-MsolUser -UserPrincipalName pexip@pexip.no -PasswordNeverExpires $true

Configuring Application Impersonation on the service account

The service account must be configured with a Role of Application Impersonation. This allows the service account to impersonate all users who will be using VMR Scheduling for Exchange, and to impersonate the equipment resource that is to be used for the scheduling service.

To check if your service account has Application Impersonation already configured, use the PowerShell command:


1
Get-ManagementRoleAssignment -RoleAssignee "&lt;email_of_service_account&gt;" -Role ApplicationImpersonation | Format-List

Below is an example of the output of the command when the service account already has Application Impersonation configured:

If the service account does not have Application Impersonation configured, then the above command will not return anything at all. If this is the case, enable Application Impersonation as follows:


1
New-ManagementRoleAssignment -name:"&lt;role_name&gt;" -Role:ApplicationImpersonation -User:"&lt;email_of_service_account&gt;"

For example:


1
New-ManagementRoleAssignment -name:PexipSchedulingService -Role:ApplicationImpersonation -User:pexip@office365.com

This will enable the service account to impersonate all users in the organization.

Creating an equipment resource

The equipment resource will be added as a resource attendee to all VMR Scheduling for Exchange meetings. Users will see replies from this resource when it accepts or rejects a meeting request.

Each equipment resource can be used by only one Pexip Exchange Integration.

This command creates an equipment resource with the specified Name, Alias and Display Name. Name and Display Name should be the same, and will appear as the location of any meeting requests, and as a recipient. The Alias (also known as the mail nickname) will be used as the email address.


1
New-Mailbox -Equipment -Name "&lt;Equipment Name&gt;" -Alias "&lt;Equipment Alias&gt;" -DisplayName "&lt;Equipment Name&gt;"

For example:


1
New-Mailbox -Equipment -Name "Pexip Meeting" -Alias pexipmeeting -DisplayName "Pexip Meeting"

Configuring the equipment resource

You must configure the equipment resource to disable automatic processing for the equipment resource, so that the processing can be done by the scheduling service. You must also configure it to permit conflicts, because meetings may be scheduled at the same time by different users.

This configuration is done using the following PowerShell command:


1
Set-CalendarProcessing -Identity "&lt;email_of_equipment_resource&gt;" -AutomateProcessing None -AllowConflicts $true -BookingWindowInDays 1080 -MaximumDurationInMinutes 0 -AllowRecurringMeetings $true -EnforceSchedulingHorizon $false -ScheduleOnlyDuringWorkHours $false -ConflictPercentageAllowed 100 -MaximumConflictInstances 2147483647

To verify that the above command has configured everything correctly, use the PowerShell command:


1
Get-CalendarProcessing -Identity "&lt;email_of_equipment_resource&gt;" | Format-List

Viewing the equipment resource’s mailbox

There may be occasions, such as when troubleshooting, that you want to view the equipment resource’s mailbox or calendar. To do this, you first need to assign full access to the equipment resource’s mailbox to a delegate account, and then view the mailbox or calendar using the delegate account. (The delegate account could be the service account, or it could be, for example, an administrator’s account.)

 


	
Notes from the Field: KB298200 – The update is not applicable to your computer

Notes from the Field: KB298200 – The update is not applicable to your computer

Hello Reader,

In this “Notes from the Field” post we will look at a common Skype for Business error which you may encounter when installing a Skype for Business Front End for the first time.

As you can see from the image below we have encountered an error during the the deployment wizard when installing a Skype for Business Front End for the first time on a newly built Windows 2012 R2 Server.

After downloading KB298200 and attempting to install the required Windows Update the following error occurs;

In order to resolve this issue effectively we need to download the latest Skype for Business Server Cumulative Update. This error was resolved in Skype for Business Server cumulative update Janaury 2018. A good point of reference for all Skype for Business Server CU, head over to https://blogs.technet.microsoft.com/uclobby/2015/06/22/skype-for-business-2015-cumulative-update-list/ 

First of all, you will need to stop all Skype for Business Service and this can be done easily using the following PowerShell cmdlet:

Stop-CSWindowsService

Launch the Skype for Business Update Installer and click ‘Install Updates’

Once the installation has been completed you will be able to complete the deployment wizard process with a successful outcome.

Please Note: You will need to re-run the Skype for Business Update Installer to patch the rest of the Skype for Business services.

Regards

Author – Blogabout.Cloud