Tag Archives: Kerberos

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 8 – Configuring My Sites and User Profiles

Posted on by

UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

MySites

We are now going to create a new Web Application for our My Site site. However we are not going to create a HNSC like we did for dev.cannonfodder.local, here we are going to create path-based site collections. From the Microsoft Technet article (which is for SP2010, so it might be different now, but couldn’t see anything saying something different) that there is a guideline for mysite sites.

  • You must use the self-service site creation feature that is included with SharePoint Server to create path-based site collections. MySite should be created as a path-based site or a custom solution should be provided.

Creating a Web Application for MySites

  1. From the start menu, type Central Administration and open the site.
  2. Select Application Management > Manage Web Applications.
  3. In the ribbon click the New icon.
  4. In the Create New Web Application dialog leave Create a new IIS web site selected and type the name as SharePoint My Site Host, leave the port as 80, and put my.cannonfodder.local in the host header.
  5. For simplicity in finding the Web Applications, I put the path on a different drive. D:\VirtualDirectory\MySite
  6. Under Claims Authentication Types set the Integrated Windows Authentication to Negotiate (Kerberos)
  7. Under Application Pool, select Use existing application pool and select SPContent App Pool
  8. Under Database Name and Authentication set the Database Name to SP_DEV_MySites.
  9. Scroll down to the bottom and click OK.
  10. Once the Web Application of My Site Host has been setup, click the link to Create
    Site Collection

Creating a Site Collection for MySites.

  1. On the Create Site Collection put the Title as My Site Host
  2. Set the URL as /
  3. The Template section as My Site Host, which can be found in the Enterprise tab
  4. Set the Primary Site Collection Administrator as cannonfodder\administrator

  5. Scroll down to the bottom and click OK.

Configure the Web Application to Host My Sites.

  1. After you have created your site collection, you should be returned to the Manage Web Application page. Select SharePoint My Site Host by clicking on it. This will highlight the line and items in the ribbon will become available to you.
  2. In the ribbon click the button Managed Paths

  3. In the Define Managed Paths dialog tick Sites. Then click the link Delete selected paths.
  4. Now add a new path called personal and make it Wildcard inclusion.
  5. Add another new path called my and make it Explicit inclusion. Then click OK.

  6. With SharePoint My Site Host still selected click the icon on the ribbon called Self-Service Site Creation.

  7. On the Self-Service Site Creation page, under Site Collections, select the on radio button. Click OK.

Add my.cannonfodder.local to DNS

  1. From the start menu, type DNS and open the application.
  2. Expand Forward Lookup Zones,
    right click cannonfodder.local and select New Host (A or AAAA)…
  3. For Name put my. Put the IP Address as 192.168.139.99, click Add Host. Click OK to the DNS message box stating the host record wad successfully created. Close DNS Manager.

Create Kerberos SPN for my.cannonfodder.local

  1. From the start menu, type cmd and open Command Prompt.
  2. Type setspn –S HTTP/my.cannonfodder.local cannonfodder\SP_Content
  3. While here also flush dns by typing ipconfig /flushdns
  4. Close Command Prompt window.

Configuring the User Profile Service Application My Site settings.

  1. In Central Administration left hand menu, select Application Management.
  2. Under Service Applications select Manage Service Applications.
  3. Find the User Profile Service Application in the list and click on it.

  4. Under the My Site Settings section click the Setup My Sites link.
  5. On the My Site Settings page, set the My Site Host to http://my.cannonfodder.local
  6. Under the heading Personal Site Location set the value to personal. Now click OK.

Configuring SharePoint User Profile Service Application with Active Directory.

There is a new way to import users into the user profile from Active Directory in SharePoint 2013. It is called Active Directory Import. It is a faster than the SharePoint 2010 way of using the FIM approach. Spencer Harbar has written a good blog about it here.

  1. From the start menu, type Central Administration and open.
  2. Under Application Management click Manage Service Applications.
  3. Find the User Profile Service Application and click the link.
  4. Under Synchronization, click Configure Synchronization Settings.
  5. On the Configure Synchronization Settings page, under Synchronization select Use SharePoint Active Directory Import and click OK.
  6. Back on the User Profile Service Application page, under Synchronization, select Configure Synchronization Connections.
  7. On the Configure Synchronization page, select Create New Connection.
  8. Put the following details in the Add New Synchronization Connection page.
    1. Connection Name: Cannonfodder AD
    2. Type: Active Directory import
    3. Connection Settings:
      1. Fully Qualified Domain Name: cannonfodder.local
      2. Authentication Provider Type: Windows Authentication
      3. Account Name: cannonfodder\administrator
      4. Password: Pa55w0rd
      5. Confirm Password: Pa55w0rd
    4. Under Containers click Populate Containers.
    5. After it loads, expand CANNONFODDER and then tick Users. Click OK.
    6. You will now be returned to the Synchronization Connection Page. You will see your new connection display.
  9. Repeat Steps 2 + 3 to navigate back to User Profile Service Application.
  10. Take note that on the right hand side of the screen under Profiles it states that there are 2 User Profiles.
  11. Under Synchronization, click Start Profile Synchronization.
  12. Select Start Full Synchronization and click OK.
  13. Refresh the Manage Profile Service: User Profile Service Application page, and you should see more User Profiles.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 7 – Configuring Hosting Apps

Posted on by

UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

In this blog I will talk about setting up your environment for Hosting Apps. The best blog I have found out there is by Mirjam (SharePointChick). The first attempt I did at setting up an App Host I used Mirjam blog to help me.

There are 3 choices here. Create a New Domain, a Subdomain or create a new wildcard so all requests for http://*.cannonfodder.local will be forwarded to our SharePoint machine. The last option is mentioned in Critical Path Training SharePoint 2013 Virtual Machine Setup on Windows Server 2008 R2, and is a perfectly valid option for single development machine. As you only have one machine, all requests can go to it. This step by step guide I’m doing also is a single machine, however I don’t know if in the future if I will create another machine in my domain, maybe an exchange server, even an Office Web App server. Also by creating a separate domain helps prevent cross-site scripting between apps and SharePoint sites. Therefore my instructions are following Mirjam’s blog, and creating a new Domain.

Configuring Hosting Apps

First we need to configure DNS.

  1. From the Start Menu, type DNS, and open the application.
  2. In the Left Hand panel, right click Forward Lookup Zones and select New Zone… Click Next
  3. Keep the Primary zone selected and Store the zone in Active Directory ticked. Click Next >
  4. Leave the option To all DNS servers running on domain controllers in this domain: cannonfodder.local. Click Next >
  5. Here you enter the domain name, type cfapps.com. Click Next >.
  6. Leave the top option selected and click Next >
  7. Click Finish. You will see your new domain showing in the Forward Lookup Zones in DNS.
  8. Now right click on cfapps.com and select New Host (A or AAAA)…
  9. Type * for Name
  10. Set the IP address as the IP Address of the server. In my case 192.168.137.99

    As Mirjam states in her blog, if you are using more than one server in a Network Load Balance environment, point the DNS record of the primary cluster address for the NLB environment.

    Now if you open a command window and type in nslookup something.cfapps.com it will resolve to your server.

    While we are here, we should also create the Hosts for two sites we will be creating later.

    1. Still with DNS Manager in the left panel, right click cannonfodder.local within the Forward Lookup Zones and right click to create a New
      host (A or AAAA)…
    2. Type Dev in the Name, and set the IP address to the IP address of the server. In my case 192.168.137.99. Click Add Host.
    3. Repeat steps 1 and 2, but type Intranet in the name, and set the IP Addess to 192.168.137.99
    4. Within the Command prompt, type ipconfig /flushdns.
    5. While you are in the Command prompt, we should also set up the Kerberos for the sites. Type the following
      setspn –S HTTP/cannonfodder.local cannonfodder\SP_Content
      setspn –S HTTP/dev.cannonfodder.local cannonfodder\SP_Content
      setspn –S HTTP/intranet.cannonfodder.local cannonfodder\SP_Content

Configuring SharePoint Server 2013 for Host-Named Site Collection and create Initial Site Collections.

Here we are going to create Host Named Site Collection (HNSC) for testing and hosting our apps. Microsoft recommends this, and more can be found out directly from the technet article: http://technet.microsoft.com/en-us/library/cc424952.aspx . The only way you can create HNSC is via powershell. So this is what we are going to do, after we have removed the original Web Application created when SharePoint Wizard was run. It is also using the wrong service account of SP_Services. We also need to register SP_Content as a manage account.

Register SP_Content

  1. From the Start menu, type Central Administration and open the link.
  2. Select Security > Configure managed Accounts.
  3. Click Register Managed Account
  4. Type UserName as cannonfodder\SP_Content and the password as Pa55w0rd. Then click OK.

Create a new Web Application

  1. Select Application Management > Mange Web Applications.
  2. Select the Web Application SharePoint – 80 the URL of this is http://cannonfodderser/
  3. On the Ribbon, click Delete. A dialog will appear, say Yes to both Delete content databases and Delete IIS web sites. Then click Delete. Click OK to the warning.
  4. In the ribbon click on New.
  5. In the Create New Web Application dialog leave Create a new IIS web site selected and type the name as SharePoint HNSC Host, leave the port as 80.
  6. For simplicity in finding the Web Applications, I put the path on a different drive. D:\VirtualDirectory\HNSC
  7. Under Claims Authentication Types set the Intergrated Windows Authentication to Negotiate (Kerberos)
  8. Under Application Pool, select Create new application pool, and set the name as SPContent App Pool, select Configurable radio button and select Cann0nf0dder\SP_Content.
  9. Under Database Name and Authentication set the Database Name to SP_DEV_HNSC.
  10. Scroll down to the bottom and click OK.
  11. When SharePoint asks you create a Site Collection, just click OK, as we are going to create the Site Collection by Powershell.

Creating the Site Collections.

Here we are going to create a TeamSite called Intranet.cannonfodder.local and a Developer Site called dev.cannonfodder.local. Please note you can only create, debug and test apps using a developer site. You could type the Powershell into notepad, save the file as a PS1 and run it from the SharePoint 2013 Management Shell, instead of typing each row directly into the SharePoint 2013 Management Shell.

  1. From the Start Menu, type SharePoint 2013 Management Shell, and open the application.
  2. Type

    $hnsc = Get-SPWebApplication | Where-Object {$_.DisplayName –eq "SharePoint HNSC Host"}
New-SPSite –Name "Root HNSC Site Collection" –Url http://cannonfodder.local –HostHeaderWebApplication $hnsc –OwnerAlias "Cannonfodder\Administrator"
New-SPSite –Name "Cannonfodder Development" –Url http://dev.cannonfodder.local –HostHeaderWebApplication $hnsc –Template "DEV#0" –OwnerAlias "Cannonfodder\Administrator"
New-SPSite –Name "Cannonfodder Intranet" –Url http://intranet.cannonfodder.local –HostHeaderWebApplication $hnsc –Template "STS#0" –OwnerAlias "Cannonfodder\Administrator"

Update Internet Explorer to Bypass the URL to log in automatically.

  1. On the Start Menu, type Internet Explorer and open the application. (To avoid opening the Windows Server 2012 App version of Internet Explorer, right click on the icon and select Pin to task bar, then on the desktop you can click the link)
  2. Click the Cog icon in the top right corner of the screen, and select Internet Options.
  3. On the Security tab, select Local Intranet and click the Sites button.
  4. Untick Automatically dectect intranet network.
  5. Click the button Advanced and add the following entries to the exception list.
    1. http://*.cannonfodder.local
    2. http://*.cfapps.com
    3. http://cannonfodderser
  6. Click Close, Click OK.
  7. Now click on Trusted sites, click sites and remove http://cannonfodderser from Trusted sites. (Need to do this because we enabled Kerberos on Central Administration, when Automatically Dectect intranet network was untick, I discovered the http://cannonfodderser was added to trusted sites, and unfortunately when the URL is in trusted sites, Kerberos ingrated authentication does not work.

Configuring SharePoint 2013 for Hosting Apps.

I would recommend to copy the following powershell script and run it as a ps1 file.

  1. From the Start Menu, type SharePoint 2013 Management Shell.
  2. Run the Script.

    $appHostDomain = "cfapps.com"

$adminService = Get-Service -Name spadminv4

if ($adminService.Status -ne "Running")
{
Start-Service $adminService
}

$timerService = Get-Service -Name sptimerv4
if ($timerService.Status -ne "Running")
{
Start-Service $timerService
}

Set-SPAppDomain $appHostDomain

$appMgmtSvcInstance = Get-SPServiceInstance | Where-Object { $_.GetType().Name -eq "AppManagementServiceInstance" }

if ($appMgmtSvcInstance.Status -ne "Online")
{
Start-SPServiceInstance -Identity $appMgmtSvcInstance
}

$appSubSettingSvcInstance = Get-SPServiceInstance | Where-Object { $_.GetType().Name -eq "SPSubscriptionSettingsServiceInstance"}

if ($appSubSettingSvcInstance.Status -ne "Online")
{
Start-SPServiceInstance -Identity $appSubSettingSvcInstance
}

$appPoolSvcApps = Get-SPServiceApplicationPool -Identity "SharePoint Web Services Default"

$appSubSvc = New-SPSubscriptionSettingsServiceApplication –ApplicationPool $appPoolSvcApps –Name "Settings Service Application" –DatabaseName SP_SettingsServiceDB

$proxySubSvc = New-SPSubscriptionSettingsServiceApplicationProxy –ServiceApplication $appSubSvc

$appAppSvc = New-SPAppManagementServiceApplication -ApplicationPool $appPoolSvcApps -Name "App Management Service Application" -DatabaseName SP_AppServiceDB

$proxyAppSvc = New-SPAppManagementServiceApplicationProxy -ServiceApplication $appAppSvc

Set-SPAppSiteSubscriptionName -Name "app" -Confirm:$false
  3. To verify the script configured SharePoint 2013 correctly Open Central Administration.
    1. Under Application Management click Manage Service Applications.
    2. You should have two new service applications created.
      1. App Management Service Application
      2. Settings Service Application
    3. Now navigate to System Settings by clicking the link on the left menu.
    4. Under Servers click the link Manage Services on Server.
    5. Check that the following services have started:
      1. App management service
      2. Microsoft SharePoint Foundation Subscription Settings Service.
    6. On the left hand menu, click on Apps
    7. Under App Management, click the link Configure App URLs
    8. Verify that:
      1. App Domain: cfapps.com
      2. App Prefix: app

Your SharePoint server is now setup for apps. We will verify this in the next step.

Checking that Apps are now set up for your farm

  1. Open up your intranet site. http://intranet.cannonfodder.local
  2. At the top right of the screen Site Settings
    from SharePoint 2010 has been moved from the left back to the right (like SharePoint 2007) but now is a cog icon.
  3. Click the Cog Icon and select Add an App.
  4. On the App page, click SharePoint Store.
  5. First time you hit the page, you will get the error message that you need to select a language. In the top right select English (United States)
  6. If you have connected up correctly you will now see Apps that you can download from the SharePoint Store.
  7. Pick a free one to install. I’m picking myFAQ. Click on the Icon of the app.
  8. You now have the option to ADD IT. Click Add It.
  9. You will need to sign in with a Microsoft Account.
  10. Click Continue. To confirm you wish to add the App. Take note of the URL here, you are no longer in your SharePoint site.
  11. After you have click OK, your new app will start downloading, and you will be back in your site. The page will inform you that you have this app for everyone in your organization. Click Return to Site.
  12. A prompt will appear, asking if you trust the application. Click Trust It.
  13. After a moment you will be returned to your Site Contents. You will also note that your app that you downloaded is currently being added to your site.

    Once completed the adding text will disappear.
  14. Click on the App. It will load. Take note of the url. It is being called from the domain you created earlier cfapps.com. Congratulations you have got Apps working in your Development SharePoint 2013 machine.

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 6 – Installing SharePoint 2013

Posted on by

UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

Finally after 5 parts of setting up your virtual machine, we can now install SharePoint.

Windows Update.

Ensure your Server is up to date. I have attempted to install the SharePoint 2013 prerequisites twice now trying to write this blog. I found by ensuring all updates were install on the server before installing SharePoint 2013 I had more success.

Each time I got errors when installing the prerequisites. All I did was just run the prerequisites again, 3 times in total before I got a successful installation message.

Installing SharePoint Server 2013 Prerequisites

Select the SharePoint 2013 ISO in the Virtual Machine Settings.

  1. Run splash.hta
  2. Click the Install Software Prerequisites link.
  3. In the Microsoft SharePoint 2013 Products Preparation Tool dialog, click Next.
  4. Accept the License Terms,
    and click Next.
  5. The prerequisites for SharePoint 2013 will be installed and set up. When it has completed, you might need to reboot the machine. Please note I had to try installing the prerequisites 3 times before it fully worked. Each time I got an error message saying something could not be installed properly. But by running it again, it passed the first error and then had another. I kept running it until I had no more errors. I’m not 100% sure why this happened, but it did sort itself out. Click Finish.

  6. Although all prerequisites required by SharePoint 2013 are installed, Microsoft recommends you installing the following hot fixes if not already installed.
    http://go.microsoft.com/fwlink/p/?LinkID=268725 – .Net Framework 4.5 that resolves an ASP.NET Race Condition Issue in Windows 8, Windows RT, and Windows Server 2012.

     

Installing SharePoint Server 2013

  1. Run splash.hta
  2. Click Install SharePoint Server.
  3. When prompted Enter your Product Key. Click Continue
  4. Accept the License terms. Click Continue.
  5. Accept the default file location (Unless you have reason not to). Click Install Now.
  6. When it has finished. Run the configuration wizard by clicking Close.
  7. On the Welcome to SharePoint Products click Next >.
  8. Accept the dialog warning that services may have to be started or reset during configuration.
    Click Yes.
  9. On Connect to a server farm, select Create a new server farm. Click Next >.
  10. On the Specify Configuration Database settings
    1. Database Server: SQL2012
    2. Database name: SharePoint_Config
    3. Username: cannonfodder\SP_Farm
    4. Password: Pa55w0rd
      Click Next.
  11. On Specify Farm Security Settings put the Passphrase as Pa55w0rd. Click Next >.
  12. On Configure SharePoint Central Administration Web Application tick Specify port number. Type in the number 10000. Select Negotiate (Kerberos) for security settings. Click Next >. Accept the warning about choosing Kerberos. You will set up the SPN later.
  13. On the final page Completing the SharePoint Products Configuration Wizard it will display a summary of what you have selected. Click Next >
  14. When the installer has finished, you will be presented with Configuration Successful. Click Finish. Internet explorer will open Central Administration allowing you to complete the installation.

     

Configuring SharePoint 2013

First thing we should do is set Kerberos SPN for Central Adminsitration.
Note: On a single machine like the one we are building, there is no real need to use Kerberos. Kerberos helps us get over the double hop issue. However, you never know if you will use multiple servers in the future, and it’s not too much work to enable Kerberos. Also another skill to learn.

  1. Open a Command prompt in Administrative mode.
  2. Type setspn –S HTTP/cannonfodderser:10000 cannonfodder\SP_Farm
    setspn –S HTTP/cannonfodderser.cannonfodder.local:10000 cannonfodder\SP_Farm
  3. To ensure it has been set up type setspn –L cannonfodder\SP_Farm

Now we will continue configuring SharePoint in the browser.

  1. Open up a web browser (if not already open) and browse to http://cannonfodderser:10000
  2. At the bottom of the home page of central admin click the Configuration Wizards

    Now most of the time when I’ve created SharePoint machines in the past, I’ve never used the Configuration wizard, I like to set up each service one at a time. However for simplicity, I’m going to use it this time. I will write further blogs in the future (hopefully) that will show you how to set up a given service from scratch.
  3. On the Configuration Wizards page, click Launch the Farm Configuration Wizard.
  4. On the Welcome page, click Start the Wizard.
  5. On the Services page, select Create a new managed account.
    1. Put the UserName as cannonfodder\SP_Services
    2. Password as Pa55w0rd
    3. Untick Access Services 2010 and App Management Services. The reason for this is because Access Services 2010 is included for backward compatibility and isn’t needed in new installations unless you are migrating solutions using Access Services 2010 from SharePoint Server 2010. The App Management will be created manually later in the next blog post.
    4. Click Next. This will take a long time to process.

There you have it, SharePoint 2013 installed on your machine. There are still some steps to set up, which I will discuss in the next few blogs.

  • Hosting Apps
  • My Sites and User Profiles
  • Workflow

Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 5 – Configuring SQL 2012 Ready for SharePoint 2013

Posted on by

UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

When I started planning the 10 parts of the blog, the one bit I forgot about was Kerberos. So I have squeezed part of it in here. As I am a developer and not really an IT-Pro I had to look up information on the web to help me write this bit on Kerberos and speak to the IT Pro at my work. My references are blksthl blog and my work colleague Adam McEwen, who blogs you can access via these links.

Creating the Accounts required.

First we need to create 4 different accounts.

SP_Farm – SharePoint Farm Account

SP_Content – SharePoint Content account for the Content Databases.

SP_Services – SharePoint account for the Shared Services within SharePoint.

SP_SQL – The account to run SQL with.

  1. In the Start Menu, type Active Directory Users and Computers. Select the application.
  2. Expand the tree in the left hand pane to see the Users OU. Select the Users OU.
  3. Right Click on User and select New > User. Create a new user called SP_Farm. Set the Full Name and Log on name to SP_Farm. Click Next.
  4. In the password dialog screen, enter the following and click Next.
    1. Password and Confirm Password as: Pa55w0rd
    2. Untick User must change password at next logon.
    3. Leave User cannot change password as unticked.
    4. Tick Password never expires
    5. Leave Account is disabled as unticked.
    6. Click Next. Then click Finish.
  5. Repeat the steps 1-4 for the remaining accounts (SP_Content, SP_Services and SP_SQL).

Setting up Kerberos for SP_SQL account.

We will need to set up Kerberos for the other accounts, but this section of blog is getting your SQL ready for SharePoint 2013. Therefore at this point we will just set SQL up for Kerberos.

Name Resolution.

  1. In the Start Menu, type DNS. Open the application to the DNS Manager.
  2. Expand the forward lookup zones container in the left panel.

  3. Right click on the zone cannonfodder.local and click on a New Host (A or AAAA).

  4. Type in the name of the record. In this case we are going to name our SQL Server SQL2012. Set the IP address at the IP of the machine. We set this to a static IP in the last blog. (If you have forgotten you can find out by bringing up a command prompt and type ipconfig /all and look at the IP4 IP address.) Click on Add Host.

  5. Click on Done. You will then get a verification dialog, and after click OK to that, you will see the record has been created in the right pane of the DNS manager.
  6. To check that this is all working, open a command prompt, and type
    ipconfig –flusdns

    Then type

    Ping SQL2012

Service Principle Name

  1. Open a command prompt from the Start Menu by typing in cmd. Right click Command Prompt and along the bottom of the screen will be an option to Run as Administrator.
  2. Type the following in the command window. This will create the SPN for the service account paired with the host name.
    setspn –S MSSQLSvc/SQL2012:1433 CANNONFODDER\SP_SQL
  3. Type the following in the command window. This will create the SPN for the service account paired with the FQDN.
    setspn –S MSSQLSvc/SQL2012.cannonfodder.local:1433 CANNONFODDER\SP_SQL
  4. Now by typing in setspn –L CANNONFODDER\SP_SQL it will list all the SPN for that account.


Trust for delegation

As our server is a domain controller we do not need to set it up so that it is Trusted for Delegation. We can prove this by doing the following.

  1. From the Start Menu type Active Directory Users and Computers. Open the application.
  2. In the left hand panel, expand cannonfodder.local and select Domain Controllers.
  3. In the right hand panel you will see the computer CANNONFODDERSER.
  4. Right click this computer and select Properties. From the properties window, select the Delegation tab. As you can see this computer is already set to Trust this computer for delegation to any service (Kerberos only).

Configuring SQL Server 2012

As SQL was installed using a built in account, and also installed on the machine before it was sysprepped, SQL now needs to be configured to work properly on this server in preparation for SharePoint.

  1. From the start screen type SQL Server Configuration Manager and select the application.
  2. Click to expand SQL Server Network Configuration (not the 32 bit), and choose Protocols for MSSSQLServer, and ensure TCP/IP and Named Pipes are enabled. To enable them right click them and select Enable. Click OK at the warning.
  3. Now in the left hand pane, click SQL Server Services.
  4. For SQL Server (MSSQLSERVER) right click the service name and choose Properties.
  5. Select the Log On tab.
  6. Select this account: radio button and enter cannonfodder\SP_SQL and enter the password as Pa55w0rd. Click Apply, and Yes to restart the service, or Start the service if not already.
  7. Click OK and close SQL Server Configuration Manager.

Now we need to give cannonfodder\administrator access and update SQL Server 2012 local instance after the machine name has been changed.

  1. From the start screen type SQL Server Management Studio and select the application.
  2. Change the server name to SQL2012 and logon using SQL Authentication with the sa account using the password Pa55w0rd. If you try to log in at the moment as cannonfodder\administrator using windows authentication, you will fail to access SQL.
  3. Now give cannonfodder\administrator the correct security access.
    1. Expand Security and right click Logins to select New Login…
    2. Next to the Login Name click Search
    3. Type cannonfodder\administrator, and then click check names. Select the user administrator, not the group.
    4. On the left hand panel, select the Server Roles page, and tick sysadmin. Click OK
    5. Right click the database connection in Object Explorer and choose disconnect.
    6. Click Connect in the Object Explorer, choose database engine, and connect to SQL2012 using Windows Authentication, then confirm you can browse objects in the database server.
  4. Now we need to update the server name. If you Click New Query and type
    
Select @@SERVERNAME

    You will notice that the server name is incorrect.

    Click New Query and copy the script

    
sp_dropserver @@SERVERNAME
GO
sp_addserver 'CANNONFODDERSERVER', local
GO

    run the query.

  5. Restart the SQL server service, right click the SQL Server service, right click the database connection in Object Explorer, and choose Restart. You will then get a prompt asking if you want to restart the MSSQLSERVER service. Say Yes.

  6. Right click the database connection again, and choose disconnect.
  7. Click Connect to SQL2012 using Windows Authentication.
  8. Click New Query, and run the following script to confirm the instance name has been changed to reflect your chosen machine name:
    
Select @@SERVERNAME

  9. You can now close SQL Server Management Studio. No need to save the queries.

Now we are past the half way point, and we can now finally start installing SharePoint 2013!