Setting Up SME Client Users - Revision history

CraigL at 19:57, 9 November 2015

2015-11-09T19:57:48Z

Marks at 22:23, 22 December 2014

2014-12-22T22:23:32Z

Amy: Created page with "

Server-End:

Open SQL Management Studio, click "Connect" on the default connection.
Select the "Security" folder on the left-hand pane, and drop it down to show ..."

2013-11-29T18:48:28Z

Created page with "<h3>Server-End:</h3> <br>Open SQL Management Studio, click "Connect" on the default connection. <br>Select the "Security" folder on the left-hand pane, and drop it down to show ..."

New page

<h3>Server-End:</h3>

<br>Open SQL Management Studio, click "Connect" on the default connection.
<br>Select the "Security" folder on the left-hand pane, and drop it down to show "Logins"
<br>Right-click on "Logins", then "New Login".
<br>Click "Search" to pop up the Network user search tool - make sure to select your domain under the locations box.
<br>Locate the user to add, click OK until back to Login-New page.
<br>On the left-hand pane, go down to "Server Roles" - check as "sysadmin"
<br>On the left-hand pane, go down to "User Mapping" - check "NormentSecurity" in the top section, then check "db_owner" in the bottom section.
<br>Click ok - this user is now permitted to access SME over SQL authentication.

<h3>Client-End:</h3>

<br>For setting up a client machine to use SME over the network, these are the steps to follow:
<br>First, on the new client machine, navigate to the network path of the high5software folder (accessed via network IP address as opposed to computer network name)
<br>Open "ClientInstall", and install either the 32(x86) or 64 bit version of the sqlncli.msi file. You can click next through every screen without intervention throughout the install process.
<br>Next, make a shortcut to "sme5.exe" (in the High5Software root folder) on the client machine desktop.
<br>Go to the control panel/windows firewall. On the left-hand pane, click "Advanced Settings".
<br>- Highlight "Inbound Rules" on the left pane, then click "New Rule" on the right hand pane.
<br>Select "Port" from the first page
<br>Leave "TCP" checked, and fill in port number 1433, click next - Allow Connection - Next (domain/pub/work) -> then give it a name (I usually name it _SMETCP, so it's at the top of the list and easy to locate).
<br>Repeat these steps on another "New Rule", except select "UDP" on the second screen, and use port number 1439
<br>Allow/Check all and name _SMEUDP
<br>Click on the "Outbound Rules" tab
<br>Repeat steps to add TCP/UDP rule in outbound rules - note that allow connection won't be checked by default this time, so be sure to switch it on this screen.
<br>Launch shortcut from client machine, and SME should load.

← Older revision		Revision as of 19:57, 9 November 2015
Line 1:		Line 1:
−	~~<h3>Server-End:</h3>~~
−
−	~~<br>Open SQL Management Studio, click "Connect" on the default connection.~~
−	~~<br>Select the "Security" folder on the left-hand pane, and drop it down to show "Logins"~~
−	~~<br>Right-click on "Logins", then "New Login".~~
−	~~<br>Click "Search" to pop up the Network user search tool - make sure to select your domain under the locations box.~~
−	~~<br>Locate the user to add, click OK until back to Login-New page.~~
−	~~<br>On the left-hand pane, go down to "Server Roles" - check as "sysadmin"~~
−	~~<br>On the left-hand pane, go down to "User Mapping" - check "<your company>" in the top section, then check "db_owner" in the bottom section.~~
−	~~<br>Click ok - this user is now permitted to access SME over SQL authentication.~~
−
	<h3>Client-End:</h3>		<h3>Client-End:</h3>

@@ Line 7: / Line 7: @@
 <br>Locate the user to add, click OK until back to Login-New page.
 <br>On the left-hand pane, go down to "Server Roles" - check as "sysadmin"
-<br>On the left-hand pane, go down to "User Mapping" - check "NormentSecurity" in the top section, then check "db_owner" in the bottom section.
+<br>On the left-hand pane, go down to "User Mapping" - check "<your company>" in the top section, then check "db_owner" in the bottom section.
 <br>Click ok - this user is now permitted to access SME over SQL authentication.