I used to spend quite some time on building and re-building Microsoft BI demo machines. As you can imagine this manual process takes a lot of time and effort. Therefore (and also for my own education on PowerShell) I decided to look into automating the whole process. I will explain this in this series of posts.
In the end, we want to have a virtual machine that is configured as follows: Windows Server 2012 R2, with Active Directory Domain Controller role. Additionally, SQL Server 2014 is installed and configured as well as SharePoint 2013. Finally, the BI tools like Power Pivot and Power View are configured.
Ok, but how do we build such a machine?
Here are the steps to take. I always do them in this order, partly because there are some dependencies and partly because it stops me from going insane.
- Install Windows (doh). I will skip this step (therefore it is number 0) since I use Azure and a VM in Azure comes with Windows Server pre-installed. I happen to use Windows Server 2012 R2 b.t.w.
- Disable Internet Explorer Enhanced Security Configuration. Although it is a great idea (see http://technet.microsoft.com/en-us/library/dd883248(v=WS.10).aspx for more info on this) it is hard to give a good demo on the machine with this thing on. So first step is disabling it.
- Set up Active Directory; AD is required for the PowerPivot service.
- After AD has been set up we need to promote the Domain Controller.
- After promotion we configure a very unrestrictive password policy; remember, this is just a demo machine!
- Virus protection is important, even for a demo machine; therefore set up System Center Endpoint Protection.
- Install SQL Server 2014.
- Install SharePoint.
- Install PowerPivot Service.
- Configure PowerPivot Service.
- Configure last parts of PowerPivot Service.
- Configure Master Data Services.
- Configure Data Quality Services.
- Configure other SharePoint Service Applications.
- Activate SharePoint site features.
- Add favorites in Internet Explorer to point to MDS and SharePoint site.
In this blog series I will share my PowerShell code to accomplish this. Please note that I am not a developer so things can probably be done a lot smarter J
Next step is preparation: the install files.