This morning I awoke early to a lovely fall-esque morning, bright sun, clear sky, and just a little chill to the air…you never would have thought it was mid-August.
So a beautiful morning, mixed with a delightful cup of coffee (Wegman’s Cinnamon Nut coffee blend) seemed like the perfect fit to write an article on how to install SharePoint 2010 on a local virtual machine with domain connections for development.
So gather you cup of choose beverage ( I recommend a Bell’s Double Creamy Stout for an evening session of install, but I’ll leave that for you to decide) grab the machine of choice and let us begin.
I can’t claim to know it all, and have borrowed the notes made by Neil ‘The Doc’ Hodgkinson in his article from October 19, 2009 found at, http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=112.
My first time attempt at performing an advance install of SharePoint 2010 on a single machine, I ended up with the following error message:
(For the search engine: The specified user <local user> is a local account. Local accounts should only be used in stand alone mode.)
So reading this message, I then uninstalled and tied again, but this time using the Stand Alone option given at install time. Well, this worked…BUT you end up with a special SQL Express version installed on your machine, and no control over what user accounts are performing what actions. This was not ideal for me, nor did it give me the additional practice of SharePoint farm installation that I was seeking.
So enough of the small talk…onto the How To!
- The first step is to plan out the appropriate user accounts that will be needed throughout the installation process.
- Based on guidance found in MSDN and the SharePoint Getting Started Guide (http://www.microsoft.com/downloads/details.aspx?FamilyID=3ba69d42-65a2-48fb-88d9-814034874498&displaylang=en) there area number of different user accounts that can be created and assigned to different tasks, in general I would recommend creating the following three accounts.
- SQL Server Service Account
- Purpose: Default account used to run the SQL Server services
- Setup User Account
- Purpose: Runs the Setup, SharePoint Products Configuration Wizard
- Specific Requirements: Must be part of the Administrators group, and have read/write access to the SQL server. In addition this account should have db_owner rights in SQL so that PowerShell can be leveraged to get around the noted local account issue.
- Server Farm and Database Access Account
- Purpose: Configure and manage the server farm and acts as the app pool identitiy for Central Administration.
- Place the DVD into your system or mount the ISO you have. The following opening screen shall come up. Click Install software prerequisites to begin with to confirm all the needed items are installed.
- This is the opening screen to the prerequisite checker.
- Click Finish. You will be returned to the opening screen.
- Click Install SharePoint Server
- Enter your Product Key and click Continue.
- You are now prompted to either perform a standalone or a server farm install.
- Under the Server Type options, you should select Complete as it provides the ability to properly customize the installation.
- Once the installation completes, you will be asked to launch the Configuration Wizard. DO NOT just blindly click Close. Uncheck the box that says "Run the SharePoint Products Configuration Wizard now." If you don’t the local user account error message will be displayed.
- Exist out of the Install screen by clicking Exit.
- Now the product is installed, but nothing has been setup and configured. Why? Because we have delayed the running of PSConfig so that we could use local user accounts, instead of being attached to a domain controller.
- This is were Neil’s blog article comes into play. His article can be found at http://sharepoint.microsoft.com/Blogs/fromthefield/Lists/Posts/Post.aspx?ID=112.
- SharePoint 2010 has been integrated into PowerShell with a collection of administration cmdlets, more on this in future posts, some of which we are use to seeing as part of STSADM, and even some new ones.
- For our issue we will need to use New-SPConfigurationDatabase cdmlet. This cmdlet creates a new configuration database on the designated SQL server, for a SharePoint Farm.
- From the start menu open SharePoint Management Shell running it as Administrator this is required even if you are logged as a local administrator….this is a PowerShell prompt, with the SharePoint modules included, and enter New-SPConfigurationDatabase at the prompt and hit enter.
- You will then be asked to enter the required information for a configuration database.
- When prompted for the Farm Credentials make sure to include your machine name as the domain for the account and to enter the password. Passphrase is the password used of the login account.
- If you receive any error messages, close out of the PowerShell console, delete the Admin and the configuration databases, if they exist, and try again. It does seem to take a few minutes for the process to complete.
- Once this succeeds launch the SharePoint Products Configuration Wizard. You will not get the normal opening screen, as we have already created the farm information via the above PowerShell cmdlet.
- Since the farm has already been created you will be shown the current farm settings. Make sure "Do not disconnect from this server farm." and click Next
- You will now be asked to configure the necessary settings for the Central Administration Web application for the new farm. Feel free to assign a new port or accept the default, just make sure to take note of what it is. As we will be using local user accounts through out this setup, NTLM is the preferred security setting.
- After clicking Next, you will be given a chance to review the settings for the farm. If everything looks correct, click Next.
- Configuration will now begin, the green processing bar will fill back and forth completing the 9 tasks of SharePoint configuration. Upon completion of the 9 configuration tasks, you should see the "Configuration Successful" screen. Click Finish and the CA should appear.