Configuring SQL Server Permissions
Recast Management Server requires a SQL Server in 4.0. This can be the free SQL Server Express version, if desired. If SQL Server is installed on a remote device, the computer account of Recast Management Server will need permissions to create the database on the remote device. Alternatively, you can pre-create the RecastManagementServer database and give the computer account db_owner permissions. If the SQL Server is installed on the local device, the computer account of the Recast Management Server will need permissions to create the database on the local device. You can precreate the database and give the IIS AppPool\Recast Management Server account db_owner permissions to the database. This account will not exist until after the installation is finished, so the permissions will need to be given after installation. The Test SQL Connection button can verify connectivity to the SQL Server if the account running the installation has permissions to remotely connect.
Adding a Computer Account via SQL Server Management Studio (SSMS)
- If a computer account for the Recast Management Server doesn not exist in SQL, users will need to manually add on. The computer account will have the following name format: domain\computername$
- To create the account open SSMS > locate the RecastManagementServer > Security > Users > right click > add user > switch user type to windows user > domain\computername$
- Note: User Name and Login are the same
Assigning SQL db_owner Permissions
- After creating or locating the Recast Management Server computer account, users need to assign it db_owner permissions for the RecastManagementServer database.
- To do so, right click on the account > properties > membership tab > db_owner box:
Precreating the RecastManagementServer Database
- If DB Admins aren't able/willing to give SysAdmin rights to the user account running the installation, the DB Admin can manually create a database named RecastManagementServer
- Note: the IIS AppPool\Recast Management Server account will not exist until after the installation is finished, so db_owner permissions will need to be assigned after installation.