Most companies talk about Linux cloud hosting, but Microsoft-based businesses benefit from Microsoft data centers offered by Microsoft Azure. Microsoft Azure is a PaaS and laaS cloud solution for small businesses. This article describes Microsoft Azure and cloud hosting technologies.
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.
I remember having to terminate an entire Amazon EC2 instance because I somehow lost access to it via SSH. Well, looking back, termination really wasn’t necessary. Using the simple process described here, you can easily regain access to the AWS EC2 instance that you locked yourself out of.
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.
My previous article on the subject of adding a swap file to an Amazon EC2 instance focused on adding the swap file to the instance storage (also known as ephemeral storage) that comes with certain Amazon EC2 instances. This article discusses how you can still leverage the concept of swap files even on “EBS only” Amazon EC2 instances.
Amazon Web Services (AWS) makes it very easy to expand EBS volumes. You just right-click on the volume, select modify, and enter the new, larger volume size. Done. To shrink Amazon EBS volumes, however, is a whole different matter – there is no way to do this directly using the AWS console. In this article, I describe a roundabout technique that I have often used to save some bucks in scenarios where I mistakenly over-allocated Amazon EBS when setting up EC2.