xSharePoint is now SharePointDsc – what you need to know!

For just over 12 months now we have been working hard to grow the xSharePoint DSC module to let SharePoint 2013 and 2016 administrators use PowerShell Desired State Configuration to manage their SharePoint deployments. We’ve come a long way in the last year, and now with the help of my core team we are making an important transition – we are renaming from “xSharePoint” to “SharePointDsc”. Continue reading “xSharePoint is now SharePointDsc – what you need to know!”

Cross server DSC dependency options with Azure Resource Manager templates

One of the topics I have been discussing a little lately around the use of the DSC extension for Azure virtual machines is how to create dependencies for DSC configurations that work between servers.If you’re not familiar with how to use the DSC extension in Azure ARM templates have a read of my previous blog post on the topic. Continue reading “Cross server DSC dependency options with Azure Resource Manager templates”

Using DSC to download from Azure file storage to an Azure VM

I’ve been exploring a lot PowerShell Desired State Configuration lately, and one of the things I’ve come up against was the need to be able to move files from a file share in an Azure storage account, to the local file system of a VM (usually to install software). Now since I’ve been trying to achieve as much as possible using DSC I decided to explore whether or not I could do this through DSC – and the news was good. Continue reading “Using DSC to download from Azure file storage to an Azure VM”

Multiple zones for host named site collections in SP2013

For those who haven’t heard of host named site collections, the short version of what they are is that rather than having multiple web applications in a SharePoint farm for sites with different URLs (such as teams.contoso.com and then projects.contoso.com for example) you can have a single web application that will use the full URL to identify a site (including the host header) rather than just the path (such as “/” or “/sites/site1”). If you’re not familiar with the concept there is a good write up on TechNet that covers off all the details that I recommend you read (see: Host-named site collection architecture and deployment (SharePoint 2013)). Continue reading “Multiple zones for host named site collections in SP2013”