Scripted Installation for SharePoint 2013 - Problems and Solutions

Just in case you trying to install SharePoint 2013 using PowerShell scripts I discovered some things that took more time to handle. Take a look at my guide if you need to install SharePoint 2013.

I know this is a Preview version so it’s likely that issues will be fixed.

SharePoint 2013 Management Shell

If you open the SharePoint 2013 Management Shell or a PowerShell console (adding the SharePoint snap ins) you will get an error:

could not create a CmdletConfiguration for CmdletName Start-BulkOperation, CmldetClass,      
CmdletHelpFile C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\

Here’s a screenshot if you use the PowerShell console and manually add the SharePoint 2013 PowerShell snap ins:

SharePoint 2013 PowerShell snapin error.

I didn’t encounter any problems so far… so it doesn’t hurt right now.

Windows Server 2012 and PowerShell Scripts

This one is getting on my nerves but it looks like it’s a security feature:

  1. I create the SharePoint Setup Administrator in AD and add him to the local admin group of each server where I will install SharePoint 2013.
  2. I right click a PowerShell script and run it with the privileges of my SharePoint Setup Administrator.
  3. I also turned User Account Control (UAC) off.

Although this account has administrator privileges I can’t e.g. access the registry and my scripts fail.

I remember this worked with Windows Server 2008…

Run PowerShell scripts without administrator privileges.

As far as I understand this is a security feature… you need to first run a console using ‘Run as administrator’ (CMD, PowerShell) and then call your scripts.

  1. So you can create a batch file calling the PowerShell script and run it as an Administrator:
    Run PowerShell scripts with administrator privileges.
  2. Or you can run a PowerShell console as administrator and call your script (but drag & drop doesn't work):
    Run a PowerShell console as administrator and call your script

It was really convenient with Windows Server 2008 and the right click on the script.

If you have a better solution please let us know.