NETAPP INTERNAL DOCUMENT WFA Installation and setup procedure Yaron Haimsohn, NetApp October 2011 | DRAFT v 1.4
NETAPP INTERNAL DOCUMENT
WFA Installation and setup procedure
Yaron Haimsohn, NetApp
October 2011 | DRAFT v 1.4
TABLE OF CONTENTS
1 PURPOSE ................................................................................................................................... 4
2 GENERAL ................................................................................................................................... 4
• Pre-Requisites ...................................................................................................................... 4
• Revisions .............................................................................................................................. 4
3 WFA PRE-INSTALLATION STEPS ........................................................................................... 5
• Delivery of installation kit to designated machine .............................................................. 5
• Setup data verification ........................................................................................................ 5
4 WFA INSTALLATION ................................................................................................................. 6
• Verify VM pre-requisites ..................................................................................................... 6
• Install WFA ........................................................................................................................... 6
• Install 3rd party SW as applicable ....................................................................................... 7
5 WFA SETUP ............................................................................................................................... 8
• Working with WFA............................................................................................................... 8
• Import DB backup (in case of upgrading an older installation) ........................................... 8
• Data acquisition ................................................................................................................... 8
• Credentials setup ................................................................................................................. 9
• Mail setup .......................................................................................................................... 11
• Auto SUPPORT (ASUP) setup ............................................................................................. 11
• LDAP setup ........................................................................................................................ 12
• SNMP setup ....................................................................................................................... 13
APPENDIX A – INSTALLATION KIT CHECKLIST ........................................................................ 14
APPENDIX B – UPGRADE PROCEDURE .................................................................................... 15
• backup current configuration ............................................................................................ 15
• Uninstall WFA and Install updated version ....................................................................... 16
• Restore backup .................................................................................................................. 16
APPENDIX C – WFA POC REQUIREMENTS ............................................................................... 17
• WFA Platform – VM Pre-requisites ................................................................................... 17
• Storage lab environmental requirements ......................................................................... 18
• Information requirements for WFA setup ......................................................................... 18
APPENDIX D – AUTOMATED ONCOMMAND 5 (DFM 4.1) SETUP FOR WFA .......................... 19
• Installing on Linux .............................................................................................................. 19
• Installing on Windows ....................................................................................................... 19
• Validation........................................................................................................................... 20
APPENDIX E – CONFIGURATION INSTRUCTIONS FOR CONNECTING WFA TO VCENTER 21
• Create read-only user, which will be used by WFA to access the data. ............................ 21
Option1: Create user using SQLCMD CLI ................................................................................... 21
Option 2: Create user using Microsoft SQL Server Management Studio .................................. 22
• Setting the data-source in WFA ......................................................................................... 25
• Troubleshooting – Enable remote access to the VC’s SQL server ..................................... 26
• Set Authentication Mode of the SQL server to ‘Mixed’ .................................................... 29
Option 1: Set Authentication Mode using Registry ................................................................... 29
Option 2: Set Authentication Mode using Microsoft SQL Server Management Studio ............ 29
1 PURPOSE
The purpose of this document is to describe the installation and setup of WFA. It will encompass
the various parts of the installation package, the installation procedure and the following setup
phase (Up to and including some basic sanity testing).
2 GENERAL
A successful installation of WFA is based on several steps. Some are pre-requisites and provide
as gating to the process but each must be followed through and/or verified in order for the
installation to complete successfully.
The steps involved in the installation and setup process are:
• Creation of an installation kit
• Kit delivery to the designated installation target
• Setup data verification
• Installation of WFA and related SW
• Setup of WFA
• Sanity testing
• PRE-REQUISITES
The detailed requirements from a VM for WFA installation are outlined in Appendix C
• REVISIONS
• 1.3
o Added Upgrade procedure – Appendix B
• 1.4
o Updated document for 1.0.1 release
� Included VM requirements document – Appendix C
� Included Vcenter connectivity instructions – Appendix E
o Added setup instructions for working with OnCommand 5.0
o Added setup instructions for ASUP, LDAP and Mail server
3 WFA PRE-INSTALLATION STEPS
• DELIVERY OF INSTALLATION KIT TO DESIGNATED MACHINE
In order to install WFA you will need to obtain an installation kit, a DB backup and a license.
• SETUP DATA VERIFICATION
When setting up WFA in an environment require the following information:
Unit/System Details purpose
DFM IP,
Username, Password
*Data acquisition
*Operations via ProvMgr, ProtMgr and Service
catalog
Array(s) IP, Username, Password Credentials for performing operations on arrays
Vsphere IP,
*VC-Login: User/Pass
*VC_DB-Login:User/Pass
*Credentials for operations via VMware APIs
*Data acquisition (for more details see Appendix E)
External
repositories
IP, Username, Password Data acquisition
Mail server IP, Username, Password Receiving WFA notifications via email
LDAP server IP, Username, Password,
Group Name
Authentication and Authorization via LDAP server
SNMP
Managment
Application
IP, Port Receiving WFA SNMP traps
It is advised to pass the required information in advance and verify its existence prior to the
installation session.
4 WFA INSTALLATION
• VERIFY VM PRE-REQUISITES
Prior to any POC, the customer is given the VM requirements document. It is advised to try and
verify prior to the scheduled installation that the VM is indeed ready for installation. The main
points to verify are:
1) Microsoft Powershell version installed – The Powershell version installed on the VM must be
2.0. It can be verified by checking http://www.asoft.be/prod_netver.html (it also provides links for
downloading the right version) or opening Powershell (Type “Powershell” at Start->Run) and
typing the command “$host.version” at the prompt. The major version should be 2 as seen
below:
2) Verify access to the filers and DFM – Pinging the applicable DFM machine and filer can cover
that requirement. It is imperative to verify that we can access the filers directly and give SSH
commands to the filers. SSH can be verified and/or enabled via FilerView under “Secure admin”.
• INSTALL WFA
The WFA installation is simple and straight forward. For complete reference of all the files in the
installation kit refer to Appendix A.
1) Assure no previous installation of WFA exists.
2) Make sure that all the files from the installation kit are available on the VM.
3) Create a “WFA” folder on the desktop and open the kit compressed archive to there.
4) Make sure that the customer put the DB backup file on the VM – Place it at the “WFA”
folder on the desktop.
5) Run the WFA installer exe file and complete the installation by pressing the “next”
buttons.
Note: In WinServer 2K3/2k8 please run the Exe as Administrator (via right-click menu).
6) Wait 2 minutes for the WFA application server to initialize.
7) Direct the VM browser to http://localhost/wfa and verify that WFA is indeed working.
Note: You may have to install Flash player either for IE or Firefox.
8) WFA starts without license – Insert the license as per the instructions in Appendix A.
9) Refresh the client – You are ready to continue.
10) Create links in the Links/Favorite bar for WFA and the Backup/Restore.
• INSTALL 3RD PARTY SW AS APPLICABLE
Some 3rd party SW installers are included in the WFA installation kit. Install them as required and
per the instructions below:
1) VMware Power CLI – A PowerShell extension for VMware APIs. Install if the POC
includes integration with a VMware vSphere.
Link for downloading:
http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/p
owercli?view=overview
Note: In WinServer 2K3/2k8 please run the Exe as Administrator (via right-click menu).
2) Firefox – Web browser. Install per need or in WinXP VMs.
3) Flash player – Required for WFA. Install either Firefox/Chrome version or IE as needed.
5 WFA SETUP
• WORKING WITH WFA
The VM on which the WFA is installed can be anywhere within the customer network providing.
It will have access to the filers and the DFM. WFA can be used by any browser from anywhere,
as long as the VM on which the WFA is installed is accessible via HTTP.
To run WFA direct your browser to the following address: http://<WFA server VM IP>/WFA.
The default credentials are admin/admin. It’s recommended to change the password of the user
after first login.
Note: The latest version of Flash player is required to be installed in your web browser. Pop up
blocker may be needed to be turned off for WFA to work correctly.
• IMPORT DB BACKUP (IN CASE OF UPGRADING AN OLDER INSTALLATION)
The first thing to do after an installation is to restore the DB backup applicable for the current
installation. That can be done by clicking on “Backup & Restore” link in “Tools” menu.
Choose the applicable DB backup file, and press “Restore”.
• DATA ACQUISITION
The first step in going towards data acquisition is to setup WFA data sources.
For now WFA supports following data source types:
- DFM 3.7.1
- DFM 4.0/DFM 4.1 (The latter using OnCommand 5)
- VMware Vcenter 4
Perform the below steps in order to set data source:
1) Go to “Data sources” via the left pane menu under “Execution”.
2) Create (Or substitute, as required) a new data source:
a. Press ”New” and name the source as you wish
b. Select relevant data source type and see most of the fields fill automatically
c. Insert the Host Name or IP
d. Select the update interval as 5 minutes (5 minutes is a recommended value, 0
means that no auto-updated will be performed)
e. Save settings
3) Press “Acquire now” and follow the status updates on acquiring data.
Note: If you are using DFM 4.1 and above (Part of OnCommand 5.0), you will be required to
complete OC5 setup to work with WFA. Kindly refer to Appendix D for additional details.
Note: During the initial acquisition, some warnings may occur – Please review them
carefully.
Note: For VMware vCenter 4 issues – Please refer to setup instructions at Appendix E
• CREDENTIALS SETUP
After initial data acquisition, we need to set the credentials for the arrays we will perform
commands on:
There are 3 ways to define credentials:
• Exact match – user can define single credentials for a specific IP or Host Name
• Default credentials – user can define single credentials for entire subnet or IP range.
The definition is done by using regular expression syntax with type “Pattern”.
• LDAP authentication – user can connect to array without defining credentials in WFA,
but using domain credentials (in this case array should be configured to perform
authentication with same LDAP)
Perform the below steps in order to set Exact match/ Default credentials:
1) Go to “Credentials” via the left pane menu under “Execution”
2) Create (Or substitute, as required) credentials for the applicable arrays:
a. Press ”New”
b. Select type of matching:
‘Exact’ for Regular credentials
‘Pattern’ for Default credentials
c. Select relevant type
d. Insert the Host Name or IP, relevant User Name and Password
e. Save
3) Repeat the process for all the relevant arrays and other types
4) If the workflows will include VMware vSphere operation – Create applicable credentials
for “VMware vCenter” type
5) If the workflows include ProtMgr/ProvMgr/Service Catalog operation – Create the
credentials for “DFM” type.
6) In order to test the credentials, use “Test” button in case of exact match credentials or
“Test Connectivity” button for all cases.
Should LDAP connectivity to the array be required - Perform the below steps in order to setup
LDAP authentication
• Array should be configured to perform LDAP authentication
• WFA service should be configured to run with domain user
• MAIL SETUP
In order to configure email notifications regarding workflow operations the Mail server
configuration needs to be set.
That can be done by selecting “Mail” tab in “Tools”-> “WFA Configuration” dialog.
Mandatory fields: ‘Mail Host’ and ‘Sender’.
• AUTO SUPPORT (ASUP) SETUP
In order to configure ASUP scheduling and content of ASUP messages the ASUP server
configuration needs to be set.
That can be done by selecting “ASUP” tab in “Tools”-> “WFA Configuration” dialog.
Mandatory fields: ‘Mail Host’, ‘Sender’ and ‘Destination’.
• LDAP SETUP
In order to configure WFA’s authentication and authorization to use an external LDAP server the
LDAP configuration needs to be set.
That can be accomplished by selecting “LDAP” tab in “Tools”-> “WFA Configuration” dialog.
The fields in this form are:
Field Description
User Principal Name Attribute Attribute that identifies each user in the LDAP server.
Group Membership Attribute LDAP attribute containing the groups in which a user is a
member.
Mail Attribute LDAP attribute that identifies the user’s e-mail address.
Distinguished Name Attribute LDAP attribute that identifies the user distinguished name.
Timeout Length of time to wait for a response from the LDAP server
before timing out, in seconds (ignore the ms in the screenshot).
LDAP Servers Comma separated list of LDAP server URIs.
LDAP server URI formatted as: ldap:///<ldap-server-address>[:port]
For the Active Directory used by the WFA server, leave this field
blank: ldap:///
WFA administrators group Name of the LDAP group that identifies the user as having
"Admin" role.
WFA architects group Name of the LDAP group that identifies the user as having
"Architect" role.
WFA operators group Name of the LDAP group that identifies the user as having
"Operator" role.
• SNMP SETUP
In order to configure SNMP notifications regarding workflow operations the management
application server configuration needs to be set.
That can be accomplished by selecting “SNMP” tab in “Tools”-> “WFA Configuration” dialog.
APPENDIX A – INSTALLATION KIT CHECKLIST
The following section details the products currently included in WFA installation kit. The kit is
comprised of 3 distinct parts:
WFA installation kit essentials:
File Filename (or example) Note
WFA installer exe WFA-x86-V1.0.1.3.18-B4853.exe
WFA DB backup Gzip file with DB backup relevant to the
installation
Optional - To be sent
over email
Dar definitions file .dar file containing certified and
customer specific content definition
Optional - To be sent
over email
VMware PowerCLI VMware-PowerCLI-4.1.0-264274.exe 3rd party API
Adobe flash player install_flash_player_10.exe – Firefox
install_flash_player_10_active_x.exe - IE
3rd party freeware
WFA license:
License string is to be created and be ready at hand for time of installation. There is no need to
send it over to the customer prior to installation (if installed via Webex).
Kindly contact the WFA team in order to obtain an appropriate license.
WFA installation kit supplemental tools:
While setting up WFA and testing the various scenarios, you may need to use some additional
tools to help with verification of the different functionality. Software like better editors (Such as
the Notepad++), DB viewers(Such as SQLYog or Navicat), and Baretail are obviously very helpful.
Unfortunately, they are currently not allowed for use, with the exception of Baretail.
APPENDIX B – UPGRADE PROCEDURE
The following section details WFA upgrade procedure.
The upgrade process is a fairly simple one, as (almost) in-place upgrade. The process is as
follows:
• BACKUP CURRENT CONFIGURATION
The first thing to do prior to upgrading WFA is to backup the current database, which contains
both configuration and cache information.
That can be accomplished by clicking “Backup & Restore” link from the left pane under “Setup”.
When in the “Backup & Restore” screen just press “Backup” and save the file on the desktop.
If the backup is taken for deployment on another machine, it may be useful to check the
“configuration only” checkbox.
• UNINSTALL WFA AND INSTALL UPDATED VERSION
Go to the Windows Control Panel (Start ->Settings->Control Panel-> Add/Remove programs) and
uninstall WFA.
Install the updated version as per the instructions in section 4 of this document, but don’t
continue to the setup phase.
Note: On rare occasion the uninstall process seems to get stuck before ending: If that happens,
open the Services console (By running “services.msc” from the Start->Run dialog) and stop the
“NetApp WFA Database”.
• RESTORE BACKUP
After the installation is complete and WFA started, go back to the “Backup & Restore” screen by
clicking on it from the left pane under “Setup”.
Choose the backup file you created prior to the uninstall process. If any changes were made in
the previous installation to any of the pre-canned definitions (Dictionary, commands, finders,
filters etc.) uncheck the “Upgrade pre-canned definitions” checkbox, or otherwise these will be
overwritten.
Regardless, the restoration process will migrate the backed up database to fit the currently
installed (updated) version and will update it as needed. When the process completes
successfully, press the link at the top right to “Return to WFA”.
Note: Electing not to upgrade the pre-canned definitions may prevent you from getting
important updates and fixes. Unless major changes were made to the pre-canned definitions it
is advised to update and upgrade those definitions.
APPENDIX C – WFA POC REQUIREMENTS
The purpose of this section is to define the pre-requisites and requirements from the customer
side towards the Workflow Automation (WFA) POC. The section will detail the requirements
from the VM on which the WFA server would be installed and the pre-requisites from the
storage lab.
• WFA PLATFORM – VM PRE-REQUISITES
The WFA platform should be installed on a dedicated VM for the purpose of the POC.
The recommended settings for the VM are:
• VM OS : Windows Server 2k8 R2 /
Windows Server 2K8 SP2 /
Windows XP 32Bit SP3
• RAM : 3072MB
• Disk Space : 20GB
• VM Name : Must not include “_” (Underscore)
During the installation, several applications will be deployed as part of WFA installation:
• JBoss application server
• MySQL
• PowerShell 2.0
• Adobe Flash player
The following ports are to be open in the firewall to allow these applications to work properly:
• MySQL – 3306
• JBoss – 1098, 1099, 80, 443
In order to install PowerShell 2.0, .Net 2.0 framework run-time patches should be fully updated
on the VM.
• STORAGE LAB ENVIRONMENTAL REQUIREMENTS
The WFA Server POC will utilize the customer’s storage lab.
For the purpose of the POC the following will be required:
• IP access from the WFA server to the lab DFM server (in which the lab storage arrays are
registered)
o DFM installed with Protection Manager (Optional)
o DFM installed with Provisioning Manager (Optional)
• At least 2 storage arrays (Filers), which:
o Are registered in the lab DFM
o Can be directly accessed from VM WFA will be installed on
o Are available for creating data protection connections
o Contain usable primary and secondary aggregates, as per the naming
conventions previously supplied
o Have SSH enabled
• Optional - A desktop/server with appropriate FC HBA adapter that can mount the
created data-stores and verify their operability.
• INFORMATION REQUIREMENTS FOR WFA SETUP
After installation WFA will be configured to work and utilize the customer’s storage lab.
In order to do that the following information is needed:
• IP of the DFM that is governing the arrays in the storage lab
• IP, username and password of the arrays we will use (Only the arrays we may create or
manipulate storage on)
• Optional - Prefix/ID/naming convention of the aggregates we will use from the arrays
mentioned above
• Optional – Mail server configuration details (Hostname, IP, port, username and
password) for delivering workflow execution notifications
• Optional – DFM connection details (Username and password) when using NetApp
management suite (Protection Mgr, Provisioning Mgr, Storage services)
APPENDIX D – AUTOMATED ONCOMMAND 5 (DFM 4.1) SETUP FOR WFA
Starting with OnCommand 5 (DFM 4.1), remote access to DFM's Sybase database was blocked
except for the built-in views. However, WFA cannot currently use these view and instead
requires direct read-only access to the DFM schema. This page describes how to use the
oc5setup tool to grant such remote read-only access to WFA.
• INSTALLING ON LINUX
1. Download the wfa_oc5setup.sh file to your home directory on the DFM server.
wfa_oc5setup.sh
2. Change wfa_oc5setup.sh to be executable: chmod +x wfa_oc5setup.sh>
3. Invoke the script providing it with DFM's home directory: ./wfa_oc5setup.sh <dfm-
home>
# chmod +x wfa_oc5setup.sh
# ./wfa_oc5setup.sh /mnt/lun_nb_iscsi_prod_1_filerip_21/
Verifying archive integrity... All good.
Uncompressing WFA OnCommand-5 Setup...
>>> Connecting to database
<<< Connected
*** Dropped existing 'wfa' user
=== Created user 'wfa'
>>> Granting access
<<< Granted access
#
• INSTALLING ON WINDOWS
1. Download the wfa_oc5setup.exe file to a folder in the DFM server.
wfa_oc5setup.zip
2. Start the wfa_oc5setup.exe and choose the DFM's home directory then click next:
3. Review the setup results:
4. Click "Next" and then "Finish" to complete the installation.
• VALIDATION
1. Both the wfa_oc5setup.sh and wfa_oc5setup.exe should emit the following if successful:
>>> Connecting to database
<<< Connected
*** Dropped existing 'wfa' user
=== Created user 'wfa'
>>> Granting access
<<< Granted access
2. Setup a data-source to the DFM server using wfa/Wfa123 and acquire.
Note that setup may fail if user 'wfa' is currently logged in to the database. In this case,
close Squirrel and stop any scheduled acquisitions before trying again.
APPENDIX E – CONFIGURATION INSTRUCTIONS FOR CONNECTING WFA TO VCENTER
From version 1.0.1 WFA has an ability to add vMware vCenter data to WFA Cache.
It’s done by acquiring data from VirtualCenter’s database using MSSQL JDBC driver.
WFA is connecting to VC SQL Server as read-only user and acquires relevant data.
This document provides instructions for creating "select/read only" user in VirtualCenter’s
database, setting the data-source in WFA and Troubleshooting guide for correct connectivity to
vMware vCenter.
• CREATE READ-ONLY USER, WHICH WILL BE USED BY WFA TO ACCESS THE DATA.
WFA is connecting to VC SQL Server as read-only user for acquisition
The user’s “User Mapping” should have “public” and “db_datareader” roles on the VIM_VCDB
database
There are two alternatives for the user creation.
One of the below sections (9.1.1 or 9.1.2) should be performed for this.
OPTION1: CREATE USER USING SQLCMD CLI
a) Open cmd session
• Start > Run > cmd
b) Connect to SQL Server, use below command:
• sqlcmd -S <HOME>\SQLEXP_VIM –E
Note: <HOME> is the server name and –E means that using windows authentication
c) Set VIM_VCDB as the current database
• USE VIM_VCDB
• GO
d) Create a new server login name: wfa and password ‘wfa’ as it defined by default in WFA
datasource type
• CREATE LOGIN wfa WITH PASSWORD = 'wfa', DEFAULT_DATABASE=[VIM_VCDB],
CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
• GO
e) Create a new database user linked to the login name
• CREATE USER wfa FOR LOGIN wfa
• GO
f) Grant database SELECT permission to the user
• GRANT Select To wfa
• GO
g) Set user role as 'db_datareader'
• EXEC sp_addrolemember 'db_datareader', wfa
• GO
h) Exit and close cmd session
OPTION 2: CREATE USER USING MICROSOFT SQL SERVER MANAGEMENT STUDIO
a) Open Microsoft SQL Server Management Studio and connect to the SQL Server
b) Right-click on SQL Server Instance->Security->Logins and select ‘New Login…’
c) On ‘Login-New’ tab, select General on the left window and update as below:
• Select SQL Server Authentication mode
i) Insert Login name:wfa and Password ‘wfa’ as it defined by default in WFA datasource
type
• Uncheck below checkboxes
o User must change password in next login
o Enforce password expiration
o Enforce password policy
• Set
� Default Database = VIM_VCDB
� Default Language=English
d) Select Server Roles and verify that ‘public’ role is selected
e) Select User Mapping and map ‘VIM_VCDB’ database to new user name and ‘dbo’
Schema
f) Select Status on the left window, and set
� Settings = ‘Grant’
� Login=’Enabled’
g) Click on ‘OK’ to save new user
h) Select SQL Server Instance->Databases-> VIM_VCDB->Security->Users and Double-click
on created user name.
In opened tab, select General on the left window, and set ‘db_datareader’ role
i) Click on ‘OK’ to save the changes
• SETTING THE DATA-SOURCE IN WFA
In order to set the data-source in WFA for acquiring data from VirtualCenter’s database need
perform the following steps:
a) Go to Execution->Data Sources form
b) Click on ‘New’ bottom to open ‘New Data Source’ editor
c) Set
� Name = <Name of new Data Source>
� Data Source Type = VMware vCenter- 4
� Host Name = IP/Host Name of the specific Virtual Center
� Port = <TCP Port that Virtual Center uses> (by default 1433)
� User Name/Password = <read-only user, which shall be used by WFA to access the
data>
(See section 2 above, by default its wfa/wfa)
d) Save the configuration
e) Select the created Data Source and Click on ‘Acquire Now’ for acquisition
f) When the acquisition will be completed the WFA Cache will contain information from
the specific VirtualCenter’s database
g) In case the acquisition will fail, follow instructions from section 4 ("Troubleshooting
guide")
• TROUBLESHOOTING – ENABLE REMOTE ACCESS TO THE VC’S SQL SERVER
In order to enable the remote access need to perform the following steps:
a. Open the Sql Server Configuration Manager (Start -> Programs -> Microsoft SQL Server
<VERSION> -> Configuration Tools)
b. Expand SQL Server Network Configuration -> [Your SQL Server Instance]
c. Double click TCP/IP
Under Protocol:
• Ensure Enabled is Yes
Under IP Addresses:
• Scroll to the bottom and set the TCP Port under IPAll
Note: Port 1433 is defined by default in WFA datasource type. In case the SQL
Server uses another port, the WFA datasource type should be updated accordingly.
d. If Firewall is enabled, you may need to create an exception on it for the SQL Server
instance and port you are using
• Start > Run > Firewall.cpl
• Click on exceptions tab
• Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL
Server\MSSQL.x\MSSQL\Binn), and port that SQL Server uses (see above section ‘c’)
e. If some changes were performed from steps c-d, need to restart SQL Server Service and
SQLBrowser processes
f. Finally, check that you have connectivity to the SQL Server. Note what you are using to
connect: machine name, domain name or IP address? Use this when checking
connectivity. For example if you are using <IP>
• Start > Run > cmd
• netstat -ano| findstr 1433
• telnet <IP> 1433
• ping -a <IP>
g. Check what ports are IP addresses are being returned.
Note: See http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-
2008-express/ for more information
• SET AUTHENTICATION MODE OF THE SQL SERVER TO ‘MIXED’
WFA uses SQL Server Authentication for connection to VC SQL Server.
In order to allow this kind of connection, Authentication Mode of the VC SQL server should be
set to “Mixed Mode” (Windows Authentication and SQL Server Authentication)
There are two alternatives for the setting of Authentication Mode
One of the below sections (9.3.2.1 or 9.3.2.2) should be performed for this
OPTION 1: SET AUTHENTICATION MODE USING REGISTRY
• Start > Run > Regedit
• The authentication mode is stored in the following registry location: \HKEY_LOCAL_MACHINE\SOFTWARE\...\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\
• The Key that needs changing is: LoginMode
• Set Value to 2
(Value of 1 is for Windows Authentication Mode and 2 is for Mixed Mode
Authentication)
• Restart the SQL Server Service
OPTION 2: SET AUTHENTICATION MODE USING MICROSOFT SQL SERVER MANAGEMENT
STUDIO
a) Open Microsoft SQL Server Management Studio and connect to the SQL Server
b) Right-click on the SQL Server Instance and select Properties.
c) On Server Properties, select Security on the left window. Then, select SQL Server and
Windows Authentication mode.
d) Click on ‘OK’ to save the changes - there is a pop-up shown up that you have to restart
the SQL Service to apply changes.
e) Right-click on the SQL Server Instance and select Restart