This article details the steps I took to install Microsoft SQL Server 2008 SP2 Enterprise Edition, Analysis Services, and Reporting Services were installed on a Windows 2008 R2 SP1 VM, with 8 CPU's, and 32GB Ram, for use by the Symantec Management Platform (SMP). I included MSSAS and MSSRS because I will be installing ITAnalytics (ITA) in my environment. This server is dedicated to SMP so we have no worries about other applications on this SQL server. These steps worked flawlessly for me, but should be reviewed with your Database Administrator(s) first to ensure they will work for your environment. Some steps may be modified based on your requirements, so please keep that in mind when reading through this article.
2. Configure OS
2.1. Login to the server.
2.2. Add the following users to the Administrators group on the server.
· You (as the installer)
· Altiris Application Identity
2.3. OPTIONAL: Modify the User Account Control settings
2.3.1.Click Start | Control Panel.
2.3.2.In Control Panel, click User Accounts.
2.3.3.In the User Accounts window, click Change User Account Control Settings.
2.3.4.Move the slider down to the bottom Never Notify me when:.
2.4. OPTIONAL: Disable the Windows Firewall
2.4.1.Click on Windows Firewall with Advanced Security in the left pane of Server Manager.
2.4.2.Click on Windows Firewall Properties in the right pane of Server Manger.
2.4.3.Change the Firewall state to Off on the Domain Profile Tab.
2.4.4.Change the Firewall state to Off on the Private Profile Tab.
2.4.5.Change the Firewall state to Off on the Public Profile Tab.
2.5. OPTIONAL: Disable IE ESC
2.5.1.In Server Manager, click on Server Manager in the left pane of the Server Manager.
2.5.2.Click on Configure IE ESC in the right pane.
2.5.3.Check Off for the Administrators and Users then click OK.
3. Install OS Features
3.1. Install WCF, .NET, IIS
3.1.1.In Server Manager, click on Features in the left pane.
3.1.2.Click Add Feature in the right pane.
3.1.3.Check WCF Activation under .NET Framework 3.5.1 Features and click Next.
3.1.4.Click Add Required Role Services in the window that pops up.
3.1.6.Check the boxes for the following items, and then click Next.
3.1.8.When done, review and correct any failures, then click Close.
4. Pre Installation Configuration
4.1. Create folder structure
4.1.1.For the SQL install, you will need to create your appropriate directories for the database, database log, tempdb, tempdb log and backup directory. I setup the following:
4.1.1..1. User database Directory: D:\ mssql\data
4.1.1..2. User database log directory: F:\ mssql\logs
4.1.1..3. Temp DB directory: E:\ mssql\tempdb
4.1.1..4. Temp DB log directory: E:\ mssql\temdblogs
4.1.1..5. Backup directory: G:\ mssql\backup
4.1.2.Reboot the server.
5.1. Install Microsoft SQL 2008 R2
5.1.1.Launch the installer for MS SQL 2008 R2.
5.1.3.Click New installation or add features to an existing installation.
5.1.4.Click OK on the Setup Support Rules screen.
5.1.5.Click Next after selecting to install the Evaluation version or enter your product key.
<screen omitted for security reasons>
5.1.6. Click to accept the license terms and click Next.
5.1.7. Click Install to install the setup support rules.
5.1.8. Click Next.
5.1.9. Check SQL Server Feature Installation and click Next.
5.1.10. Leave the default directory set to C:\ (or change it to whatever you like) , then checkmark the following features below and click Next.
5.1.11. Click Next after the installation rules complete checking.
5.1.12. Leave the default instance if you want and click Next. You may change it to a Named Instance based on your desired (or required) SQL configuration.
5.1.13. Click Next on the disk space requirements check
5.1.14. Click Use the same account for all SQL Server services and provide the Application Identity, except the SQL Server Integrations Services 10.0, which should be set to NT AUTHORITY\NETWORK SERVICE. Also, set all the services Startup Type to Automatic except the SQL Full-text Filter Daemon Launcher, which should be set to Manual.
5.1.15· On the Account Provisioning tab, select Mixed Mode, enter the SA password. Then click Add Current User, and then add the AppID (don't forget that one), and your DBA's if you want to act as additional SQL Server administrators.
<screenshot omitted for security reasons>
5.1.16. On the Data Directories tab, change the locations of the directories that you created in the Pre Installation Configuration step above.
5.1.17. On the Account Provisioning tab of the Database Engine Configuration page, click Add Current User, and then add the AppID (don't forget that one), and your DBA's if you want to act as additional SQL Server administrators.
<screenshot omitted for security reasons>
5.1.18. On the Data Directories tab of the Analysis Services Configuration page, change the locations of the directories that you created in the Pre Installation Configuration step above.
5.1.19. Check to Install, but do not configure and click Next.
5.1.20. Click Next to skip sending Error reports to Microsoft.
5.1.21. Click Next to install the configuration rules.
5.1.22. Click Install.
5.1.23. Click Close highlighted in the screen below
6. Post Install Configuration
6.1. Enable Named Pipes
6.1.1. Click on Start |Microsoft SQL Server 2008 R2 |Configuration Tools |SQL Server Configuration Manager
61.2.Expand SQL Server Network Configuration and click on Protocols for MSSQLSERVER.
6.1.3.Right click on Named Pipes and change it to Enable.
6.1.4. A window will pop up stating that you will need to restart the services for the change to take effect. Choose to restart now or reboot later.
6.1.5. Close the SQL Server Configuration Manager.
6.2. Verify installation
6.2.1. Launch SQL Server Management Studio and login using Windows authentication of your own account.
6.2.2. Run this query against the Master database to verify a functional installation
6.2.3. Logout and re-launch SQL Server Management Studio and login using SQL Server authentication as the sa user.
6.2.4. Run this query against the Master database to verify a functional installation
6.2.5. Reboot the server.
NOTE: The NS application identity must have DBO perms in the db. By adding the AppID to the sa group in the steps above, you will be ok.
The suspenseful continuation of configuring your installation is continued in the article: https://www-secure.symantec.com/connect/articles/h...
Feel free to message me with any questions you have and I will do my best to answer them quickly.