Two short video tutorials, Creating a SharePoint 2013 testing environment – Part 3 – Installing AdventureWorks sample database and Creating a SharePoint 2013 testing environment – Part 4 – Setting up service accounts in Active Directory, authored by Asif Rehmani, wrap up a presentation on how to build the supporting infrastructure required for a test environment for SharePoint 2013.
Setting Up a Database for the SharePoint 2013 Test Environment
The AdventureWorks database is a sample provided by Microsoft. Interested parties can download the database from CodePlex at no charge. Asif Rehmani demonstrates how to download the compressed repository for the database to a folder, where he opens the repository for further activity.
The script for the database is executed from SQL Server 2012 Management Studio. The first step is to activate SQL Server 2012 (once again from the Management Studio). Once SQL Server 2012 is running, then the “instawdb” script is identified and run from the folder in which the components of the AdventureWorks database have been locally stored. As Asif Rehmani notes, it is critically important that the Query be set to “sqlcmd mode” before running the script.
Once the necessary settings to correctly execute the script have been made, the script, itself, needs to be modified to include the actual local folder location. Once the edit has been done, the script should run, successfully.
Setting up Service Accounts with Active Directory
As Asif Rehmani notes, “SharePoint requires some service accounts, which are created in Active Directory”. These accounts can be set up automatically by running a script like the “CreateSpServiceAccounts” script, which is provided by Critical Path Training. Another option is to manually set up these accounts through “Computers” and “Users” for the Domain Controller for your Windows 2008 R2 network.
The latter option requires that 3 accounts be set up in Active Directory. The first account is the SharePoint Farm Account, “SP_Farm” in this video tutorial example, which is the main Farm account for the test environment. Asif recommends that the password set for the account should be configured to never expire.
The second service account is set up for content, with the name “SP_Content”. This account is used to fetch content for workflow service and workflow manager. The login name and password should conform to the procedure followed for the “SP_Farm” service account.
The third and final service account is set up for services, “SP_Services”. The credentials for this account are configured with user name and password (set never to expire) as was the case for the prior two service accounts.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved