Part 4 of my series on setting up a SharePoint 2016 development farm in Azure. In this article, we will perform the actual SharePoint 2016 installation. This will be a virtual machine (spVM) in the virtual network we created in Part 2 of this series. We will make spVM a member of the Windows Server AD domain, and then create a new SharePoint farm.
Part 3 of my series on setting up a SharePoint 2016 development farm on Azure. In this article, we will create a SQL Server 2014 virtual machine (sqlVM) in the virtual network we created in Part 2 of this series. We will make sqlVM a member of the Windows Server AD domain, and prepare it for SharePoint.
Part 2 of my series on setting up a SharePoint 2016 development or test farm on Azure using Azure PowerShell. This article focuses on the domain controller virtual machine deployment and configuration. It includes lots of details that are re-used in the subsequent parts.
In this multi-part “tutorial”, we build a single-server SharePoint Server 2016 farm inside a subnet of a Microsoft Azure virtual network. The purpose of this server will be for development and testing and as a basis for demonstrating what’s possible in SharePoint 2016. This is the introduction article.
You might already be using PowerShell to automate other things in your environment. But if you haven’t started automating your cloud workload with Azure PowerShell, it’s time you take your cloud game to the next level. In this article, I’ll be showing you how to get started managing Azure resources with PowerShell. We’ll install the Azure PowerShell module and connect to your Azure subscription.
Cloud computing has become one of the most talked-about subjects in the world of corporate IT. However, in spite of the hype, there’s also a strong case against cloud-based services, particularly in certain situations. This article takes a look at the more problematic side of cloud computing while comparing it directly to its on-premises alternatives.