Posted by: paralleldivergence | October 26, 2009

Want to run SRN Server from your Windows Server?

Many schools around the world have Windows Server 2000, 2003 or 2008 as their main file server. The great thing is, if you have a Campus-Wide licence of Student Response Network, it makes a lot of sense to run both the SRN Server module and the SRN Client from shares on that server, meaning no local installations are required at all! This article is aimed at school/campus Network Administrators, providing clear instructions on how to run SRN properly from shares on a Windows server.

Step 1: Locate your SRN Server folder on a share accessible to staff. It is not necessary for teachers or presenters that will use SRN Server to have write/modify access to the share, but it should be on a share that Students generally do not have access to. Usually a StaffShare of some kind will do.  The path can either be accessible via UNC Path or Mapped Drive Letter to run SRN Server. It’s recommended that you create a folder called StudentResponseNetwork in your share, then place the SRNServer folder inside that.

Step 2: Locate your SRN Client folder on a Read Only share, accessible by both students and staff – usually an Apps share of some kind. The path can either be accessible via UNC Path or Mapped Drive Letter to run SRN Server.

Step 3: Create shortcuts to SRNServer.exe for staff logons and to SRNclient.exe for student logons. However you deliver shortcuts to your users, use that method to deliver shortcuts to these applications as appropriate.

Step 4: Adjust Group Policy settings to define Windows Firewall exceptions to allow SRN Server to run on any computer on the school network. This step should only be run by the school’s server administrator!

(a) Run Group Policy Management Console
(b) Right-click on the domain or the appropriate user Organizational Unit and create a New Policy – name the policy “Client Firewall” or similar.
(c) Right-click on that new policy you created and choose Edit.
(d) Navigate to Computer Configuration…Administrative Templates…Network…Network Connections…Windows Firewall…Domain Profile.  The following screen will appear:

WinFirewalPolicy1_500

(e) Double-click “Windows Firewall: Define program exceptions
(f) Click Enabled at the top, then click Show, then click Add.
(g) In the box that appears, type in (or copy this line and paste it):

\\<sname>\<shname>\SRN\SRNserver\SRNserver.exe:*:enabled:SRN

Replace <sname> with your server’s name and <shname> with the share where you put SRN.

(h) Click OK twice to return to the screen shown above.
(i) Double-click “Windows Firewall: Define port exceptions
(j) Click Enabled at the top, then click Show, then click Add.
(k) In the box that appears, type in (or copy this line and paste it):

3128:TCP:xx.xx.xx.0/254:enabled:SRN

Replace xx.xx.xx with the first three octets of the server’s IP address.

(l) Click OK twice to return to the screen shown above.
(m) Click the X at the top right to close Group Policy Management Console

Finally, any workstation that is to run SRN Server must be rebooted once in order to receive the new Computer Client Firewall Policy.  From there, SRN Server should work fin from ANY PC logged onto the server as a staff member.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: