Lab Policies
Laboratory FAQ
Subversion
Backup
Getting Help With Computer Problems

Users of the Senior Design Center (SDC) Laboratory are expected to abide by the following policies. These policies are intended to preserve the integrity, utility, and flexibility of the equipment in the lab. They are also designed to protect the privacy of work done by students and faculty and to preserve our access to networks to which the lab is connected. You will also find useful and important information in the FAQs section.

Lab Policies

1. Students are expected to comply with the relevant policies of the Computer Science Department and with NCSU network and computing policies (http://www.ncsu.edu/it/rulesregs/).
2. All labs are secured-access facilities. People who need access are granted that access on an individual basis via key or fob. Under no circumstances should you allow anyone into the lab.
• It is your responsibility to update the Antivirus software on your machines. If the lab machines are not updated frequently they may be compromised. Set up an automatic update and an automatic system scan on a weekly basis.
• Automatic updates: File > Schedule Updates
• Automatic scans: View > Scheduled Scans
3. Any attempt to circumvent lab and system security, guess other passwords, or in any way gain unauthorized access to local facilities or network resources is forbidden.
4. Do not remove equipment from the lab without explicit permission from the course instructor.
5. You are expected to take proper care of the equipment in the lab. Report any malfunction via a Resource Request form immediately (see Getting Help With Computer Problems, below). Under no circumstances should you attempt to move, repair, reconfigure, modify, or attach any external devices to the lab equipment. Flash Drives are the only exception to this rule.
6. You are expected to take care of your lab space. Please keep your lab area neat and clean. Your lab space should be in the same condition at the end of the semester as you found it at the beginning of the semester.
7. Do not modify network connections or attempt to connect a personal machine to the local area network without prior approval.
8. Do not install or use file-sharing programs such as Kazaa, E-Mule, etc. on Senior Design Center lab machines, or personal machines on lab networks.
9. Student teams are responsible for backing up project related materials. See below for the backup procedure.
10. Please change the password for the ‘Team00’ Account to something unique for your team.
11. DO NOT CHANGE THE PASSWORD ASSOCIATED WITH THE 'ADMINISTRATOR' login. DO NOT RENAME OR DEACTIVATE THE 'ADMINISTRATOR' login.
12. If you change the password associated with the 'administrator' login, the system will be rebuilt, without notice, from a base image. No attempt will be made to recover project files and/or data.
13. If you install software or change any setting(s), and the computer subsequently becomes inoperative or unstable, no attempt will be made to recover. A “base system” image will be applied which will over-write the entire disk. You are responsible for recovering your work to date.
14. Do not change/add printer setups unless advised to do so by an IT staff member.

Laboratory FAQ

How do I log on to the computer in my workspace?

The computers that are in your workspace are not related to your unity accounts. An account for your team has been set up. The initial login/password for your team is “Team00/team00” (for Windows machines). Please change the password immediately.

Should I change the password(s) on my team’s SDL machine?

Please change the password associated with the team login to something more secure. Be sure to change the password to one that the team decides upon. All student team accounts have administrator privileges. Be advised, if you also create additional logins, the Sys Admin will not support any problems with these accounts. Please create passwords for any additional accounts as well.

DO NOT CHANGE THE PASSWORD ASSOCIATED WITH THE ‘administrator’ login.

What is installed on our lab machines?

The default operating system for the Senior Design Center is Windows XP Pro. Exceptions are only made when project sponsors require a different operating system for developmental purposes. The following software is installed in addition to Windows XP Pro

• Office 2007
• Visual Studio 2008
• Eclipse 3.2
• Tortoise SVN
• Visio 2003
• Firefox
• Thunderbird
• WinSCP

How can I get a specific application installed on our lab machines?

There are several applications that are freely available on the Internet and each team has administrator privileges on their machine. You are encouraged to install and configure these free applications in an effort to better understand the technology that you will be using to develop your project. If the application you need is not freely available for download on the Internet use the ‘Resource Request’ form provided on the Senior Design Center web site (http://www.csc2.ncsu.edu/sdc/students/forms/request.php). In your request be sure to specify your computer name(s) found on a sticker on the front of each computer and the software you need to be installed and any other helpful information.

Can we have administrator privileges on our computers?

Yes. All student accounts on Senior Design Center computers will belong to the ‘administrator’ group. With this comes the responsibility to ensure that your computer remains viable and stable.

Do I have access to my AFS space?

Yes, you may access your AFS space with your unity login through WinSCP. You may download and install the latest version of WinSCP at http://www.eos.ncsu.edu/remoteaccess/windows/ras-win-sftp.html.

Can I access lab machines remotely?

In an effort to increase security in our labs, machines will be made remotely accessible on a VERY limited basis. They will require that you access them from a FIXED IP address. No exceptions will be made to this rule. You must put in a resource request to be allowed remote access to your machines.

Can I connect a personal laptop or computer to the network?

Yes, but you must get permission before you can connect a new host to the local area network. If you would like to connect a personal machine to the LAN, use the ‘Resource Request’ form mentioned above. Wireless networks are available in several lab locations and you do not need permission to use the wireless system.

Virtual Machines

We will have virtual images available upon request. Virtual machines are good for running multiple machines without needing extra equipment filling up your cube. If you need and virtual machine running Windows 2003, XP, RHEL 4 or 5, please put in a resource request. You can download the VMWare player for free from here: http://www.vmware.com/products/player/

Subversion

A departmental Subversion Server (SVN) is available for version control of source code and other text-based documents. This helps to restore your work in case it gets corrupted, overwritten, or changed improperly. Use the “checkout” procedure described below to make changes.

How to Use the Subversion Server:

1. We will be using Tortoise SVN to connect to the Subversion server:
2. Create a new folder, or select a blank folder where you plan to keep your code.
3. Right-click on the folder, and select SVN checkout
4. For the URL use the following Address:
   https://svn.csc.ncsu.edu:8443/svn/csc-492-project1-teamX/
   (again, replace teamXX with your team number)
5. Click Ok
6. You will be prompted to accept the SSL Certificate.
7. You will then be prompted for your unity username and password.
8. You should see the folders added to your coding folder: Trunk, branch, and tags.
   These three folders are the standard for keeping track of your coding. Here is some documentation on how to use the different folders:
   http://dev.wp-plugins.org/wiki/RepositorySetup
9. Click Ok.
10. You are now connected to the Subversion server. You can right-click this folder at any time to checkout or update a piece of code. Spend some time getting familiar with this system. It will help you and your teammates from overwriting each other’s hard work.
11. The departmental SVN server is shared amongst multiple classes. Therefore, we have a size limit on files that can be committed. You should be submitting code to SVN anyways, not large binary files.

Backup

The departmental SVN runs on a RAID-5 system to provide high reliability, however, independent backups are also recommended. Each team should establish a backup philosophy for work products. System code and other executables installed on desktops allocated in each team space or installed on team members’ laptops should also be backed up. Consult IT support staff for assistance in establishing a system level backup plan.

Getting Help with Computer Problems

Please let us know immediately if you have any problems using the subversion server of if you have any other resource requests!!!

Go to http://www.csc2.ncsu.edu/sdc/

On the left, under forms is a link called “Resource Request”

Click the link, and you will be asked to login with your Unity name and password.

You should then fill out the form explaining your problems or requesting your needs. Make sure to include the Computer Name with your request (it is written on the front of the machine). Resource Requests should be completed by the Team Lead.

Resource Requests should be completed by the Team Lead.