THE ART OF INSTALLING SHAREPOINT 2013 IN A 3 TIER TOPOLOGY- PART THREE
So you’ve got your Active Directory Server up and running and SQL server 2012 is configured and good to go. If not see my previous posts for how to go about this Lets install SharePoint 2013 on your Web server. One thing to note is that my web server on which I am installing SharePoint 2013 will also act as my application server. My environment is not for client use as of yet so I don’t need a separate application server. If you have a client requirement for this type of topology, then by all means separate it out.
First the Requirements…
- You have an active and fully configured Active Directory.
- You have a SQL 2012 Server fully updated and configured, with the correct permissions set up for SharePoint required service accounts. See my previous post for this.
- You have all your service accounts created in Active Directory, I’ll cover this below.
- All servers in the topology are connected to the same domain.
- Your web/application server on which you are installing SharePoint 2013 has all required software and updates applied.
This post assumes you have all the above sorted before you install SharePoint 2013. Remember I am using the hyper V service to manage my servers and they are all running on a Server 2008 Guest OS.
Service Accounts
Why do we need these service accounts? Let’s thing separation of data. When it comes down to the nitty gritty and there needs to be “physical” boundaries between data you’ll want to use different service accounts. Think about search content access, user profile data etc. Custom Database Names
is a roundabout way pro for using separate service accounts and really is a point towards not using the Service Application wizard. It goes hand in hand that by not using the wizard you can use your own service account for the application and therefore being able to name the databases that get created when configuring specific Service Applications. When not using the wizard and using your own service accounts it lets you dictate what names most Web Apps are called as well as what services run under them. Call it a control thing! Separate service accounts mean multiple points of redundancy. Just as multiple accounts could be failure points. They are also redundancy levels. Think if you had all your services running under the same service account. What if that account went bad, password expired etc. All your services go down. Now think if you had all your proper service accounts structured out maybe just search goes down but the rest of your farm and access to its features is still up.
is a roundabout way pro for using separate service accounts and really is a point towards not using the Service Application wizard. It goes hand in hand that by not using the wizard you can use your own service account for the application and therefore being able to name the databases that get created when configuring specific Service Applications. When not using the wizard and using your own service accounts it lets you dictate what names most Web Apps are called as well as what services run under them. Call it a control thing! Separate service accounts mean multiple points of redundancy. Just as multiple accounts could be failure points. They are also redundancy levels. Think if you had all your services running under the same service account. What if that account went bad, password expired etc. All your services go down. Now think if you had all your proper service accounts structured out maybe just search goes down but the rest of your farm and access to its features is still up.
With the new feature of managed accounts in SharePoint 2010 we can now set credentials and forget about them. We can now set SharePoint to manage the passwords of our Service Accounts (yes that can be scary) but some of that risk is taken out of needing to worry about the passwords. Least Privileges basically means that you can manage and control the exact level of permissions that SharePoint can operate under. Search on “SharePoint Least Privileges” it will give you a good understanding of just how lean you can run SharePoint and still have all things work correctly. Ok let’s vamoose…
You need at least the following service accounts created in AD to successfully install SharePoint 2013:
SQL Server Service Account, e.g. sqlSvcAcc (If you have been following my previous posts, this has already been created and assigned permissions on the SQL server)
SharePoint Setup Administrator, e.g. spAdmin
SharePoint Farm Account, spFarmAcc
In SharePoint 2013 these accounts will fall under the managed accounts where you control the ability for passwords to expire or whether users cannot change their passwords. I always use in my development environment the options “User cannot change password” and “Password never expires”.
SQL Server Service Account
Permission are assigned automatically during installation of SQL Server 2012. The SQL Server service account should be a domain account and is used to run SQL Server.
SharePoint Setup Administrator
You need to manually assign permissions for this account. The setup administrator is used to install SharePoint 2013. The SharePoint 2013 setup administrator has to be a member of the administrators group on every server SharePoint should be installed. This account also needs the securityadmin and dbcreator and sysadmin (If creating a development environment so you can have only 1 account to administer Windows Server, SQL Server and SharePoint) role in SQL Server.
Farm Account
Permissions are automatically assigned by the SharePoint 2013 setup administrator so you don’t have to do it.
The farm account is used for the following things [1]:
“Configure and manage the server farm.”
“Act as the application pool identity for the SharePoint Central Administration Web site.”
“Run the Microsoft SharePoint Foundation Workflow Timer Service.”
See the Microsoft site for recommendations for service accounts: http://technet.microsoft.com/en-us/library/ee662513.aspx
In addition to the main accounts you need a separate account for each service application you intend to run as well as:
Application pool account
The application pool account is used for application pool identity. The application pool account requires the following permission configuration settings:
The following machine-level permission is configured automatically: The application pool account is a member of WSS_WPG.
The following SQL Server and database permissions for this account are configured automatically:
- The application pool accounts for Web applications are assigned to the SP_DATA_ACCESS role for the content databases.
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role associated with the farm configuration database.
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role associated with the SharePoint_Admin content database.
Default content access account
The default content access account is used within a specific service application to crawl content, unless a different authentication method is specified by a crawl rule for a URL or URL pattern. This account requires the following permission configuration settings:
- The default content access account must be a domain user account that has read access to external or secure content sources that you want to crawl by using this account.
- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites.
- This account must not be a member of the Farm Administrators group.
Content access accounts
Content access accounts are configured to access content by using the Search administration crawl rules feature. This type of account is optional and you can configure it when you create a new crawl rule. For example, external content (such as a file share) might require this separate content access account. This account requires the following permission configuration settings:
- The content access account must have read access to external or secure content sources that this account is configured to access.
- For SharePoint Server sites that are not part of the server farm, you have to explicitly grant this account full read permissions to the web applications that host the sites.
Excel Services unattended service account
Excel Services uses the Excel Services unattended service account to connect to external data sources that require a user name and password that are based on operating systems other than Windows for authentication. If this account is not configured, Excel Services will not attempt to connect to these types of data sources. Although account credentials are used to connect to data sources of operating systems other than Windows, if the account is not a member of the domain, Excel Services cannot access them. This account must be a domain user account.
My Sites application pool account
The My Sites application pool account must be a domain user account. This account must not be a member of the Farm Administrators group.
The following machine-level permission is configured automatically: This account is a member of WSS_WPG.
The following SQL Server and database permissions are configured automatically:
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the farm configuration database.
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the SharePoint_Admin content database.
- The application pool accounts for web applications are assigned to the SP_DATA_ACCESS role for the content databases
Other application pool accounts
The other application pool account must be a domain user account. This account must not be a member of the Administrators group on any computer in the server farm.
The following machine-level permission is configured automatically: This account is a member of WSS_WPG.
The following SQL Server and database permissions are configured automatically:
- This account is assigned to the SP_DATA_ACCESS role for the content databases.
- This account is assigned to the SP_DATA_ACCESS role for search database that is associated with the web application.
- This account must have read and write access to the associated service application database.
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the farm configuration database.
- This account is assigned to the WSS_CONTENT_APPLICATION_POOLS role that is associated with the SharePoint_Admin content database.
FYI the database roles mentioned above are created automatically during installation.
You will need additional accounts for each additional service application you install, see here for the Microsoft best practice plan for service accounts:
It’s impossible to define a real set of service accounts that could fit any scenario, from a small development farm to a huge multi-tier farm. Each environment is different and will require its own customised set of service accounts. The Microsoft best practices link is very detailed, but you need to use your initiative to decide, based on your requirements, which accounts to use and which not to use.
Ok let’s install SharePoint 2013:
Make sure you are logged on using the SharePoint Setup Administrator.
The installer will also configure the Windows Server Application Server and Web Server role.
The installer will also configure the Windows Server Application Server and Web Server role.
I used this as a reference: http://technet.microsoft.com/en-us/library/ee805948.aspx
Run the installation application and you will be presented with the following screen (Excuse the quality of the images, I will get better ones and replace as soon as I can):
Click on the Install software prerequisites link to automatically install all the pre required software.
After the Install, the system needs to reboot. When this is done, start up the installation again and select to install SharePoint 2013:
Enter your License Key, Accept Microsoft’s terms and conditions and choose to perform a complete install:
Once the Installation is completed, close the installation wizard. Select the check box “Run the SharePoint Products Configuration Wizard now” (default).
You will be presented with notification of services being restarted during the configuration:
Select to create a new server farm:
Enter the appropriate information. Be careful of using the correct server names. I kept getting a permission error when trying to create the farm. It look hours of investigation to realise that I was using the incorrect database name for my SQL server. My database server was called SP2013DatabaseServer but its FDQN was SP2013DBServer, thus I was getting permissions issues as there was no server with that name. Good old SharePoint, always giving us uninformative error messages! I had to use the IP address in the end to get it to work.
Enter a passphrase and now it down.
Pick your Central Administration Settings:
Double check your configuration:
Configuration proceeds:
Hopefully not after too many grey hairs you should have a successful configuration:
Then a browser window will open with the following page, select to ‘Start the Wizard’ to configure the farm:
You will be asked to select the services you require to run in the farm as well as the service account. You can create a new one (needs to be in AD first) or select from the list but you can only select one for all of the services. I had to go back and manually change the service accounts for each of the service applications…boring!:
Notice some new faces in the service applications?
Then we see this screen with the words which will become both an annoyance and a joy for you as you will be bombarded with it, at least they are apologising now:
If everything is successful you will get this screen:
And voila, your farm is created… now go create a web application and site collection and have a play! Good luck.
Next I will try to automate the install and config of SharePoint 2013 using Powershell for multiple server farm… exciting I know. Powershell and I have a fractious relationship as I don’t like dark screens, I’m a girl I like bright pretty things, but the new Powershell commands for SharePoint 2013 are doing their job in making my life much simpler, so I can handle a simple life, even though I have to occasionally use a black screen!
FYI If you followed these instructions you might not get internet access on your DB and Web servers. What happens is that when you configure your AD Forest, Windows 2012 automatically expects all Internet traffic should be rerouted to this domain and that the domain is able to serve as a gateway to the Internet, meaning the domain can (or will later) have a DNS Server. My guest OS is using a wireless connection which is shared between all the servers, when connecting the DB and web servers to the domain you have to enter an IP address as well as a subnet mask and connect your DNs server (AD server). Doing this immediately blocks the internet. I have yet to configure the AD server to route internet connections, and when I do I will post the solution or you can research it, if you require your servers to have internet access. I don’t require internet access as I want control over the windows update service. I’m not a DNs expert so will have to consult the experts on this.
That’s all for now, wow 3 posts in one day..
Peace Love and Happiness!
THE ART OF INSTALLING SHAREPOINT 2013 IN A 3 TIER TOPOLOGY – PART TWO
Installing and Configuring SQL Server 2012
The plan is to install and configure SQL Server 2012. This blog post is a part 2 to my installing SharePoint 2013 so let’s go..
Just to recap, I’m installing SQL server 2013 Standard on Windows Server 2012 OS. I’m creating my server using Windows Hyper V service on a guest OS as Windows Server 2008 R2 with 3GB and 80GB on a 64 bit processor as hardware specifics. Things to note include:
- Do not try to install SQL Server 2012 on a compressed, encrypted or read-only drive, because setup will block the installation.
- Do not install SQL Server on a Domain Controller.
- Verify Windows Management Instrumentation service (Control Panel -> Administrative Tools -> Services) is running.
- The user account that is going to be configured to run SQL Server Setup must have administrative privileges on the computer.
- Enable .NET Framework 3.5 (http://www.sqlcoffee.com/Troubleshooting101.htm).
- Make sure your server has internet access to download all the latest updates. I had a problem with internet connection and connection to my domain. Enabling DHCP (required for internet access) ‘detaches’ the server from the domain as it changes the internet settings for that server (IP v4 settings for the network connection adapter) to automatically assign IP addresses and DNS (Dynamic settings). To add the server to the domain you simply change the IP, Subnet Mask, DNS server address in the adapter settings to static addresses, which means they don’t change. I haven’t resolved this yet but research points to creating DNS forwarders to resolve, but I don’t want internet access on my servers once it is set up so this doesn’t bother me for now. I will resolve it one day when I get around to it and will blog about it.
- Identify drives to which the databases and/or logs will be backed up, ensuring that there is enough disk space to accommodate the backups for the retention period that you choose.
- Create dedicated service account for each of the service to be installed. Ensure that these accounts are not member of Local Administrator because it will give unnecessary rights to these accounts. Note: for the purpose of this tutorial I’m using local system accounts as a service start-up accounts. Assign Deny logon locally right to these service accounts.
- Choose the port number for you SQL Server installation because common TCP\IP ports 1433/1434 ports are well known and are common target for hackers. Therefore it is recommended to change default ports associated with the SQL Server installation.
Ok so we are ready, let’s do this!
Run the setup from the installation media. I used Hyper V, so I attached the installation image to the DVD Drive so it appears as the dvd drive on the server.
Under Installation, choose a New SQL Server stand-alone installation.
You will be presented with a Setup is now preparing to launch Setup Support Rules window:
Now Setup Support Rules will run to identify problems that may occur during the Setup Support Files installation. If I had ended up with any “Failed” items I would not have been able to proceed without resolving them. If you don’t have any errors continue on with the next step in the installation process by clicking on the “OK” button, otherwise click the failed links to resolve the issues.
Next choose between an evaluation version or enter your product key to install your required version:
In the License Terms window, tick the box to accept the license terms and then click Next to continue and install the set up files:
Click Next to install set up files:
By default the SQL Server 2012 installation will look for product updates using the client Windows Update service. The “Checking for Updates…” progress bar shows when it is searching for updates. If you don’t want to search for updates uncheck the “Include SQL Server product updates” checkbox and then click on “Next >” to proceed with the installation process, which installs the updates.
Access to the Internet is required, since SQL Server setup will try to get updates for SQL Server during installation. If the computer does not have access to the Internet and Windows Update service, then you may get the above error message:
“SQL Server Setup could not search for updates through the Windows Update service. You can either check again or click Next to continue. To troubleshoot issues with your Windows Update service, view the link below ensure you have Internet or network access, and ensure your Windows Update service can find updates interactively through the Windows Update control panel
Error 0×80240042: Exception from HRESULT: 0×80240042.”
These files are necessary to perform the actual installation. Following the installation of the setup support files, you will be presented with another compatibility check. Following dialog appears once you successfully pass these checks.
The warning message above refers to a firewall warning. You can go ahead with the installation of SQL Server, but when it finishes configure your Windows Firewall to allow SQL Server access or disable it. See here to set that up: http://msdn.microsoft.com/en-us/library/cc646023.aspx
Now we need to assign this server a role. Select SQL Server Feature Installation option and then Next to continue to Feature Selection page.
I selected all features to install the Database Engine Services, Analysis Services, Reporting Services, and a number of shared features including SQL Server Books Online. You can also specify the shared feature directory where share features components will be installed. I left all other defaults in there. Click Next to continue to the Installation Rules page, Setup verifies the system state of your computer before Setup continues:
Click Next to continue to the Instance Configuration page. Each server machine can host one default instance of SQL Server, which resolves to the server name, and multiple named instances, which resolves to the pattern ServerName\InstanceName. Then you need to specify if you are going for a named instance or the default.
On this occasion I used a named instance, but the default is fine too. If there are already an instances on the machine, they will be named here too. Then click Next to proceed to the Disk Requirements Page:
Click Next to go to Server Configuration page:
Here you specify service startup and authentication credentials. Microsoft recommends that each service account have separate user accounts as a security best practice as shown in the following figure:
The SQL Server 2012 Books Online makes the following security recommendations:
Run separate SQL Server services under separate Windows accounts.
Run SQL Server services with the lowest possible privileges.
Associate SQL Server services with Windows accounts.
Require Windows Authentication for connections to the SQL Server.
I specified my SQL Service Account to run the SQL Server Agent and the SQL Database Engine and kept all the default collation settings. I would suggest that if you plan to install a number of SQL Server instances you consider installing all of them with the same collation. This will minimize the collation issues you will have when comparing data across databases and instances. Clicking next takes you to the Database Engine Configuration:
Note that there are three different tabs on this window: Server Configuration, Data Directory, and FILESTREAM. On the first tab, “Server Configuration”, I need to identify the “Authentication Mode” that SQL Server will use for my installation. There are two choices for authentication, “Windows” and “Mix Mode”. If I select Windows only, then all logins that need to connect with my SQL Server instance will need to be Windows accounts. If I select “Mixed Mode” then I can have both Windows and SQL Server authenticated logins. I typically select “Mixed Mode” so I can have the flexibility of using both account types, but I typically require all applications to connect using Windows Authentication if possible. I do this because I have found a number of third party applications that still do not support Windows authentication. If I specify “Mixed Mode” I am also required to set a SA password. Additionally on this tab I can add the Windows logins that I want to be placed in the sysadmin role by using the “Add Current User” or “Add…” buttons at the bottom of this window.
I also added the current Admin and Set Up admin accounts as administrators.
Use the “Data Directories” tab on the “Database Engine Configuration” page to change the default location for data directories. On this window I can specify the location for each of the different database components. With SQL Server 2012, Microsoft has given me more options on where to place the different data components. I now have options for where I want the user database, temp databases and backup components to reside. This allows me to separate my components across different disk drives to help optimize the disk layout of my SQL Server components across my I/O subsystem. I left the defaults in there.
By default FILESTREAM is disabled. FILESTREAM feature is quiet useful when binaries or other data that does not fit neatly in a table structure. To enable it all I would need to do is check the checkbox labelled “Enable FILESTREAM for Transact-SQL access”. If I check this box the “Enable FILESTREAM for file I/O access” checkbox becomes available. If I decided to check this box Windows will be able to access the files store in the windows share. I can use the “Windows share name” to identify the Windows file share name that will be used access the file stream data. If I also want to allow remote clients to be able to access the FILESTREAM datasets then I would also want to check the checkbox labelled “Allow remote clients access to FILESTEAM data”. For my installation I will not be enabling FILESTREAM, so I will not be checking any of these boxes. If I find I need FILESTREAM later I can always enable it. If you plan to use RBS you need to enable FILESTREAM for Transact-SQL access and FILESTREAM for file I/O.
Once I had configured all three tabs on the “Database Engine Configuration” window I can then click on the “Next >” button, which will bring up the following window:
Select “Install Analysis Services in Multidimensional and Data Mining Mode” to install Analysis Services with support for online analytical processing databases and data mining models. Or select “Tabular Mode” to install Analysis Services with support for tabular models. Each mode is exclusive of the other. Pick an administrator. I created an AD account for Analysis services to run and used this account as the Admin. Analysis services I required for Business Intelligence features to work in SharePoint 2013.
In the Data directories Tab, I left the defaults as is. Clicking next brings up the Reporting Services Configuration window:
I chose the above settings, for more info on there see here: http://msdn.microsoft.com/en-us/library/ms144292.aspx
If you selected to install the Distributed Replay Controller feature, then the above window presents you with options to configure it. I created an AD account to administer this and inserted it here. Distributed Replay Client Configuration page appears next:
Here I entered the Domain Controller name, the machine I was working on, and left the defaults for directories.
On 32-bit computers, the default installation path is C:\Program Files\Microsoft SQL Server\
On 64-bit computers, the default installation path is C:\Program Files (x86)\Microsoft SQL Server\
Click Next to advance to Error Reporting page, tick the check box if you want to send Windows and SQL Server error reports to Microsoft:
Click Next, then the System Configuration Checker will run some more rules that will validate your computer configuration with the SQL Server features you have specified. This window will verify that the installation has no failures. If I did have failures I would need to resolve them prior to proceeding.
Click Next, and on the “Ready to Install” window I can review all of my installation settings. This page shows a tree view of installation options that were specified during Setup. On this page, Setup indicates whether the Product Update feature is enabled or disabled and the final update version. I can use the slider bar on the right to move up and down so I can review all the options. If I need to change any options I can use the “< Back” button to go back and change installation settings. After I review all my installation settings are correct, I click the “Install” button to install SQL Server 2012. The Setup will first install the required prerequisites for the selected features followed by the feature installation. The installation process pops up the following “Installation Progress:” window:
If installation succeeds the next window will display:
Then you’re done. I would then fire up Configuration Manager and start all my required services. Also enable all 3 protocols for SQL Server Network Configuration, also in configuration manager (Restart of services required). Don’t forget to enable SQL Server Browser service if you installed a named instance of SQL Server.
Log into SQL Server Manager and add and assign your SharePoint Set up account (Spadmin) permission roles in the database: DBCreator, SecurityAdmin, and SysAdmin
If you have any problems during installation or error messages you can’t figure out, I used this site to help decipher them:
Now you should be ready to install SharePoint 2013 in the next part…
THE ART OF INSTALLING SHAREPOINT 2013 IN A 3 TIER TOPOLOGY – PART ONE
Ok, so you’re a support person/ newbie/ trainee SharePoint guru, and you have been asked to install SharePoint 2013 with the following topology or similar:
Now SharePoint 2013 is similar to 2010 but they are very different. Although this topology is quite rare, I had to re-create it for my app development, architecture and POC creation, and I’m going to take you through the steps of creating it from scratch. I’m going to assume this is your first SharePoint installation, so all the gurus out there, be patient! It could be a long post so I might put some links to the same information I used for reference to help me complete some of my tasks. There’s a lot of info out there on installing SharePoint 2013 (SP2013 from here on in) so by all means, have a gander and design your own custom installation solution using different aspects of others as I have done.
First off please read and understand the hardware and software requirements for SP2013, they are very important, the nature of the beast is that SharePoint is getting more splendid and all these beautiful features require more and more memory.
http://technet.microsoft.com/en-us/library/cc262749.aspx – this is a good link to read to get you thinking about browser and IP support as well as software boundaries, limits and capacity management. Before installing SharePoint 2013, you need to really understand what it is you are doing, it will save many days of frustration and prevent many grey hairs! Ok, so here we go…
Hardware RoadMap
I created all of this on a machine with 16GB RAM, my OS was Server 2008 r2 with Hyper V role installed. All servers are on 64 bit processors.
My plan for memory allocation was as such:
AD Server – 2GB Ram and 80GB Hard drive On 64 bit processor
Database Server – 3GB and 80GB Hard drive (8GB Ram usual for SP2013 but I have used 3 and not suffered any repercussions yet, you can always increase this if the need arises especially if you are using Hyper environments) On 64 bit processor
SharePoint Server – 8GB and 80GB hard drive (Microsoft recommends at least 12 GB for production deployments but really, I think they are being overly cautious because of performance issues (Page Loads etc.) encountered with SharePoint 2010. I work with my 8GB just fine, no problems yet, but this can always be increased if required). On 64 bit processors
I created all these hyper V servers using my Hyper V manager on my guest OS. See these 2 links to create a virtual machine from a guest OS (Windows Server 2008 R2 in my case):
The next links helped me understand the different network options available in Hyper V and how basic networking in Hyper V environments work:
http://blogs.technet.com/b/jhoward/archive/2008/06/16/how-does-basic-networking-work-in-hyper-v.aspx
One other very important step is providing internet access to your machines once you have created them. I was connecting to the internet on my guest OS using a wireless connection and used the following link to facilitate that:
Software RoadMap
My software list is as follows:
AD Server – Windows 2008 R2 with AD Services role installed. I used the following link to help with setting up my domain and promoting my server to be a domain controller:
To install the OS once I had created my hyper V machine was to attach the installation media, i.e. point Hyper V to where your Windows Server 2008 r2 installation media is on your guest OS. Don’t forget to install DHCP, WINS and Enterprise Certificate Services.
*Note Before I installed the AD role on the server I update the machine with the latest service packs and updates as the Domain controller is not really meant to have any internet access for security reasons.
SQL Server – Windows Server 2012 and SQL Server 2012 standard (No longer enterprise version of Windows now, only Standard and DataCenter).
I used this link to help me set up Server 2012 and add it to my domain (Created on the domain controller):http://www.petri.co.il/installing-windows-server-2012-rc.htm
The process of installing SQL is quite laborious so I will help you through that one in the next blog post. Don’t forget to install updates after you have installed all your required software.
SharePoint Server – Windows Server 2012, SharePoint Server 2013, Visual Studio 2013, Office 2013, SharePoint Designer 2013, and any other Dev tools you usually use. I included ULS viewer and CSK Dev Visual Studio tools from Codeplex, SP2013 Client Component Tools SDK (http://www.microsoft.com/en-gb/download/details.aspx?id=35585), and whatever else you might use for your development machine.
So I knew I had a big task ahead of me to set this all up, so I made a list of all my required tasks and it looked something like this:
- Create, install and configure AD Server and Domain and create Service and Farm accounts (See SharePoint installation blog post for a list of these)
- Create, install and configure Database Server
- Install Server 2012 and configure
- Install SQL Server 2012
- Add SharePoint Admin and Farm account to Database server and apply correct perms (Spadmin needs DBCreator and Security Admin permission as well as an admin on the SQL and SharePoint servers). See here (http://technet.microsoft.com/en-us/library/ee662513.aspx) and here (http://technet.microsoft.com/en-us/library/cc678863.aspx)
- Set Up Max degree of parallelism (http://technet.microsoft.com/library/ms181007.aspx) and some info here (http://pwconsultant.blogspot.co.uk/2012/12/sharepoint-2013-and-sqls-max-degree-of_354.html)
- Configure SQL Server Security (http://technet.microsoft.com/en-us/library/ff607733.aspx)
- Create, install and configure SharePoint 2013 Server
- Set up server with Web server and Application server roles
- Install and configure SharePoint 2013
- Install and configure Visual Studio 2013, Office 2013, SharePoint Designer 2013, ULS Viewer and other software
- Configure Managed Accounts and set up logging, email etc
- Set Up AD synchronisation
- Download and install SP2013 Client Components SDK
- Update all servers
- Backup all servers and create future backup schedule
- Pour a much needed Long island Ice tea and assume the recovery position! Lol that’s optional!
Ok so for part 2, I’m gonna assume you have your own plan ready to go, and you have an AD server with a working domain. Ok Lets install and configure SQL 2012
Comments
Post a Comment