Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

My SMP 7.1 Beta Install - SQL

Created: 11 Feb 2011 • Updated: 11 Feb 2011
Language Translations
ziggy's picture
+2 2 Votes
Login to vote

1.       Overview

This document was written by me as a supplement to the Symantec provided instructions for the installation of the Symantec Management Platform (SMP) 7.1 beta.   This document will focus on the SQL database portion of the environment.  There is a separate document that addresses the NS configuration itself.

While every environment varies, I tried to ensure that the contents of this document are as universal as possible.  As such, they take into account the defaults set at installation time.  If you change settings, such as the default database name during your install, then you would need to ensure that you take that into account while reading through this document.

If you are like me, and a few of the others that I have seen in the forums, then this document, with a bit of luck, help you out by pointing out some specifics that I did not see documented elsewhere.  This document contains steps to be taken to ensure your environment is correctly configured assuming that you have already installed the OS, the software, and the database.

Since every Microsoft Windows imaged used and every SQL installation may be slightly different, some of the items here may not be applicable to you. I will not get into how an environment should be built, but focus on what the steps and pre-requisites I found I needed to get the SMP 7.1 beta installed.  With every environment being different, you may find that some, or even most of this document may not be applicable to you.  My hope is that this will help someone out there.

2.       Some, if not most, of these items could be done at installation time. I installed Microsoft SQL 2008 SP1

2.1.    Ensure you have mixed mode authentication enabled. You can ensure this by following these steps:

1.       Open the SQL Server Configuration Manager via Start > SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager

2.       Right-click on your database and select Properties.

3.       Select Security in the left pane

4.       Select SQL Server and Windows Authentication mode

5.       Click OK

6.       Restart the SQL Server Services

2.2.    Ensure Named Pipes are enabled.  You can ensure this by following these steps:

1.       Open the SQL Server Configuration Manager via Start > SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager

2.       Drill down the left pane to SQL Server Network Configuration > Protocols for MSSQLSERVER

3.       Double-click TCP/IP and Named Pipes and on the Protocol tab and change the dropdown to Yes.  Or, you could right-click on TCP/IP and select Enable.  (You will be warned that these changes will not apply until you the service is shut down.)

4.       Restart the SQL Server Services

2.3.    Ensure that the application identity of the SMP has DBO perms in the database.  You can ensure this by following these steps:

1.       Launch Microsoft SQL Server Management Studio and login to your instance

2.       Drill down to Security | Logins

3.       If the application identity of the SMP is not listed here then right click on the Logins folder and choose ‘New Login’.

4.       Enter the login name in the ‘domain\username’ format on the ‘General’ page

5.       Checkmark the dbcreator role on the ‘Server Roles page:

6.       Checkmark the Symantec_CMDB (or appropriate database if you changed the defaults at installation time):

7.       Click to ‘Grant’ permission to connect and ‘Enabled’ for login on the ‘Status’ page:

2.4.    Ensure IIS and .Net are installed.  Here is a screen shot of all the roles on my Win2k8 Database server listing those that are installed:

2.5.    I had to disable the Windows firewall.  I would not do this unless you have tried everything else and receive approval from your respective security department.  You can complete this yourself by following these steps:

1.       In Server Manager, click on Windows Firewall properties:

2.       Change the Firewall state to OFF on the Domain Profile Tab, then click Apply and OK.

3.       Change the Firewall state to OFF on the Private Profile Tab, then click Apply and OK.

4.       Change the Firewall state to OFF on the Public Profile Tab, then click Apply and OK.

2.6.    My SQL server was an off-box VM, and after the above steps were done, this is the configuration:

·              Microsoft Windows 2008 R2 Standard (64 bit) with 2 dual core processors and 8GB RAM

·              From within my SQL 2008 SP1 installation, I launched Microsoft SQL Server Management Studio and pulled this information from the Help | About menu:

o       Microsoft SQL Server Management Studio 10.0.2531.0

o       Microsoft Analysis Services Client Tools 10.0.1600.22

o       Microsoft Data Access Components (MDAC)                6.1.7600.16385

o       Microsoft MSXML 3.0 6.0

o       Microsoft Internet Explorer 8.0.7600.16385

o       Microsoft .NET Framework 2.0.50727.4952