Cgriffen: /* Procedure */

2012-11-09T22:29:53Z

Procedure

← Older revision		Revision as of 22:29, 9 November 2012
Line 47:		Line 47:
	#** db_datawriter		#** db_datawriter
	#** db_ddladmin		#** db_ddladmin
		+	#** db_owner
	# Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Step 7\|Step 7]] for each additional MPWEB slave database.		# Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Step 7\|Step 7]] for each additional MPWEB slave database.
	#: The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.		#: The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.
-	# Click '''OK''' to complete the account configuration.	+	# Click '''OK''' to complete the account configuration.
-		+
-		+

	== Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility ==		== Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility ==

Docwikibot: Bot: Adding {{Template:Required Metadata}}

2009-12-18T00:06:48Z

Bot: Adding {{Template:Required Metadata}}

← Older revision		Revision as of 00:06, 18 December 2009
Line 1:		Line 1:
		+	{{Template:Required Metadata}}
	'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]		'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

Jmcmulle: added this note: '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

2009-04-17T21:35:28Z

added this note: '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

← Older revision		Revision as of 21:35, 17 April 2009
Line 72:		Line 72:
	# Click '''OK'''.		# Click '''OK'''.
	# Restart the Cisco Unified MeetingPlace Web Conferencing Service.		# Restart the Cisco Unified MeetingPlace Web Conferencing Service.
		+
		+	'''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

MeetingPlace Express Moderator: 1 revision

2009-03-20T23:41:47Z

1 revision

← Older revision

Revision as of 23:41, 20 March 2009

MeetingPlace Express Moderator at 18:29, 10 March 2009

2009-03-10T18:29:12Z

New page

'''Main page:''' [[Cisco Unified MeetingPlace, Release 7.0]]

'''Up one level:''' [[Cisco Unified MeetingPlace, Release 7.0 -- Configuration|Configuration]]

By default, the Cisco Unified MeetingPlace Web Conferencing installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, and configure the Web Server to use this account.

Complete the following procedures in the order shown to create and use a least-privileged SQL account:

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Creating a Least-Privileged SQL Account for Web Conferencing|Creating a Least-Privileged SQL Account for Web Conferencing]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility|Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility]]

== Creating a Least-Privileged SQL Account for Web Conferencing ==

'''Caution! ''' If you choose to create a SQL account that is dedicated for use with Cisco Unified MeetingPlace Web Conferencing, ensure that it meets all the specified database role requirements in this procedure. Failure to do so can cause a database connection failure between the web conferencing application and the SQL Server and result in a total outage or broken features.

'''Note: ''' If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.

===== Procedure =====

# Open the SQL Server Enterprise Manager and create a new login:
## On the Start menu, click '''Programs > SQL Server 2000 > Enterprise Manager'''.
## Click a server group to expand it, then click the name of a server.
## Click '''Security > New Login'''.
#: The SQL Server Login Properties window displays.
# Enter a name for the login on the General tab.
# Click '''SQL Server Authentication'''.
# Enter a password for the account.
# Click '''MPWEB''' from the Database drop-down menu to set the MPWEB database as the default database.
# Click the '''Database Access''' tab.
# Specify the database roles for the MPWEB database:
## Check the '''MPWEB''' database in the Databases table.
## Check the boxes for the following roles in the Database Roles table:
#** db_datareader
#** db_datawriter
#** db_ddladmin
# Repeat [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Step 7|Step 7]] for each additional MPWEB slave database.
#: The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.
# Click '''OK''' to complete the account configuration.

== Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility ==

The MeetingPlace Gateway Configurations utility allows you to update the Web Server with the least-privileged SQL login account that you have already created. It does not create a SQL Server login or update the SQL Server for you.

===== Before You Begin =====

Change the username and password on SQL Server. See [[Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing#Creating a Least-Privileged SQL Account for Web Conferencing|Creating a Least-Privileged SQL Account for Web Conferencing]] for instructions.

===== Procedure =====

# Stop the Cisco Unified MeetingPlace Web Conferencing Service.
# Open the MeetingPlace Gateway Configurations utility.
# Click the '''Web Conferencing''' tab.
# Enter the hostname or IP address of the SQL Server that you want to update in the Server field.
#* Enter '''local''' for a local server.
# Enter the username and password that you applied to the SQL Server.
# Click '''OK'''.
# Restart the Cisco Unified MeetingPlace Web Conferencing Service.

===== Related Topics =====
* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Use the Cisco Unified MeetingPlace Web Conferencing Service#Stopping All Web Conferencing Services|Stopping All Web Conferencing Services]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- How to Use the Cisco Unified MeetingPlace Web Conferencing Service#Restarting All Web Conferencing Services|Restarting All Web Conferencing Services]]

* [[Cisco Unified MeetingPlace, Release 7.0 -- Opening the MeetingPlace Gateways Configuration Utility|Opening the MeetingPlace Gateways Configuration Utility]]

[[Category: Configuring Web Conferencing for Cisco Unified MeetingPlace, Release 7.0]]

Cisco Unified MeetingPlace, Release 7.0 -- How to Create and Use a Least-Privileged SQL Account for Web Conferencing - Revision history

Cgriffen: /* Procedure */

Docwikibot: Bot: Adding {{Template:Required Metadata}}

Jmcmulle: added this note: '''NOTE:''' When you restart the Web Server, all manual changes made to the registry are lost.

MeetingPlace Express Moderator: 1 revision

MeetingPlace Express Moderator at 18:29, 10 March 2009