Video Screencast Help
Symantec Secure Login will be live on Connect starting February 25. Get the details here.

SWS - Configuring SQL Server Using Windows authentication

Created: 04 Jun 2014 • Updated: 04 Jun 2014
Language Translations
Christyt's picture
+1 1 Vote
Login to vote

Steps to Configure SWS with SQL Server on Windows Authentication Mode.

On the SQL Database Server:

1. Configure a SQL 2008 R2 (or any other SWS supported SQL version) Server with Windows authentication alone (Default SA account will be disabled).

2. Identify one domain user and add it as sysadmin in the SQL 2008 Security Logins. This user will act as the super user who creates the DB schema and the administrator for appstream database.

Note: You can also have two separate users based on the business need. One user will be used as the super user to create the DB schema and the other one will be the DB owner.

On the SWS Server:

3. Install a SWS 7.5 Back End Server and opt to Skip the DB configuration during the console configuration and finish the configuration.


4. Edit the da.conf to include database host, port, connection.url and connection.user as appropriate.

Example: torque.database.appstream.adapter=mssql appstream.database.port=1433 torque.dsfactory.appstream.connection.driver=net.sourceforge.jtds.jdbc.Driver torque.dsfactory.appstream.connection.url=jdbc:jtds:sqlserver://${}:${appstream.database.port};DatabaseName=${};domain=NAM; useNTLMv2=true torque.dsfactory.appstream.connection.user=dbasuser torque.dsfactory.appstream.connection.password=Jr7i9Swna4bUJty9mKM1Qw==

  • Da.conf can be found under [InstallDir]\Workspace Streaming\Server\streamletEngine\da\conf
  • By default the da.conf has the SQL Server settings. The values above in bold needs to be changed matching your environment.
  • The should be given the SQL Server hostname
  • The appstream.database.port should be given the SQL Server port (Default 1433)
  • The connection.url should be appended with the DOMAIN Name of the Server (Both SQL and the SWS BE should belong to the same Domain). Format is domain=’Domain Name’
  • Note: ‘ useNTLMv2=true’ is an optional parameter. In some customer environments it is seen that Domain=’Domain Name’ alone won’t be sufficient. Without the NTLM parameter, it would error out and state that the login is not from a trusted domain. In those cases, this parameter can be added so that it points out the NTLM version to the connection string and allows it to connect using NTLM.
  • The connection.user is the user (like asuser) which is used to do all the DB connections and transactions. This user should be a sysadmin.
  • The connection.password can be ignored as it will be populated and encrypted in the following steps during the execution of Create Schema command.

5. From Run>cmd, navigate to [INSTALLDIR]\streamletEngine\bin (C:\Symantec\Workspace Streaming\Server\streamletEngine\bin) folder and run CreateDatabaseSchema.cmd with following parameters:


CreateDatabaseSchema.cmd [admin user] [admin password] [default Db] [db option] [asuser password]

Note: [Default db] master - for mssql
     [Db option] mssql2005
     [asuser password] - A password for admin user for appstream database


CreateDatabaseSchema.cmd dbasuser Stream#123 master mssql2005 Stream#123

  • Here we are using the same user ‘dbasuser’ as the super user (sysadmin) who can create the table and as the admin user for appstream DB. ‘Stream#123’ is its password.( It is a domain user)
  • ‘master’ is the name of default DB
  • ‘mssql2005’ is the DB type (common)
  • ‘Stream#123’ is the password for the domain user ‘dbasuser’ which is mentioned in the da.config.


  • The above command will create the Appstream DB, schema and the tables.
  • If there are any errors while executing this script, the log can be located at
    [InstallDir]\Workspace Streaming\Server\Installation\Logs\CreateApstreamSchema

Note: If you want to use separate users as the Super User and the DB owner, then the command should be modified accordingly to include both the passwords.

6. After successfully executing the above command, start the Agent and the STE services from the Services console.

7. Now login to the console, Navigate to Manage>Components>Add> Provide the hostname of the Back End Server.

Note: It may error out while resolving the component name of the STE during ‘Get Name’, at that time you can manually provide ‘STE on SERVER’ corresponding to ‘Component Name’ and Click on ‘Save’

8. Refresh the Component status page to check the status. Now you can proceed to add Front End Servers, Data Access Servers and Upload Packages etc.

General Notes:

  1. While navigating to Manage>Components>Add, if the Back End Server component is already present, please remove it and follow the step: 7 to add it manually.
  2. By default, a user called ‘asuser’ will get created under the Security Logins on the SQL DB. This user can be either deleted or ignored.
  3. While executing the CreateDatabaseSchema.cmd, the command window will display “Updating da.conf with encrypted password given for ‘asuser’”, you can ignore this message.