[PowerShell] Skype For Business Daily Configurations and Topology Change Report


The new script Compare-CsConfiguration.ps1 is now available on Technet Gallery 🙂

Compare-CsConfiguration.ps1 script will generate a daily reference file for Skype for Business server CsConfiguration, and compare it with the last day reference file.

First day you run the script, a reference file will be created, and from the next day you will get the Topology and CsConfiguration changes report.

he result is emailed to the addresses you defined in the User Variables section,   The Result also will be saved in the selected folder.

The configurations compared includes:

  • Skype for Business Server Topology.
  • Federated Partners.
  • BW Policies.
  • Access Numbers.
  • Dial Plans. ….etc.

Some Screenshots:

First day running the script, The first reference file will be prepared, and of course no comparison will happen:


Example of when there are no changes between current configurations and yesterday’s configurations:


Example when there are some changes:


The Script and some more details are available here: https://gallery.technet.microsoft.com/Skype-For-Business-Daily-b04dd3a5/

Update all of your Skype For Business Servers

DigitalBamboo's Blog


Good Morning Class, Today I just wanted to put into your hands a needed cheat sheet that puts together all of the update changes in SFB into one simple upgrade document for any set of SFB servers. So lets begin.

Pre-Requisite Install work for Skype for Business Updates

Updates should be done in the

To begin, If you have Skype for Business (SFB) Standard Edition, you will follow this process:

Standard Edition Updates for SFB Server Environment

  • 1 Stop-CsWindowsService
  • 2 net stop w3svc
  • 3 SkypeServerUpdateInstaller.exe
  • 4 Once this is complete move to step 5
  • 5 Open a new SFB Shell after closing the update window
  • 6 Stop-CsWindowsService
  • 7 net start w3svc
  • 8 Depending on your Database setup- you may…

View original post 400 more words

OAuth certificate missing

“The same OAuthTokenIssuer certificate needs to be used by all of the Lync Server 2013 servers. In order to assure this, when you assign this certificate, it is replicated via the CMS and is assigned to all of the Lync Server 2013 servers that require OAuth. ” dodeitte

Troubleshooting UC

Whilst deploying Lync Enterprise Edition with 3 Front End Servers I cam across an interesting issue. FE 1 was fine but when I fired up FE 2 and got to the certificate wizard the OAuth Certificate was missing.

One thing you will notice if there is no OAuth certificate is that the Lync Front End Service wont start. OK so where is the cert???

Found a good blog explaining the purpose of OAuth here (thanks Doug)
So fist thing was to see if the Front End Servers were replicating, and indeed they were BUT no OAuth. 

Checking the Cert Manager through MMC shows that the cert isn’t in the personal store. Adding it there manually didn’t help me much either…

Seems that it needs to be put there by the replication process.

I decided to move along (against my best judgement and the clock) and add the default cert to FE 2 and…

View original post 134 more words

[Powershell] Know your Variable Type

You can define variables in your Powershell script by various means, it’s a good idea to check if the parameter type is defined as expected,

in one of the scripts I came across, one command was failing with this error:

Cannot process argument transformation on parameter <Variable Name>. Cannot convert value to type System.String.

Displaying the parameter alone, I found it looks as an array, also I did query the variable type, and of course it was not System.String which is required by the command to complete:


the result can be one of the following, weather it’s correct or no, it depends on how you plan to use this variable in your script:

Alias Type
[int] 32-bit signed integer
[long] 64-bit signed integer
[string] Fixed length string of Unicode characters
[char] A Unicode 16-bit character
[bool] True/False value
[byte] An 8-bit unsigned integer
[double] Double-precision 64-bit floating point number
[decimal] A 128-bit decimal value
[single] Single precision 32-bit floating point number
[array] An array of values
[xml] XML objects
[hashtable] A hashtable object (similar to a dictionaryobject)

For my case, We redefined the variable so it only hold the correct single value, and hence $MyVariable.GetType().FullName returned: System.String

Supported or not Supported, this is the Question

Summary of Lync Supported and Non-Supported Configurations

Teams Dude


: thanks to Lync MVP Thomas Poett, and his input, I updated the article

how many times did you stumble upon a question from a customer if a certain feature or deployment scenario is supported by Microsoft and Lync 2013 or not.

we all forget, I mean there is a new stuff happening in our world (UC) every minute and sometime we loss tracks, so I have what I call my SCS (supported Cheat sheet) where I keep all information I have through my years in Lync by something I read or researched or learned from someone else about Lync supportabilities, and I decided to share it here in a blog article about what is supported or not supported regarding Lync 2013.

feel free please to correct my information, or put a comment about something I did not mentioned and I will be add it to this article…

View original post 909 more words

Simple Understanding of Lync Windows Fabric & Failover

Why you should deploy “3” Frontend Servers in Lync Server 2013 Enterprise pools.

Teams Dude


I saw a scary number of Lync 2013 deployments in the last 8 months where the Lync is deployed using an Enterprise pool with only two front end servers, even I saw a couple that have an Enterprise pool with only one front end server, yes you read that right, only one front end server.

So I decided to write another post of my “Simple Understanding” article series aimed to explain the Lync 2013 server architecture, how it utilize windows fabric for high availability and why you should not deploy a 2 nodes Enterprise Edition pool, I’ll try to use small words and simple explanations as I can.

I’m planning also to use this article as a guide to share with customers which have an existing Lync deployment or considering Lync to help them in their decisions.

View original post 1,514 more words

SQL Server 2012 automated Install ini Feature list

Good reference to interpret/create SQL installation ini file

Understanding SQL

Any DBA worth their salt will have automated the deployment of any version of SQL server using a SQL server configuration ini and a standard installation script. Through the ini, you can manage exactly what you required to be installed, where you want it installed and how you want your features to run.

With the introduction of SQL Server 2012, Microsoft introduced some new features that can be included in your network standard installation, so I figured it was time to update the list of features and their abbreviated name that needs to be included in the ini.

In your ini, you will have a line approximate to this:


For reference, here are the full names:




Server Engine




text Search


Quality Services




Services – Native


Services – SharePoint



View original post 75 more words