I guess once you will read through this article you will also notice how this technology is shaped out of familiar building blocks, but what I also hope for is that you will get a grasp of what is AlwaysOn, and get a basic understanding of how it works. I will fully cover installation and configuration of SQL Server AlwaysOn environment (using new and shiny SQL Server 2017) in my next article while focusing on technology overview here.
Despite I have mentioned in my previous article that setting up an integration between K2 blackpearl and SharePoint online is rather “a piece of cake” level of complexity compared to manual AAD integration set up the process, I’ve decided to write this article and describe this process from start to finish. Why? Because it is one thing to say that entire process boils down to adding K2 for SharePoint App to your SharePoint Online site through app catalog, and another thing to set this up completely from the ground up.
When it comes to SQL Server database indexes there is a wide scale of variation in depth of knowledge on this important topic among IT professionals leveraging SQL Server power while not necessarily being specialist DBA. Let’s discuss SQL server indexes a bit here with non-SQL DBAs/non-DB developers audience in mind covering why and how sides of the subject.
NIC teaming is not something we got with Windows Server 2016, but I just find it interesting to review this functionality as we have it in the current iteration of Windows Server, as usual, touching a bit on the basics and history of this feature.
In my previous blog post, I covered SharePoint 2016 installation process, my next logical step after that was to configure SharePoint app catalog so that I can add K2 for SharePoint app and as I covered this process earlier on my personal blog, I expected this to be a small task. Indeed, I had created it following steps from my old blog post in just minutes, but, alas, I run into loads of warnings while running K2 for SharePoint AppDeployment.exe. I sorted most of them but after seeing extra warnings telling me that additional configuration is required just because I’m using HTTP instead of HTTPS I decided that it is better to re-create my app catalog using HTTPS.
Recently there was an article on StarWind Blog dedicated to Exchange 2016 installation written by Nicolas Prigent, so I decided that some folks might want to get something similar for SharePoint 2016, so here you are. Disclaimer: I did not touch on scripting SharePoint installation with PowerShell or any other advanced stuff, but I promise that you’ll find some interesting details beyond of “how do I click my way through setup wizard” information.
Time to continue our conversation about that “scaled down even further” Server 2016 installation option. In my previous article, I covered general concepts around Nano Server, now I want to switch gears and talk about more practical aspects: installation and management. At the end of the day, you would agree that the best way to learn new technology it is trying to use it – this way you will be exposed to its strengths and weaknesses directly, and can get the real understanding of whether it works for you or not. Though at this point even Microsoft admits that despite all its greatness, at the moment, Nano Server has quite limited utility as it supports only a small subset of roles and features out of those which you can find in full GUI version of Windows Server.
We are in 2017 now, and it’s about fourth month since Windows Server 2016 has been RTMed in September 2016. By now, everyone probably heard about one of the big new features of Windows Server 2016 – Nano Server, new installation option which you can’t select during setup 🙂 . But I think there is still a lot of “why” and “how” questions around Nano Server. In this blog post, I will try to provide a bit of a history and compare Nano Server with other installation types.
