15 49.0138 8.38624 1 0 4000 1 https://vladtalkstech.com 300 1
theme-sticky-logo-alt

Create a scripted SharePoint 2013 Development Environment Tutorial – Part 3

49 Comments

Introduction

Creating a SharePoint Development Virtual Machine is something you might have to do quite a few times as a Developer. Even if it’s a pretty easy process, on a slow machine it can easily kill 4-5 hours of your day only to install SQL, SharePoint, Visual Studio and all the others tools you might need to get started. What if you could just script it so it’s all done automatically while you go take coffee, chat on SharePoint Community or whatever else you enjoy doing? In this tutorial we will learn how to build a script that we will keep using for as long as you keep developing on SharePoint 2013. The tutorial will be split in a few sections since in order to keep them focused and short, and at the end they will all be published in a downloadable PDF. I strongly encourage you to not only copy the scripts, but actually read the blog posts of why I did them like this and there are some parts where you will need to work as well!

Sections:

  1. Introduction & Prerequisites & Creating the Domain and Service Accounts
  2. Installing software prerequisites + SQL
  3. Installing SharePoint 2013
  4. Installing Visual Studio 2012 and Optional Software
  5. Basic Optimizing and Summary
  6. Advanced Optimizing of the scripts! (You are here)
  7. An eBook Guide of the 6 sections and a video! (19/11/2013)

Installing SharePoint 2013

The Installation of SharePoint 2013 will basically be done in two steps. The first step is, of course, preparing our source package and configuration, and the second step is installing it. Both those steps will be done with the help of two great tools done by Brian Lalancette. The first one is AutoSPInstaller that you can download here: https://autospinstaller.codeplex.com/ and the second one is AutoSPSourceBuilder that you can download here: https://autospsourcebuilder.codeplex.com .

First, let’s download AutoSPInstaller, and put the “SP” Folder in C:\SharePoint . Now, let’s download AutoSPSourceBuilder and extract it in C:\SharePoint Again. The folder should look something like:

SharePoint 2013 Development Environment Tutorial

Next thing you have to do is mount the SharePoint 2013 ISO file and open PowerShell as an administrator.

Run the following script (If you want to add language packs to your install you can now! Make sure to read the tools documentation if you modify stuff! Also, for this step you will need an internet connection so it can download the prerequisites! However, once we have them we won’t need them anymore for future Virtual Machines.

cd C:\SharePoint\AutoSPSourceBuilder
.\AutoSPSourceBuilder.ps1 -Destination "C:\SharePoint\SP\2013" -GetPrerequisites $true

The script will start copying the Source Files from your ISO in the right folder in C:\SharePoint , as well as downloading the pre-requisites so they are offline in the future! It will look something like this:

When Asked to enter a Cumulative Update, just press Enter, we don’t want to slipstream the updates using the old process, we will use the new “AutoSPInstaller” way!

While it runs, you can download the March 2013 PU from this link: http://download.microsoft.com/download/5/1/C/51CA768E-C79E-41BA-91D4-7F7D929B0BFE/ubersrvsp2013-kb2767999-fullfile-x64-glb.exe

And the August 2013 Cumulative Update from this link: http://hotfixv4.microsoft.com/Microsoft%20SharePoint%20Server%202013/sp1/ubersrv2013kb2817616fullfilex64glb/15.0.4535.1000/free/466901_intl_x64_zip.exe

The March 2013 CU is already an .exe file, however the August 2013 one is a zip, so you will have to extract it into the exe. After you do, copy both your executables and the .cab file into C:\SharePoint\SP\2013\Updates folder. It should look something like this :

When the AutoSPSourceBuilder finishes, it will have copied all the SharePoint 2013 Media in the C:\SharePoint\2013\SharePoint folder and all the prerequisites in C:\SharePoint\SP\2013\SharePoint\PrerequisiteInstallerFiles . Now that your media is prepared, you can actually delete the AutoSPSourceBuilder folder as we won’t be using it anymore. It will look something like this:

Now that our SharePoint Sources are ready, we can start configuring everything! Go in C:\SharePoint\SP\AutoSPInstaller and open “AutoSPInstallerInput.xml” with a notepad editor. You can also edit this file on your local machine since you probably have NotePad++ which makes modifying this document a lot easier! The Document is pretty well documented however I will go over with you with some settings we need to change. I will also show you a bit under an example of a configured AutoSPInstallerInput.xml that you can refer to incase you have any questions… so let’s start!

  1. change the “PIDKEY” value with your actual SharePoint 2013 Key :
  2. Change “OfflineInstall” to true:
  3. Change the “AutoAdminLogon” to true and enter the sp_admin password. This will make sure we aren’t prompted to reboot every time the Pre Req installer needs a reboot! :
  4. Change the “CertificateRevocationListCheck” to true. If we keep it enabled, it will slow down your VM when not connected to internet!:
  5. Enter the passphrase of the farm… Make sure it’s pretty complicated!

Tip to make configuration faster! Do a Find/Replace with Domain\ for vladdev\ (for example) and domain.com for vladdev.local (for example). This will avoid you writing in the domain every time!

From now on, I won’t tell you what to change on each line, since it’s very well documented in the XML file, however I will post you screenshots of “Sections”. The only thing I want to make sure you do is set the <DBServer> to localhost! This will make sure it will always pick the MSSQL instance!

PS: I will have deleted comments from my screenshots so I am able to show you more actual configuration on a smaller screenshot!

In the Logging Part, I changed the Path to C:\Logs\<logname> to make it easier to find them after! Won’t have to go to the long default path anymore!

For the Service Applications, the basic ones will only ask you if you want to provision or not… And some of them like “Search” And User profile will ask you for more detail! I will only show you the MMS, Search and User Profile Screnshots, use the comments in the XML to configure the rest if you need!

The SP_UserProfiles account currently does not have the necessary rights to sync users! You either have to give it the Replicating Directory Changes Permission (Click here for tutorial) OR, if you want an “easier” way… Just use the SP_Admin account! It’s already a local(domain) admin!

The rest of the Service Applications can be configured as you wish!

After you’re done configuring the file, run the AutoSPInstallerLaunch.bat file. It will launch a CMD window as well as a PowerShell one and will look something like this!

And then it will install the prerequisites, Binaries, Updates and configure everything as you told it to in the AutoSPInstallerInput.XML. Here are some screenshots of it running.

d

And when the SharePoint 2013 installation is done, it will open the Web Applications and Central Administration in the Background

Summary

This Part of the Guide has been quite complicated, however we managed to install SharePoint 2013 entirely scripted! The fun part is now that you already got your sources ready, so you won’t have to redo the “Source Preparation” ever again. Also, since it’s a development machine, the AutoSPInstallerInput.XML will probably never change between the installs, so now you got that forever as well! One thing that isn’t “cool” now is that we have to go to “C:\SharePoint\SP\AutoSPInstaller” to launch the script and not launch it from C:\SharePoint like all the other ones! So let’s create this script and put it in C:\SharePoint

#Name: installSharePoint.ps1
#Purpose: Installs SharePoint
cd C:\SharePoint
.\SP\AutoSPInstaller\AutoSPInstallerLaunch.bat

Your new C:\SharePoint should look something like this :

So Until now in the 3 Sections that we completed we:

  • Changed our PC Name and Created a Domain
  • Installed Prerequisite Software and Features
  • Prepared our ConfigurationFile.Ini for future SQL installs and SQL install Script
  • Prepared our SharePoint 2013 Sources and AutoSPInstallerInput.xml file for future installs!
  • And we Also installed SQL 2012 and SP2013 of course!

Now it’s time to install the other software! Head over to Installing Visual Studio 2012 and Optional Software 

Share this post with your followers on twitter:

Leave  a comment and don’t forget to like us on Facebook here and to follow me on Google+ here and on Twitter here  for the latest news and technical articles on SharePoint.  Also, don’t forget to check out SharePoint Community.Net for more great SharePoint Content

Previous Post
SharePoint 2010 RTM Language Packs are gone! What do I do now?
Next Post
SharePoint 2013 Apps do not load CSS properly 403 – defaultcss.ashx

49 Comments

  • October 22, 2013 at 12:40 pm
    Rohit

    Superb…

    Reply
  • October 29, 2013 at 11:52 am

    Vlad, timely and informative post.. I decided to run the script for a test SharePoint 2010 to demo to a client. Oddly it creates my content db under the web app but then bombs out creating the site collection … I am looking through ULS but if you have any ideas this would help as exceptions in PS give me a headache!
    Note the name of the site was named by someone else….

    xception : System.UnauthorizedAccessException: 0x80070005Access denied.
    at Microsoft.SharePoint.Library.SPRequest.CreateSite(Guid gApplicationId, String bstrUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, String bstrDatabaseServer, String bst

    Reply
  • October 29, 2013 at 11:56 am

    The xml was pulled last time so I will attempt to ‘fool’ your blog comments widget
    [SiteCollection siteUrl=”http://sharepoint”
    HostNamedSiteCollection=”false”
    Owner=”Domain\SP_AppPoolSharePoint”
    Name=”SharePoint Home”
    Description=”SharePoint Home Site aka Source in Development”
    SearchUrl=”http://sharepoint/search”
    CustomTemplate=”false”
    Template=”STS#0″
    LCID=”1033″
    Locale=”en-gb”
    Time24=”false”]
    [/SiteCollection]

    Reply
    • October 29, 2013 at 2:49 pm

      Hey Daniel,

      If you’re running it on SP2010, can you check that “UseClaims” is set at “false” for the Web Application? Tell me how it goes!

      Thanks!

      Reply
  • October 29, 2013 at 5:25 pm

    Vlad

    Thanks for your reply. Ironically, I did have claims set to false but a dev at a SUGUK meet convinced me that set this true ( since claims is implemented under the covers by default to work against windows in sp2010 ) …

    databaseName=”Content_SharePoint” useClaims=”false”
    useBasicAuthentication=”false”

    Unfortunately, I still get the error. Note, I can happily create my Site col in central admin ( using the same account I run SPAUtoinstaller with) .

    Reply
    • October 29, 2013 at 9:30 pm

      Hey Daniel… I got a good news and a bad news…

      Personally I never had this error… however you’re the second person in two days who asked me about this error (I got 50+ installs with it and never got it…). I will ask Brian Lalancette (creator of AutoSPInstaller) if he has any ideas about it and we will try to figure it out. As soon as I get an answer I will answer!

      Thanks!

      Reply
  • October 30, 2013 at 5:51 am

    Vlad

    Well at least you didn’t start your comment with “It depends….” 😉 Ok sounds like a plan. I am not in the office but I can citrix on to the server and feedback anything you ask me to. such as ULS
    – note I can create my portal site collection via central admin using my account ( which as domain admin)
    – I originally used the SPSourceBulder to download the pre-reqs, SP1 and October CU 2011 to build /sharepoint. I could rebuild this staging area and just merge SP2 only into my install /SharePoint folder.
    – I can uninstall SharePoint and reinstall via the script – at least I don’t have to sit and watch it!

    Reply
  • October 31, 2013 at 4:55 am

    Yes I do have my “default web site” which of course points to my home page of my default web app. I have updated the (20065) issue page . Next thing to try is a simple powershell test. I won’t have much time to resolve this today before I will be asked to simply manually install everything as the client wants to set up a demo today.

    Reply
  • October 31, 2013 at 1:22 pm

    Vlad

    Turns out that if you comment out @hostHeaderWebAppSwitch which ironically is set to “” in for SharePoint 2010 the script just runs until the portal and mysites are loaded into the browser … very impressive. I have updated the issue on this.

    Reply
    • October 31, 2013 at 6:28 pm

      That’s very good to know and glad you got it resolved! Also thanks for posting the resolution for other people when they search for it!

      Reply
  • November 1, 2013 at 9:42 am

    Vlad,

    I have posted a fix to Brian’s code https://autospinstaller.codeplex.com/workitem/20065 … not ground breaking but I have tested it to see that t works. Hopefully that should put and end to my posts on the subject 😉

    Reply
  • November 25, 2013 at 10:35 am

    Never say never eh? I am setting up a new SP2013 install so using AutoSPSourceBuilder
    I took the original AutoSPSourceBuilder and tweaked it to handle my client’s web proxy . I copied the rtm media to the server ( as dvd is locked down by admin)

    .\AutoSPSourceBuilder_webproxy.ps1 -SourceLocation “C:\Dev\AutoSPInstaller\SP\2013\SharePointOriginalMedia” -UpdateLocation “C:\Dev\AutoSPInstaller\SP\2013\Updates” -Destination “C:\Dev\AutoSPInstaller\SP\2013\SharePoint” -GetPrerequisites $true

    This fails as the script continuously asks me for the CUs it detects
    – Available Cumulative Updates:
    – December 2012
    – March 2013
    – April 2013
    – June 2013

    Even when I keep entering: return then return then return….. (!) .. I can edit Brian’s script to comment out the 2013 cu bit ( if it detects 2013) but I just wondered why you didn’t get the same issue.

    Reply
    • November 25, 2013 at 11:24 am

      Enter “none” and press enter when it asks you for the CU! Tell me how it works!

      Reply
  • November 26, 2013 at 8:42 am
    Björn

    Entering “none” works – thanks.

    Reply
  • January 24, 2014 at 10:53 am
    MikeM

    This tutorial is absolutely epic, Thanks so much! Very helpful.

    Reply
  • January 27, 2014 at 1:29 pm
    MikeM

    Found a typo!:
    it will have copied all the SharePoint 2013 Media in the C:\SharePoint\2013\SharePoint
    Should read:
    it will have copied all the SharePoint 2013 Media in the C:\SharePoint\SP\2013\SharePoint

    Reply
  • February 11, 2014 at 2:21 pm
    Tony

    Vlad – first of all, I want to thank you for your blog post. I’ve reviewed other blog posts when approaching this project and yours stands out by far. I ran through the script 2 times and keep running into an issue during the part 3 setup – wondering if you can help me figure out where/how to triage this. Here’s the result of the autosp log file

    ———————————-
    – SharePoint 2013 binaries are not yet installed.
    – Install based on:
    – C:\SharePoint\AutoSPInstaller\SP\AutoSPInstaller\\AutoSPInstallerInput.xml
    – Environment: Dev
    – Version: 3.96
    ————————————————————-
    – Validating user accounts and passwords…
    – Account “TL2014\SP_Farm” (Account)…Verified.
    – Account “TL2014\SP_Services” (ManagedAccount)…Verified.
    – Account “TL2014\SP_Pool” (ManagedAccount)…Verified.
    – Account “TL2014\SP_Pool” (ManagedAccount)…Verified.
    – Account “TL2014\SP_Search” (ManagedAccount)…Verified.
    – Account “TL2014\SP_Admin” (User Profile Service Application)…Verified.
    – Account “TL2014\SP_Services” (EnterpriseSearchService)…Verified.
    – Account “TL2014\SP_Crawl” (Search Service Application)…Verified.
    – Account “TL2014\SP_Services” (SharePoint Search Application Pool)…Verified.
    – Account “SP2014\SP_Services” (SharePoint Search Application Pool)…Verified.
    – Account “TL2014\SP_Superuser”…Verified.
    – Account “TL2014\SP_Superreader”…Verified.
    – Account “TL2014\SP_Pool”…Verified.
    ————————————————————-
    – Writing config-AutoSPInstaller.xml to C:\Users\sp_admin\AppData\Local\Temp\1…
    ————————————————————-
    – Testing access to SQL server/instance/alias: TL2013
    – Trying to connect to “TL2013″… – Fail
    ————————————————————-
    – Script halted!
    – Connection Error. Check server name, port, firewall.
    ress any key to exit…
    ———————————-
    Automated SP2013 install script |
    Started on: 2/10/2014 8:23:34 PM |
    Aborted: 2/10/2014 8:25:40 PM |
    ———————————-
    S C:\SharePoint\AutoSPInstaller\SP\AutoSPInstaller>

    Reply
    • February 11, 2014 at 4:51 pm

      Hey Tony, it looks like SP cannot connect to SQL. If you open SQL Server Management Studio, can you connect to the instance only by using “TL2013”? If no .. I think (from my experience) that autospinstaller creates a Pipes Alias when only on one server. Verify this by typing “cliconfg” in run and check out the type of Alias. If it’s really in Pipes Alias.. can you manually create your TL2013 alias by using TCP/IP and in Autospinstaller, put “create alias = false” and DBName = your Alias.

      I know this would not be the optimal solution but it would prove that that is the issue. Temporarily, just don’t create an alias and put SQL Server “localhost” for your VMs and it should work! If it fixes your problem please tell me and I will go back to Brian Lalancette (AutoSPInstaller Creator) to make everything tcpip.

      Reply
    • September 3, 2014 at 8:56 am
      Anthony

      Like many others before me. Many thanks for your blog post as it is great for a lot of different reasons.

      I’ve the same error like Tony and i can’t resolve it even if i can connect to SQL Server Management Studio. I tried localhost but i had the same problem (I uses SQL Server 2014).

      Anyone can help me ?

      Thanks
      Anthony

      Reply
      • September 25, 2014 at 1:06 am

        Hey Anthony, If you look in your Services, do you see what is the name of your SQL Server Instance? (you will see something like SQL Server (MSSSQLServer).

        I didn’t try the script with 2014, but it should still work! Maybe your account doesn’t have access? Did you add it when initially configuring the ini file?

  • March 7, 2014 at 4:59 am
    Mohammed Ilyas

    Like many others before me. Many thanks for your blog post as it is great for a lot of different reasons.

    I was getting the same error as Tony about failing to connect to the db. I fixed it by running “cliconfg” and editing the alias so the server name was set to ‘localhost’ and the script started to work.

    Your breakdown of the script is great as I wanted to adjust something for my needs. I setup my VM with two NIC’s with one using fixed private address and the other connected to the internet using dhcp allows me to get windows updates and do other things from the net. So I did NOT enable remote desktop and as I’m happy to remote desktop to the host machine running the VM and did NOT disable the firewall as the VM is connected to the internet.

    The script failed for me when creating the web application, but this could be since your post that updates to AutoSPInstaller caused this. I fixed the issue of the web application by sticking with the CommonName values for the managed accounts as specified by the AutoSPInstallerInput.xml, i.e.

    DOMAIN\SP_Services

    DOMAIN\SP_PortalAppPool

    DOMAIN\SP_ProfilesAppPool

    DOMAIN\SP_SearchService

    I had an issue with the Secure Store Service Application throwing and error

    – Provisioning Secure Store Service Application…
    – Starting Secure Store Service Instance…
    – Waiting for Secure Store service…Online
    – Creating Secure Store Service Application…
    – Creating Secure Store Service Application Proxy…
    – Done creating Secure Store Service Application.
    – Creating the Master Key…
    Update-SPSecureStoreMasterKey : Secure Store Service did not performed the operation.
    At C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3659 char:13
    + Update-SPSecureStoreMasterKey -ServiceApplicationProxy $secureStore. …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (Microsoft.Offic…eStoreMasterKey:SPUpdateSPSecureStoreMasterKey) [Update-
    SPSecureStoreMasterKey], FaultException
    + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCmdlet.SPUpdateSPSecureStoreMasterKey

    – Creating the Application Key…
    – Done creating/configuring Secure Store Service Application.

    The above error did not cause the script to abort and is something I can resolve once the dev machine is up.

    I did notice that you had the ‘SuperUser’ and ‘SuperReader’ accounts possibly set incorrectly in your screenshot. I set mine to:

    DOMAIN\SP_CacheSuperUser
    DOMAIN\SP_CacheSuperReader

    I am using the ISO of SharePoint Server 2013 with SP1 and did not download the March 2013 PU or the August 2013 CU, so some issues might be specific to me. Thanks for showing how to include future updates. I’m hoping now to install Visual Studio 2013 using your instructions, hopefully with your guidance on the next page, I’ll manage it.

    Reply
    • March 14, 2014 at 12:29 am

      Thanks and glad you liked it! I haven’t tested it with SP2013 with Sp1! Will do!

      Reply
  • March 20, 2014 at 9:50 am
    George

    Hi Vidar

    Good block and good information. I have followed your guide and the script run perfectly. No errors at all. When script is finished porta, central administration all was , working. If i do a restart of the server , i get the service unavailbale on all , portal, central administration. Do you have any idea what could be the problem? All service account are correct , nothing locked. On the IIS application pools, stoped the security token service app pool , sharepoint web services root and central admin , i can start them normaly but when i go to access the web site of central admin then again servise unavailable and they stop again… Any advice it would be nice. I use windows server 2008 R2 (all updates installed), sharepoint 2013 enteprise and on an other server SQL 2012.

    Reply
    • March 20, 2014 at 9:50 am
      George

      sorry for my mistake of your name. I ment Vlad. 🙂

      Reply
  • March 21, 2014 at 2:55 am
    George A.

    HI Vlad. Great job. I used your guide and i had a 100% success on the installation. BUt i have come to one problem. When server restarted , i get to all web sites service unavailable , centran admin , protal … the app pool start and the web sites also.. BUt trying to access them get the service unavailable. I start them again the pool apps and the same happen. Any advise?

    Reply
    • April 24, 2014 at 10:14 pm

      Did you check if your passwords were fine? I think that might be problem!

      Reply
  • April 8, 2014 at 2:19 am
    EdD041

    I Keep getting this error;

    ————————————————————–
    ————————————————————–
    – Installing Prerequisite Software:
    – .Net Framework 3.5.1 from “C:\SharePoint\SP\2013\SharePoint\PrerequisiteInstallerFiles\sxs”…Already installed.
    – Running Prerequisite Installer (offline mode)….Done.
    – Prerequisite Installer completed in 00:00:05.
    – SharePoint 2013 “missing hotfix” prerequisites…
    WARNING: 2014-04-07 08:47:03 – Error: Unable to install (2)
    WARNING: 2014-04-07 08:47:03 – Error: [In HRESULT format] (-2147024894)
    WARNING: 2014-04-07 08:47:03 – Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
    WARNING: 2014-04-07 08:47:03 – Last return code (2)
    ————————————————————–
    – Script halted!
    – Review the log file and try to correct any error conditions.
    Press any key to exit…

    Since the start of the tutorial everything had been going well till this….

    Reply
    • June 17, 2014 at 12:07 pm

      check if your windows update service in services is started!

      Reply
  • May 22, 2014 at 3:19 pm
    Grig

    Hi Vlad,
    There is a switch to choose the installation language ( I wold like to have the option to installed in French or English)?
    The search I suppose is not configured? The same for Apps ?
    Thanks
    Grig

    Reply
    • June 17, 2014 at 11:49 am

      It will depend on the binaries you have! if your binaries are in french it will be french!

      Reply
  • September 6, 2014 at 6:13 am
    Venkat.KL

    Very Helpful Post.

    btw; Is this willful or by mistake;

    SP_Superreader to SuperUser and vice versa;

    vladdev\SP_Superreader
    vladdev\SP_Superuser

    Reply
    • September 6, 2014 at 6:15 am
      Venkat.KL

      vladdev\SP_Superreader
      vladdev\SP_Superuser

      Reply
      • September 6, 2014 at 6:16 am
        Venkat.KL

        Sorry; ObjectCacheAccounts is getting deleted 🙁

    • September 12, 2014 at 12:56 pm

      Oups, it’s a mistake! Congrats.. you’re the first one to see it hehe!

      Reply
  • September 6, 2014 at 8:50 am
    Venkat.KL

    Kindly Leave the above comment which is not very very important.

    BTW; when run AutoSPInstaller.bat Batch File, simply waiting at “Waiting for SharePoint Products and Technologies Wizard to launch”

    – Installing SharePoint 2013 binaries……………………………………………………………Done.
    – SharePoint 2013 setup completed in 00:37:45.
    – Waiting for SharePoint Products and Technologies Wizard to launch ……………………………………………………………………………………………… ……………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………..

    Reply
  • September 7, 2014 at 6:18 am
    Venkat.KL

    ————————————————————–
    – Creating web applications…
    ————————————————————–
    – Script halted!
    – “Portal” managed account not found! Check your XML.
    Press any key to exit…

    Reply
    • January 27, 2016 at 4:27 pm
      caku

      Did you find the solution for the problem
      ————————————————————–
      – Creating web applications…
      ————————————————————–
      – Script halted!
      – “Portal” managed account not found! Check your XML.
      Press any key to exit…

      Reply
  • November 26, 2014 at 7:25 am
    tradelingua

    i am still become following failure the sql-server ist different from sp-machine:

    Script halted!
    Connection Error. Check server name, port, firewall.
    ess any key to exit…

    There is no sql-alias. The Installation-User have local admin rights on both servers and the sysadmin-role on the sql-server

    Thanks in advance

    Tradelingua

    Reply
    • December 2, 2014 at 11:19 pm

      The script was really made for a 1 machine deal. Are you sure you are connecting to the good SQL Server?

      Reply
  • December 8, 2014 at 11:00 am
    Provisioning Managed Metadata Service Application

    While trying to install I got rather far. But was stopped not being able to find the managed account that was properly installed, or so it seems. The loop for the managed accounts seems off. While trying to rerun the scripts I did receive an error that the account as already registered and the script stopped. It would seem that a validation to see if it does exist would fix that.

    error 1
    Managed account domain\SP_Services not found at At C:\Sharepoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2111 char:41

    error 2
    – Adding Managed Accounts…
    – Account “sp2013.local\SP_Services:
    – Creating local profile for sp2013.local\SP_Services…
    – Adding to local Admins (*temporarily*)…OK.
    – Removing from local Admins…OK.
    – Done.
    – Registering managed account sp2013.local\SP_Services…
    New-SPManagedAccount : Account sp2013.local\SP_Services has already been registered.
    At C:\Sharepoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2076 char:17
    + New-SPManagedAccount -Credential $credAccount | Out-Null
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (Microsoft.Share…wManagedAccount:SPCmdletNewManagedAccount) [New-SPManage
    dAccount], InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewManagedAccount

    Reply
  • December 8, 2014 at 11:02 am
    Vince

    Also wanted to mention, this is the best blog on how to install sharepoint I have found. Thank you so much

    Reply
  • January 14, 2015 at 3:09 am
    Candice

    Thanks, this is great.

    Reply
  • February 9, 2016 at 6:48 am
    Wilco

    Hey, great post! Has anyone tested this with Windows server 2012 r2 answer sharepoint 2013 sp1? I can’t seem to get it to work…

    Reply
  • February 9, 2016 at 6:49 am
    Wilco

    Hey, great post! Has anyone tested this with Windows server 2012 r2 and sharepoint 2013 sp1? I can’t seem to get it to work…

    Reply
  • February 9, 2016 at 6:32 pm
    Wilco

    Hi Vlad,

    First of all… WOW 🙂 This really is cool and useful!
    I finally got it to work on Windows Server 2012 R2 / SQL 2014 / SP2013 SP1, but I still have a few issues…
    I got an error during the installation for the “secure store service”, which now doesn’t run (see output file below). I also had isues with SQL… Had to manually add a named pipe alias to localhost.

    Can you help me with the last “secure store” error? Any idea? Can I retry the whole process?

    **********************
    Windows PowerShell transcript start
    Start time: 20160209153147
    Username: DYSDEV\Administrator
    RunAs User: DYSDEV\Administrator
    Machine: SP2013DEV (Microsoft Windows NT 6.3.9600.0)
    Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoExit -ExecutionPolicy Bypass C:\SharePoint\SP\AutoSPInstaller\\AutoSPInstallerMain.ps1 C:\SharePoint\SP\AutoSPInstaller\\AutoSPInstallerInput.xml
    Process ID: 4140
    **********************
    Transcript started, output file is C:\Users\Administrator\Desktop\AutoSPInstaller-2016-02-09_2-36.rtf

    PS>TerminatingError(Get-SPFarm): “Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permissions to access the database before trying again.”
    WARNING: Timed out waiting for service creation (maybe a UAC prompt?)
    New-SPSecureStoreServiceApplication : The timer job completed, but failed on one or more machines in the farm.
    At C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3925 char:17
    + New-SPSecureStoreServiceApplication -Name $secureStoreServiceApp …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (Microsoft.Offic…viceApplication:SPNewSecureStoreServiceApplication) [New
    -SPSecureStoreServiceApplication], SPException
    + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCmdlet.SPNewSecureStoreServiceApplication

    Update-SPSecureStoreMasterKey : Secure Store Service did not performed the operation.
    At C:\SharePoint\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:3935 char:13
    + Update-SPSecureStoreMasterKey -ServiceApplicationProxy $secureStore. …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (Microsoft.Offic…eStoreMasterKey:SPUpdateSPSecureStoreMasterKey) [Update-
    SPSecureStoreMasterKey], AddressAccessDeniedException
    + FullyQualifiedErrorId : Microsoft.Office.SecureStoreService.PowerShellCmdlet.SPUpdateSPSecureStoreMasterKey

    Attempting stop…
    Internet services successfully stopped
    Attempting start…
    Internet services successfully restarted
    **********************
    Windows PowerShell transcript end
    End time: 20160209162731
    **********************

    Reply

Leave a Reply