GENERAL RESPONSIBILITIES:

Under the direction of the I.T. Center Head, perform a variety of professional duties that include providing desktop computer and enterprise system support; troubleshoot computer system hardware and software problems; perform minor microcomputer repair; assist computer users in setting up new applications, installations and configuration; and supervise computer technicians.

SPECIFIC RESPONSIBILITIES:

1. Identify, analyze and resolve computer system and software malfunctions and procedural problems.
2. Install microcomputers and related peripheral equipment including printers, scanners, plotters, disk drives, memory sticks, network interface cards, and related items.
3. Troubleshoot hardware and software applications.
4. Operate a variety of highly technical network and computer equipment and related peripheral equipment.
5. Set up multimedia equipment in conference rooms including computers, LCD projectors, and other equipments as required.
6. Assist new users in setting up new applications, installations, problem solving and in performing minor microcomputer repair.
7. Perform a variety of professional duties involved in developing and implementing training programs for computer users.
8. Learn new software and hardware products with and without formal training.
9. Read, interpret and apply concepts in complex technical publications, manuals and other documents.
10. Maintains inventory of all computer hardware and peripherals, computer software, and office equipment in area of responsibility.
11. Provide assistance to Superior; prepare administrative reports related to training and support activities; assist in design and development of computer laboratory facilities.
12. Learn the functions and limitations of assigned duties.
13. Assist other I.T. Center Personnel in their computer hardware problems
14. Understand the organization and operation of the assigned office and the Information Technology Center in order to assume assigned responsibilities.
15. Communicate effectively both orally and in writing.
16. Establish and maintain cooperative and effective working relationships with others.
17. Mentor, supervise and evaluate computer technicians to make sure they perform to the standards defined by the office and the institution.
18. Perform duties delegated by superior for the benefit of the I.T. Center and the school in general.

OTHER DUTIES:

Attend and participate in staff meetings and in-services activities; attend specialized training classes, attend workshops and conferences to increase professional knowledge of technologies and software.

• Desktop Computers
• Server Computers
• Laptops
• LCD Projectors
• Printers
• Digital Cameras
• Video Cameras
• Speakers
• Networking Equipment like Hubs, Switches, Wired or Wireless Routers

• College Computer Laboratories
• High School Computer Laboratory
• Internet Laboratory
• Network Operations Center
• Multimedia Section

Technical Support

Computer Repair and Maintenance

• Hardware
• Software
• Equipment

Software Development

• Business Applications
• Web Development

Network Management

• Setup and Maintenance
• Internet Connection

Multimedia Production

• Photo Services
• Audio and Video Production
• Events Coverage and Promotion
• Advertisements
• ID Cards
• Layout
• Printing
• CD/DVD Burning

Training

• Technical Trainings
• End-User Trainings

Community Services

• Technical Support
• Computer Repair and Maintenance
• Software Development
• Network Management
• Multimedia Production
• Training
• Rental of Facilities and Equipment
• IT Consultancy

The office evaluates requests of the administrative offices and other units regarding computer hardware and software requirements and recommends the appropriate computer system. The office is tasked to acquire and upgrade the hardware and software to support the Center’s services to the School and to maintain the inventory of computer supplies and related software manuals.

Note: For computer laboratories of the ETD, High School, and DMSST units: An ITC Staff will be assigned to ensure the performance of the computers and network in the area. The staff will still report to the ITC Head. He will also handle the acquisition and inventory of computer facilities and other related equipment of the unit.

Programming Section
The ITC-Programming Section (ITC-PS) designs, develops, implements, maintains, and evaluates computer-based information systems. These services come in the form of implemented computer-based information systems and enhanced manual-based systems as requested by the academic/administrative units to facilitate their operations. This section is also involved in helping the offices generate additional reports from their installed information systems. It covers the creation, implementation, modification and maintenance of the school web site.

Multimedia Section
The ITC-Multimedia Section (ITC-MS) is in-charge of photography, audio, and video editing. This involves coverage of various institutional events and advertisements which may include layout of documents, banners, tarpaulins and other media. The section also does printing, CD or DVD burning, and ID card-making.

Network Administration Section
The ITC-Network Administration Section (ITC-NAS) takes charge of connecting the computers in the institution, creates the users and groups, and assigns access rights. The section also maintains the servers and the Internet connection. The section is responsible for the setup, security, administration, and maintenance both for the wired and wireless networks.

President
|___Vice President for Academic Affairs
    |___ITC Head
        |___Technicians Section
            |___Computer Technician Supervisor
                |___Computer Technicians
        |___Programming Section
            |___Computer Programmer
                |___Junior Computer Programmer
        |___Multimedia Section
            |___Multimedia Supervisor
                |___Multimedia Staff
        |___Network Administration Section
            |___Network Administrators
                |___Assistant Network Administrator

These are the persons holding the respective positions in the ITC Organizational Chart:

Fr. Romeo S. Saniel, OMI (President)
|___Westre P. Santos (Vice President for Academic Affairs)
    |___Cyril Pauya (ITC Head)
        |___Technicians Section
            |___Edwin Resmenia (Computer Technician Supervisor)
                |___Lito Debabao (Computer Technician)
                |___Nathaniel Varona (Computer Technician)
                |___Peter Bragais (Computer Technician)
                |___Ritche Corpuz (Computer Technician)
        |___Programming Section
            |___Cyril Pauya (Computer Programmer)
                |___Julius Ryan Bulahan (Junior Computer Programmer)
        |___Multimedia Section
            |___Julius Ryan Bulahan (Multimedia Supervisor)
                |___Gary Abayata (Multimedia Staff)
                |___Lito Debabao (Multimedia Staff)
                |___Peter Bragais (Multimedia Staff)
        |___Network Administration Section
            |___Cyril Pauya (Network Administrator)
            |___Nathaniel Varona (Network Administrator)
                |___Peter Bragais (Assistant Network Administrator)

• provide the highest quality service responsive to and meeting the information needs and computerization requirements of both the academic community and the various administrative units in the school
• intensify quality education to NDMC students through information technology facilities and equipment
• strengthen linkages between NDMC and the community through trainings and seminars in new technologies
• ensure the functionality of all computers and related equipment of the school
• provide a fast accessible internet service to students, faculty, administrators, and selected offices
• provide community services related to Information Technology like:
  • computer and network installation and repair
  • custom software development
  • multimedia, audio, and video production
  • training services
  • rental of facilities and equipment
  • other I.T. services

The Information Technology Center supervises, coordinates and controls the I.T. environment for administrative applicability in the school, the development and provision of the school data resource (computerized and non-computerized), computer and network facilities, information systems and services, and the design and/or improvement of school processes with the end-view that such services effectively respond to the requirements of the institution.

Table of Contents

• ITC Objectives
• ITC Organizational Chart
• ITC Sections
• ITC Personnel
• ITC Services
• ITC Facilities
• ITC Equipment
• ITC Standard Operating Procedures
• ITC Documentation

GENERAL RESPONSIBILITIES:

Under the direction of an assigned supervisor, perform a variety of professional duties that include providing desktop computer and enterprise system support; troubleshoot computer system hardware and software problems; perform minor microcomputer repair; assist computer users in setting up new applications, installations and configuration.

SPECIFIC RESPONSIBILITIES:

1. Identify, analyze and resolve computer system and software malfunctions and procedural problems.
2. Install microcomputers and related peripheral equipment including printers, scanners, plotters, disk drives, memory sticks, network interface cards, and related items.
3. Troubleshoot hardware and software applications.
4. Operate a variety of highly technical network and computer equipment and related peripheral equipment.
5. Set up multimedia equipment in conference rooms including computers, LCD projectors, and other equipment as required.
6. Assist new users in setting up new applications, installations, problem solving and in performing minor microcomputer repair.
7. Perform a variety of professional duties involved in developing and implementing training programs for computer users.
8. Learn new software and hardware products with and without formal training.
9. Read, interpret and apply concepts in complex technical publications, manuals and other documents.
10. Maintains inventory of all computer hardware and peripherals, computer software, and office equipment in area of responsibility.
11. Provide assistance to the Supervisor; prepare administrative reports related to training and support activities; assist in design and development of computer laboratory facilities.
12. Learn the functions and limitations of assigned duties.
13. Assist other IT Center Personnel in their computer hardware problems
14. Understand the organization and operation of the assigned office and the Information Technology Center in order to assume assigned responsibilities.
15. Communicate effectively both orally and in writing.
16. Establish and maintain cooperative and effective working relationships with others.
17. Perform duties delegated by superior for the benefit of the IT Center and the school in general.

OTHER DUTIES:

Attend and participate in staff meetings and in-services activities; attend specialized training classes, attend workshops and conferences to increase professional knowledge of technologies and software.

Cyril Pauya

• I.T. Center Head
• Programmer
• Network Administrator

Edwin Resmenia

• Computer Technician Supervisor
• Officer-In-Charge (OIC) when the I.T Center Head is on-leave
• Computer Technician
• ETD Laboratory In-Charge
• HS Laboratory In-Charge

Lito Debabao

• Computer Technician
• Electronics Expert
• College Laboratory In-Charge
• Multimedia Staff

Nathaniel Varona (on leave)

• Computer Technician
• Network Administrator
• DMSST Laboratory In-Charge

Peter Bragais

• Computer Technician
• Internet Laboratory In-Charge
• Assistant Network Administrator
• Multimedia Staff

Ritche Corpuz

• Computer Technician
• College Laboratory In-Charge

Julius Ryan Bulahan

• Multimedia Supervisor
• Junior Programmer

Gary Abayata

• Multimedia Staff

Area Assignments (for Computer Technicians)

College Computer Laboratories

• Lito Debabao
• Ritche Corpuz

Internet Computer Laboratory

• Peter Bragais

High School Computer Laboratory

• Edwin Resmenia

Elementary Computer Laboratory

• Edwin Resmenia

DMSST Computer Laboratory

• Nathaniel Varona

Although each staff has his own responsibilities, everybody is required to cater the needs of the whole institution.

Example::

• When computer technicians are not busy in the computer laboratories, they will fix I.T. problems in the offices.

This document contains the guidelines in creating or reading such manuals.

An I.T. Center technical manual covers one or more of the following aspects:

• installation of computer software
• assembly of computer hardware
• computer repair and servicing
• network setup and administration

Symbols
The following symbols have special meaning in the I.T. Center Technical Manual:

• REQUIREMENTS::
  • lists all needed files, setup, or configuration for the process
• PART #::
  • a part in the over-all process of the manual
• STEP:: or STEPS::
  • steps on a particular part of the manual
    
• FIX::
  • a needed fix to prevent problems during or after the process
  • don’t ignore this!
• REF::
  • reference/s for the manual or part or step
  • necessary reading
• PRACTICE::
  • exercise to get familiar with the command/s or concepts
• bash script::
  • a bash script
  • font style must be monospace font (fixed width)
  • font size must be small font
    
• syntax::
  • command syntax to execute usually at the command prompt or shell
  • font style must be monospace font (fixed width)
  • font size must be small font
• >::
  • command/s to be executed in the shell
  • font style must be monospace font (fixed width)
  • font size must be small font
• example::
  
  • a sample, usually of a shell command
    
• Note:: or Notes::
  • a note or a lot of notes
• OPTIONAL::
  • an optional step in the manual
• todo::
  • something to do

There are two colons after the keywords to distinguish them from their English word counterparts.

Basic Format
Here is the basic format of an I.T. Center technical manual:

(Title)
(text)

REQUIREMENTS::
(text)

PART #::
(text)

STEP::
(text)

All of the other symbols are used whenever they are needed in the technical manual.

An I.T. Center technical manual is usually created using Tomboy Notes on an Ubuntu 9.04 desktop.

Windows XP displays the user name of the last user who logged-in to the computer. On a shared computer, this poses a security risk. To remove the display of the last user name in Windows XP, do the following:

STEPS::
• login as an Administrator in Windows XP
• run gpedit.msc on the command-line
• goto Local Computer Policy – Computer Configuration – Windows Settings – Security Settings – Local Policies – Security Options
• Double-click on Interactive logon: Do not display last user name
• On the window that pops-up, select Enabled.
• Restart the computer.

Related articles:
• Do not require Ctrl+Alt+Delete to login in Windows XP
• Setup a Laboratory File Server using eBox

Although this process is a security feature, the user could save time if we disabled this.

STEPS::
• login as an Administrator in Windows XP
• run gpedit.msc on the command-line
• goto Local Computer Policy – Computer Configuration – Windows Settings – Security Settings – Local Policies – Security Options
• Double-click on Interactive logon: Do not require CTRL+ALT+DEL
• On the window that pops-up, select Enabled.
• Restart the computer.

Related articles:
• Do not display last user name in Windows XP
• Setup a Laboratory File Server using eBox

REQUIREMENTS::

• see stud_faculty.sh (listed below)

STEPS::

• create stud.sh and put the following script:
• to add users from CSV file
  • > sudo bash ./stud.sh students.csv a
• to delete users listed at CSV file
  • > sudo bash ./stud.sh students.csv d
• Note:: experiment with adding two users by creating a temp.csv file with only two rows of data

stud_faculty.sh – begin

#!/bin/bash
<<comment
2009-07-16, cyril p.
--------------------
requirements:
	. groups must already be created at eBox web admin
	. students.csv must have already been uploaded
	. faculty.csv must have already been uploaded
	. students_faculty.csv - main input to this script

parameters:
	$1 = CSV file as source of ebox students_faculty information
		format: schedulecode, student_username, faculty_username
	$2 = commands
		a = give faculty access to student folder
		d = remove access of faculty to student folder

algorithm:
	1. check arguments
	2. check if being run by root user
	3. for each line in csv:
		convert special characters to plain character (ex: spanish n to n)
		a. check home directory of user
		b. create/delete the user
		c. set default password for user
		d. set user comment
		e. set ownership and permission to home directory
comment

#contants
EXPECTED_ARGS=2
E_BADARGS=65
E_NOTROOT=1
E_FILENOTFOUND=2
E_GROUPNOTFOUND=3
E_HOMEDIRNOTFOUND=4

#check if being run by root user
if [[ $EUID -ne 0 ]]; then
	echo "This script must be run as root, try: sudo $0 [arguments]."
	exit $E_NOTROOT
fi

#check arguments if complete
if [ $# -ne $EXPECTED_ARGS ]; then
	echo "Usage: $0 arg1 arg2"
	echo "   arg1 = [path to students_faculty.csv file]"
	echo "   arg2 = [a=give faculty access to user's folder or d=remove faculty access to user's folder]"
	exit $E_BADARGS
fi

if [ ! -e $1 ]; then
	echo "ERROR: The csv file '$1' does not exist."
	exit $E_FILENOTFOUND
fi

#loop thru each line in csv file
while IFS=, read schedulecode student faculty
do
	#NOTE: replace special character Spanish N with plain N
	student=${student/$'\303\261'/'n'}
	faculty=${faculty/$'\303\261'/'n'}
	#NOTE: replace \r in the last item on the line
	faculty=${faculty/$'\r'/''}

	student_group="${student}_group"
	#schedulecode_group="${schedulecode}_group"
	stud_path="/home/samba/users/${student}"
	faculty_path="/home/samba/users/${faculty}"
	stud_sched_path="${stud_path}/class/${schedulecode}"
	faculty_sched_path="${faculty_path}/class/${schedulecode}"
	link_stud_path="${faculty_sched_path}/${student}"

	#echo $schedulecode
	#echo $faculty
	#echo $student_group
	#faculty="serrano_michaelangelo"
	#student_group="aban_eduard_vincent_group"

	if [ $2 = 'd' ]; then
		#smbldap-groupmod -x "${student}, ${faculty}" ${schedulecode_group}
		smbldap-groupmod -x ${faculty} $student_group
		if [ -e $link_stud_path ]; then
			rm $link_stud_path
		fi
	elif [ $2 = 'a' ]; then
		#smbldap-groupmod -m "${student}, ${faculty}" ${schedulecode_group}
		smbldap-groupmod -m "${faculty}" $student_group
		if [ $? -ne 0 ]; then
			echo "ERROR: ${faculty} not added to ${student_group}."
		else
			#create a class schedule folder in student's home dir
			if [ ! -e $stud_sched_path ]; then
				mkdir -p $stud_sched_path
			fi
			chown ${student}:${student_group} $stud_sched_path
			#create a folder named after class schedule in faculty's home folder to contain links to student's home folder
			if [ ! -e $faculty_sched_path ]; then
				mkdir -p $faculty_sched_path
			fi
			chown ${faculty}:"Domain Users" $faculty_sched_path
			#now create the link to student's home folder
			if [ ! -e $link_stud_path ]; then
				echo "linking ${stud_sched_path} to ${link_stud_path}..."
				ln -n -s ${stud_sched_path} ${link_stud_path}
				#chown ${faculty}:"Domain Users" $link_stud_path
			fi
		fi
	fi 

	#exit 1
done < $1

stud_faculty.sh – end

• the ’student’ group must have been created prior to this step
• CSV schema: username,studentID,lastname,firstname,middlename
  • username is:
    • composed of lastname + ‘_’ + firstname
    • use alphabets and underscore only
    • must not have space
    • must be lower case
    • example:: doe_john
  • if firstname is more than two names, concatenate them with an underscore
    • example:: doe_john_mark
  • studentID serves as the default password of the user so it must not contain spaces
  • lastname, firstname, and middlename may contain spaces
• the following todo The NDMC EIS sql scripts are meant to
• contents of the CSV file comes from todo The NDMC EIS

STEPS::

• create stud.sh and put the following script:

	#!/bin/bash
	while IFS=, read username studentid lastname firstname middlename
	do
		echo "processing ${username}... $studentid"
		if [ $2 = 'd' ]; then
			smbldap-userdel -r ${username}
			echo "...removed $username"
		elif [ $2 = 'a' ]; then
			smbldap-useradd -a -N "$firstname" -S "$lastname" -G "student" ${username}
			echo "...successfully added $username, now setting password to ${studentid}..."
			smbldap-passwd $username $studentid
		fi
	done < $1
	# end of stud.sh

• to add users from CSV file
  • > sudo bash ./stud.sh students.csv a
• to delete users listed at CSV file
  • > sudo bash ./stud.sh students.csv d
• Notes::
  • experiment with adding two users by creating a temp.csv file with only two rows of data
  • use the eboxuser.sh script below, the above example would do but this script is more robust

------------------------------------
eboxuser.sh - begin
------------------------------------
#!/bin/bash
<<comment
2009-07-16, cyril p.
--------------------
requirements:
	1. group must already be created at eBox web admin
	2. csv file of users as source file

parameters:
	$1 = CSV file as source of ebox user information (format: username,studentid,lastname,firstname,middlename)
	$2 = commands
		a = add users based on $1
		d = delete users based on $1
	$3 = group where users initially belong

algorithm:
	1. check arguments
	2. check if being run by root user
	3. for each line in csv:
		convert special characters to plain character (ex: spanish n to n)
		a. create/delete home directory of user
		b. create/delete the user
		c. set default password for user
		d. set user comment
		e. set ownership and permission to home directory
comment

#contants
EXPECTED_ARGS=3
E_BADARGS=65
E_NOTROOT=1
E_FILENOTFOUND=2
E_GROUPNOTFOUND=3
E_UNKNOWN=555

#check if being run by root user
if [[ $EUID -ne 0 ]]; then
	echo "This script must be run as root, try: sudo $0 (arguments)."
	exit $E_NOTROOT
fi

#check arguments if complete
if [ $# -ne $EXPECTED_ARGS ]; then
	echo "Usage: $0 arg1 arg2 arg3"
	echo "    arg1 = (path to csv file)"
	echo "    arg2 = (a=add users or d=delete users)"
	echo "    arg3 = (group)"
	exit $E_BADARGS
fi

if [ ! -e $1 ]; then
	echo "ERROR: The csv file '$1' does not exist."
	exit $E_FILENOTFOUND
fi
<<comment
#these codes don't work, but kept here for reference purposes
/bin/egrep -i "^${3}" /etc/group
echo "$?"
if [ $? -eq 0 ]; then
	echo "ERROR: There is no '${3}' group."
	exit $E_GROUPNOTFOUND
fi

#create group
if [ $2 = 'd' ]; then
	smbldap-groupdel $3 > /dev/null
elif [ $2 = 'a' ]; then
	smbldap-groupadd -a "${3}" > /dev/null
fi
comment

#loop thru each line in csv file
while IFS=, read username studentid lastname firstname middlename
do
	echo "processing ${username}, $studentid as ${username/$'\303\261'/n}..."

	#IMPORTANT: replace special character Spanish N/n with plain N/n
	username=${username/$'\303\221'/'N'}
	username=${username/$'\303\261'/'n'}
	lastname=${lastname/$'\303\221'/'N'}
	lastname=${lastname/$'\303\261'/'n'}
	firstname=${firstname/$'\303\221'/'N'}
	firstname=${firstname/$'\303\261'/'n'}
	middlename=${middlename/$'\303\221'/'N'}
	middlename=${middlename/$'\303\261'/'n'}

	username_group="${username}_group"

	#create a group based on username
	if [ $2 = 'd' ]; then
		smbldap-groupdel ${username_group} #> /dev/null
	elif [ $2 = 'a' ]; then
		smbldap-groupadd -a -p "${username_group}" #> /dev/null
	fi

	profiles_dir="/home/samba/profiles/${username}"
	home_dir="/home/samba/users/${username}"
	if [ $2 = 'd' ]; then
		if [ -e $profiles_dir ]; then
			rm $profiles_dir -r
		fi
		smbldap-userdel -r $username
		echo "...removed ${username}"
	elif [ $2 = 'a' ]; then
		#create the user's home directory
		if [ ! -e $home_dir ]; then
			echo "...creating home dir for ${username}..."
			cp -r /etc/skel $home_dir
		fi

		#create the user's home directory
		if [ ! -e $profiles_dir ]; then
			echo "...creating profile dir for ${username}..."
			mkdir -p $profiles_dir
		fi

		#create the user
		smbldap-useradd -a -d $home_dir -A 1 -N "$firstname" -S "$lastname" -G "$3,${username_group}" ${username} #> /dev/null
		if [ $? -ne 0 ]; then
			echo "ERROR: code $? - user '${username}' not created (maybe group '$3' was not created?)"
			exit $E_UNKNOWN
		else
			#set profile variables to
			smbldap-usermod -C "" $username
			smbldap-usermod -D "" $username
			smbldap-usermod -E "" $username
			smbldap-usermod -F "" $username

			#set default password
			echo "...${username} added, now setting password..."
			smbldap-passwd $username $studentid > /dev/null

			#set user comment
			echo "...password set, now setting comment..."
			smbldap-usermod -c "${lastname} - ${firstname} - ${middlename}" $username 

			#set ownership and permission to home dir
			echo "...comment set, now setting ownership and permissions to home dir..."
			#chown -R "${username}":"Domain Users" $home_dir
			chown -R "${username}":"${username_group}" $home_dir
			chmod -R u=rwx,g=rx,o=x $home_dir

			chown -R "${username}":"Domain Users" $profiles_dir
			chmod -R u=rwx,g=,o= $profiles_dir

			echo "...successfully added $username."
		fi # useradd
		#fi #groupadd
	fi
done < $1
------------------------------------
eboxuser.sh - end
------------------------------------

Take note that this setup applies to a virtual machine created under Proxmox Virtual Environment. For more information, go to todo Creating a Virtual Private Server using Proxmox Virtual Environment.

Table of Contents

• Introduction
• Considerations and Solutions
• REQUIREMENTS:: Needed Files and Software
• eBox 1.2 installation (Proxmox Virtual Machine, 512mb memory, 90gb hd)
  • PART 1:: Ubuntu base install (20 mins)
  • PART 2:: eBox base install
  • PART 3:: eBox settings
  • PART 4:: File server settings
  • PART 5:: Make sure there are no special characters in the names (found at the CSV files):
  • PART 6:: Bulk-create student users
  • PART 7:: Bulk-create teacher users
  • PART 8:: Bulk-assign teacher access to students taught
  • PART 9:: todo Assign quotas to users.
• Windows XP configuration
  • todo Join a Windows XP computer in a Domain
  • Do not require Ctrl+Alt+Delete to login in Windows XP
  • Do not display last user name in Windows XP

Considerations and Solutions
The following are the considerations in the setup of a laboratory file server:

• use a static IP address of 192.168.1.3
• use LAB.NDMC.EDU.PH domain
• encoding of domain users
• hard disk quota
• shares

Computation for Hard Disk Quotas

• faculty => 100mb * 12 = 1.2gb
• students => 50mb * 1,000 = 50gb
• admins => 100mb * 6 = 0.6gb
• visitors => 100mb * 1 = 0.1gb
• total => 51.9gb

Computation for Shares

• class schedules => 100mb * 81 = 8.1gb
• cite_faculty => 5.0gb
• dmmst faculty => 1.0gb
• itc => 10gb
• total => 24.1gb

Hard disk use over-all total => 76.0gb

REQUIREMENTS:: Needed Files and Software

• smbldap-passwd
  • a modified smbldap-passwd file to allow setting a user’s password in the command line (removed the verification messages)
• eboxuser.sh
  • Bash script to create users in eBox
• stud_faculty.sh
  • Bash script to give teachers access to their student’s subject folders in eBox
• students.csv
  • a csv file of students enrolled in laboratory subjects
• cite_faculty.csv
  • a csv file of cite faculty teaching laboratory subjects
• students_cite_faculty.csv
  • a csv file of students handled by a cite_faculty (many-to-many)

eBox 1.2 installation (Proxmox Virtual Machine, 512mb memory, 90gb hd)

Most texts in the following installation parts are answers to each screen display during installation.

PART 1:: Ubuntu base install (20 mins)

• english
• install
• language -> english
• country -> Philippines
• detect keyboard layout? -> no
• origin of keyboard -> usa
• keyboard layout -> usa
• hostname -> fs-lab
• time zone -> pacific
• configuring the network with dhcp -> cancel
• configure the network
  • continue
  • configure network manually
  • ip address -> 192.168.1.3
  • netmask -> 255.255.255.0
  • gateway -> 192.168.1.1
  • name server addresses -> 192.168.1.1
  • host name -> fs-lab
  • domain name -> ndmc.edu.ph
• partition disks -> guided – use entire disk
• disk to partition -> scsi1 (sda1)
• write changes to disk? -> yes
• full name for the new user -> Cyril Pauya
• username -> cpauya
• password -> password
• http proxy information -> <blank>
• Note:: 15 minutes of setup…
• system clock to utc? -> yes
• proxmox->vm->first boot device to hard disk
• Note:: Do not remove the installation cd! Just set the bios to boot from hard disk.
• installation complete -> continue

PART 2:: eBox install

• vm will give error of non-bootable device
• proxmox->stop vm
• proxmox->start vm
• proxmox->open vnc console
• vm will install packages from cd
• choose package selection method -> simple
• choose a profile -> tick office (file sharing, printers, groupware)
• Note:: 8 minutes of setup…
• password for eBox interface -> password
• confirm password for eBox interface -> password
• select external interfaces -> do not tick eth0 (just press enter here)
• default virtual mail domain -> ndmc.edu.ph
• Note:: 4 minutes of setup…
• installation finished -> point your web browser to https://192.168.1.88/ (IP address may vary)

——————————————————————–
update to ebox-network 1.2.1:
——————————————————————–
notes:
. this is necessary because eBox has a bug when restarted, the network (eth0) cannot be found
. this process is not needed in use of eBox 1.2
ref: http://forum.ebox-platform.com/index.php?topic=1526.0
deb: https://launchpad.net/~ebox/+archive/1.2/+build/1116292steps:
1. copy .deb file to /home/cpauya/ using nautilus
>:: ssh cpauya@192.168.1.88
>:: use password as password
>:: copy .deb file
2. install updates using dpkg
>:: ssh cpauya@192.168.1.88> use password as password
>:: sudo dpkg -i <deb file>
3. enter the password for eBox web interface
>:: password
4. update finished -> point your web browser to https://192.168.1.88/ (IP address may vary)

PART 3:: eBox settings

• Note:: These steps and the Fix:: Fix Samba problems after an IP change step only applies if you have NOT configured the network manually at Part 1:: Ubuntu base install.
• login to https://192.168.1.88/ (IP address may vary)
• select Core->Network->Interfaces
• select Method->Static
• enter 192.168.1.3 at IP address
• click Change
• click Save Changes – red link at top-right portion
• a warning will popup, just click on the green check icon
• save configuration -> click Save
• after a minute, login to https://192.168.1.3/
• vm->stop
• vm->remove the eBox iso from cd
• vm->start
• repeat steps in PART 2: eBox install

FIX:: Fix Samba problems after an IP change.
REF:: http://xania.org/200809/samba-problems-after-ip-change

• stop samba
  • >:: sudo /etc/init.d/samba stop
• delete cached samba files
  • >:: sudo rm /var/cache/samba/browse.dat
  • >:: sudo rm /var/lib/samba/wins.dat
• start samba
  • >:: sudo /etc/init.d/samba start

Note:: Repeat this process if after adding a machine, it cannot join the domain.

Enable Primary Domain Controller (PDC) at eBox’s web administration site

• login to https://192.168.1.3/
• goto Office->File Sharing->General Settings
• Enable PDC: checked
• Domain name: COL-LAB
• Netbios name to: fs-lab
• Description: College Laboratories Server
• Quota limit: Limited to: 100mb
• Enable roaming profiles: checked
• Drive letter: H:
• click Change

PART 4:: File server settings.

• login to https://192.168.1.3/
• create the following groups
  • itc
  • cite_faculty
  • dmsst_faculty
  • faculty
  • student
  • visitor

PRACTICE:: Add samba/ldap users for eBox in the shell.

• syntax::
  • >:: sudo smbldap-useradd -a -m -N “firstname” -S “lastname” -G “group” <username>
• example::
  • >:: sudo smbldap-useradd -a -m -N “john” -S “doe” -G “student” doe_john

Note:: The password of the user has not been set here, refer to smbldap-passwd.

PRACTICE:: Delete user from samba/ldap in the shell.

• syntax::
  • >:: sudo smbldap-userdel -r <username>
• example:
  • >:: sudo smbldap-userdel -r doe_john

Note:: The -r switch removes the home directory of the user.

FIX:: Modify smbldap-passwd to accept username and password from the command line.
REF:: http://alex.ricobon.ro/wiki/index.php?title=How_to_make_a_script_that_adds_users_from_a_list

• backup the original /usr/sbin/smbldap-passwd
  • >:: sudo cp /usr/sbin/smbldap-passwd /usr/sbin/smbldap-passwd.bak
• replace /usr/sbin/smbldap-passwd with the modified version
  • >:: sudo cp smbldap-passwd /usr/sbin/smbldap-passwd

bash script:: Bash script to create users in eBox

STEP:: Add <computer name>$ to samba.

• syntax::
  • >:: sudo smbldap-useradd -w (computer name with $ in the end)
• example::
  • >:: sudo smbldap-useradd -w virtual-xp$

STEP:: Add machine script on /etc/samba/smb.conf.

• add machine script = /usr/sbin/useradd -s /bin/false -d /home/nobody %u

STEP:: Add root to samba to connect windows clients to domain.

• >:: sudo passwd root
• Note:: We do this because we haven’t set any password for root yet.
• >:: (type new password of root)
• >:: su
• >:: (type password of root)
• >:: smbpasswd -a root
• >:: (type new SMB password of root)

OPTIONAL:: Install smbclient for monitoring samba setup.

• syntax::
  • >:: sudo apt-get install smbclient
• example::
  • >:: sudo smbclient -L localhost
• Note:: This might fail if no gateway has been configured for the eBox machine.

STEP:: Map drive H to user’s home directory.

• edit /etc/samba/smb.conf
  • >:: sudo /etc/samba/smb.conf
• Note:: Comment the ‘logon home =’ entry to automatically map H: to user’s home directory.
• change ‘logon home =’ to ‘#logon home =’
• save
• restart samba
  • > sudo /etc/init.d/samba restart

OPTIONAL:: Set /home/samba/netlogon/logon.bat for other user-specific settings.

PART 5:: Make sure there are no special characters in the names (found at the CSV files).

• replace Ñ (N with tilde) with N
  • UTF-8: 0xC3 0×91
  • UTF-16: 0×00D1
  • C octal escaped UTF-8: \303\221
  • XML decimal entity: &#209;
• replace ñ (n with tilde) with n
  • UTF-8: 0xC3 0xB1
  • UTF-16: 0×00F1
  • C octal escaped UTF-8: \303\261
  • XML decimal entity: &#241;
• in Linux, EOF is denoted by \r whereas EOF in Windows is using \r\n
  • replace \r in the CSV input files
• save file using utf-8 encoding
• notes::
  • the conversion of Spanish N and the replacement of \r is already done by eboxuser.sh and stud_faculty.sh scripts
  • just make sure to save as utf-8 encoding

PART 6:: Bulk-create student users.

• to create the students
  • >:: sudo bash ./eboxuser.sh students.csv a student
• to delete the students
  • >:: sudo bash ./eboxuser.sh students.csv d student

PART 7:: Bulk-create teacher users.

• to create the teachers
• >:: sudo bash ./eboxuser.sh cite_faculty.csv a cite_faculty
• to delete the teachers
• >:: sudo bash ./eboxuser.sh cite_faculty.csv d cite_faculty

PART 8:: Bulk-assign teacher access to students taught.
This process has the following effects for the teacher:

• creates a ‘class’ folder in the home folder
• this folder contains the folders named after the class schedules taught by the teacher
• each schedule folder contains soft-links to the schedule folder of the students named after the student
• example::
  • doe_john (teacher)
    • class (class folder)
      • cs_414 (schedule folder)
        • mcalister_jane (student’s schedule folder named after the student)
        • smith_clark (student’s schedule folder named after the student)

For the student, this process does the following:

• creates a ‘class’ folder in the home folder
• this folder contains the folders named after the class schedules taught by the teacher
• example::
  • mcalister_jane (student)
    • class (class folder)
      • cs_414 (schedule folder)
      • cs_411 (schedule folder)

The following steps must be done:

• edit /etc/samba/smb.conf
  • >:: sudo /etc/samba/smb.conf
  • change [homes]->valid users = %S to [homes]=>#valid users = %S
  • save (press ctrl-K, press y, press enter)
• restart samba
  • >:: sudo /etc/init.d/samba restart
• bulk-assign teacher access to student’s folders
  • >:: sudo bash ./stud_faculty.sh student_cite_faculty.csv a
• delete the bulk-assignment of teacher access to student’s folders
  • >:: sudo bash ./stud_faculty.sh student_cite_faculty.csv d

PART 9:: todo Assign quotas to users.
The ebox_user.sh script should be modified to include quota assignments per user:

• those enrolled in multimedia subjects must have a 1gb quota
• those enrolled in other subjects may have a 100mb quota
• teachers should have a 1gb quota

FINISHED!

The software are categorized here for reference:

Antivirus Software

• Avast Antivirus

Archive / Compression Software

• WinRar

Database Management Systems

• Microsoft Access 2003
• Microsoft SQL Server 2000
• Microsoft SQL Server 2005
• MySQL 5
• PostgreSQL 8.3

Integrated Development Environments (IDEs)

• Java Creator
• Microsoft Visual Basic 6.0
• NetBeans
• Turbo C/C++ 3.0

Finance Software

• Integrated Accounting 3.0
• Peachtree Accounting 2005

Office Suite

• Adobe Pagemaker 7
• Microsoft Office Excel 2003
• Microsoft Office Word 2003
• Microsoft Office Powerpoint 2003
• OpenOffice 3.0

Operating Systems

• Windows XP Professional with SP2

PDF Document Readers

• Adobe Acrobat Reader

Photo-Editing Software

• Adobe Illustrator CS 2
• Adobe Photoshop CS 2

Programming Platforms

• Microsoft Visual Studio.NET 2005
• Sun Java 6

Text-Editors

• Notepad++

Sandbox Software

• DeepFreeze

Web Browsers

• Mozilla Firefox

Web / Flash Development

• Adobe Flash

3-D Modelling

• Google Sketch-Up

Efforts are now underway to include Open-Source operating systems like Ubuntu 9.04 desktop.

The I.T. projects that the I.T. Center implements ranges from any of the following:

• software development
• software benchmarking and deployment
• network setup and maintenance
• systems administration

These are the members of the I.T. Project Management Team:

1. Project Sponsor

This is usually the President of the school, Fr. Romeo S. Saniel, OMI. Being the final decision-maker, he gives a project its approval and the needed financial elements.

2. Project Manager
Most I.T. projects are usually managed by the ITC Head, Mr. Cyril Pauya. Sometimes, I.T. consultants are tapped for bigger or enterprise-wide projects.

3. Project Beneficiary
Most of the time this is a school unit or department who needs automation in it’s business processes. For maintenance works, this is usually the end-user who requested additional features or reports for an application.

The Process

• Scoping during a project meeting with all members of the team.
• Requirements gathering by the Project Manager with the Project Beneficiary.
• Approval by the Project Sponsor.
• Build, test and deploy by the I.T. Center.
• Evaluation by the Project Beneficiary.
• Maintenance by the I.T. Center.

Meetings
The team meets only when there are decisions that would involve all team members. In most cases however, it is the Project Manager and the Project Beneficiary who always meets specially during the development of the project.

Funding
Funding are usually taken from the Project Beneficiary’s department. In this case, an entry must be made in the department’s budget prior to the start of the school year for approval of the Board.

If the project scope is institutional, finances are backed by the Administration.

Table of Contents

• Introduction
• Current Issues and Practices
• Proposed Solution
• The I.T. Project Management Team
• Issues, Apprehensions, Concerns
• Criteria for Deployment
• Conclusion

Current Issues and Practices
The current setup suffers from the following problems:

• lost exercises of students due to:
  • pranksters who deletes the files of others
  • viruses and other malwares
• no privacy in the files of other students
  • other students in other classes may browse thru the files and are tempted to copy their exercises
• no automated backup of files
• students cannot continue their exercises in another computer if their assigned unit is being serviced
• teachers have no centralized way of checking exercises
  • checking must be done in each computer or during classes
• viruses and malwares
  • USB flash disks are major carriers of viruses and malwares

Aside from the above problems, the following todo I.T. Center best practices poses a threat in the successful implementation of a Laboratory File Server:

• todo Using DeepFreeze software
  • This software “freezes” the system partition (commonly known as Drive C). System changes of the user are lost once the computer is reset.
  • If the computer is joined in a domain, the roaming profile of the user will not be saved locally.
• Microsoft Windows XP user is an administrator account
  • All domain users (except the administrator/root accounts) are set to the “limited users” account type of Microsoft Windows XP. Some Software in the Computer Laboratories requires that the software be run by an administrator account and would therefore not run properly once the computer joins a domain.
    • An example is Microsoft Visual Basic 6.0. Using the professional components under a limited user account generates an error because the account cannot access the necessary registry entries of the components.

The above practices must be reviewed and tested to work in the domain computers.

Proposed Solution
The solution is to Setup a laboratory file server using eBox. This will achieve the following:

• repository of student’s files
• centralized checking of exercises by the teachers
• centralized backup of files

The following File Server features must be met:

• user accounts for teachers and students
• user accounts must use the full name of teacher or student
  • username = lastname_firstname (ex: doe_john)
  • password = defaults to the ID number from todo The NDMC EIS (ex: 09-0321)
• user name cannot be changed
• special characters Ñ or ñ converted to N or n
• users can still login to local PC’s accounts, just in case
• disk quotas of 1gb per student
• soft-links to class schedules (mapped to drive H)
• read-only access of teachers to student’s subject folders
• use of LAB.NDMC.EDU.PH domain
• use of Free and Open-Source Software (FOSS) to avoid software licensing costs in the servers
  • eBox 1.20 using Ubuntu 8.04 server

ITC Standard Operating Procedures

• Semestral tasks
  • clean-up of accounts
  • auto-encoding of student accounts based on todo The NDMC EIS
  • format of client computers (todo Using Norton Ghost)
• Monthly tasks
  • virus scanning of home directories
    • this could be automated using Linux services or daemons
• Anytime
  • account maintenance
    • creation of accounts
    • password changes
    • backup of files

The I.T. Project Management Team
This endeavor is of great value to the teachers and students using the College Computer Laboratories. It must therefore be treated with careful planning and execution considering that the grades of the students are at stake. The following are the members of the Project Management Team (PMT):

• Project Sponsor
  • Fr. Romeo S. Saniel, OMI – NDMC President
• Project Manager
  • Cyril Pauya – ITC Head
• Project Beneficiaries
  • todo College of Information Technology and Engineering
  • students of the other NDMC Colleges

Issues, Apprehensions, Concerns
The following must be considered in the implementation of a laboratory file server:

• all Software in the Computer Laboratories must be tested to run under Microsoft Windows XP’s limited account (ex: vb6)
• todo Guidelines in the Responsible Use of Computers and Networks
• account-related concerns:
  • long username
  • password changes (require users to change passwords every month?)
  • require users to press Ctrl-Alt-Delete to login
• protection against viruses and malwares
• stability of file server
• stability of network
• redundancy of:
  • power
  • file server
  • storage (hardware raid)
  • client computers (standby computers)
• file server maintenance
• backup of accounts including files

Additional Features necessary as of August 04, 2009:

• teacher access for:
  • scheduling
  • lock-in of student’s subject folders
  • sending messages to a student or the whole class

Criteria for Deployment
The following must be met before actual deployment of the Laboratory File Server:

• all client computers must have joined the LAB.NDMC.EDU.PH domain
• successful testing in one computer laboratory for a month
• list of final subjects with student names and ID numbers from todo The NDMC EIS
• all items under Issues, Apprehensions, Concerns are addressed

Conclusion
This is an endeavor that would change the way teachers and students use the College Computer Laboratories. It introduces a lot of technical challenges to todo the I.T. Center but with the guidance of the I.T. Project Management Team, and collaboration with todo College of Information Technology and Engineering, this project will solve the problems suffered by the teachers and students and make way for better todo I.T. services by the I.T. Center.

Each laboratory has a floor area of 81 square meters, with a dimension of 9m x 9m.

These laboratories operate from 7:00am until 8:00pm on weekdays. Software installation and general cleaning is done on Saturdays. Some weekend classes or community extension services are scheduled every Sundays.

Table of Contents

• Laboratory Equipment
• Installed Software
• Lab 1 Computer Specifications
• Lab 2 Computer Specifications
• Lab 3 Computer Specifications
• Networking
• Internet
• File Server
• Printing
• Computer Upgrade
• Black-outs

LABORATORY EQUIPMENT
Here are the equipment installed on each computer laboratory:

• airconditioning units (two 2hp units);
• wall fans;
• exhaust fans;
• emergency lights;
• fire extinguishers;
• circuit breakers (outlets, aircon, lights)

top

INSTALLED SOFTWARE
The software to be installed on the computers depends on the following criterias:

• assigned laboratory;
• types of subjects taught;
• requests by teachers

In coordination with the CITE Dean, here are the main uses of each college computer laboratory:

• lab 1 is for high-end and major subjects of I.T. students.
• lab 2 is for intermediate subjects of I.T. students.
• lab 3 is for computer introductory subjects with some intermediate subjects.

All computer laboratories are used for introductory subjects.

Introductory subjects include basic computer concepts, word processing, spreadsheet, and presentation software. Software used for these subjects are:

• Integrated Accounting 3.0
• Microsoft Office Word 2003
• Microsoft Office Excel 2003
• Microsoft Office Powerpoint 2003

Intermediate subjects include programming subjects in Assembly, C, C++, Java, MS Access 2003 and Visual Basic 6. It also includes web development subjects. Software used for these subjects include:

• Integrated Accounting 3.0
• Peachtree Accounting 2005
• Notepad++
• Sun Java 6
• NetBeans
• Java Creator
• Turbo C/C++ 3.0
• Microsoft Access 2003
• Microsoft Visual Basic 6.0
• Microsoft SQL Server 2000

High-end subjects are usually the advanced and most recent software technologies in the industry which include subjects in audio and video editing, 3-D layouting, and high-end programming platforms. Software used for these subjects include:

• Integrated Accounting 3.0
• Adobe Photoshop CS 2
• Adobe Illustrator CS 2
• Adobe Flash
• Google Sketch-Up
• Microsoft Visual Studio.NET 2005
• Microsoft SQL Server 2000
• Microsoft SQL Server 2005

Here are the standard software installed in all computers regardless of which laboratory they are:

• Windows XP Professional with SP2
• Adobe Acrobat Reader
• WinRar
• Mozilla Firefox
• Microsoft Office 2003
• Microsoft Access 2003
• OpenOffice 3.0
• Avast Antivirus
• DeepFreeze

top

LAB 1 COMPUTER SPECIFICATIONS
Lab 1 computers are usually the most recently purchased computers. It therefore has the same computer specifications detailed as follows:

• Core2Duo 2.4ghz cpu
• Asus P5B-MX motherboard (built-in network, sound, video cards, 4 USB 2.0 ports)
• 1gb ddr2 memory
• 256mb/64-bit nvidia graphic cards
• 160gb sata hard disks
• casing has I/O slots in front (speaker, microphone, 2 USB ports)
• 16″ LCD monitors (wide-screen)
• 500watts avr

Everybody wanted to be assigned to Lab 1.
top

LAB 2 COMPUTER SPECIFICATIONS
Lab 2 computers have mixed specifications:

• Celeron 2.0ghz / 2.2ghz / 2.4ghz cpu
• Asus motherboard
• 256mb / 512mb DDR1 memories
• 40gb / 80gb ide hard disks
• motherboard has USB 2.0 slots at the back
• 15″ crt monitor
• 500watts avr

top

LAB 3 COMPUTER SPECIFICATIONS
Lab 3 computers are mixed with multi-user devices, specifically OfficeStation devices. This allows a single desktop computer (host) to be shared by at least 7 users. There are only 24 OfficeStation devices in Lab 3 and the rest are personal computers with varying specifications.

There are 4 OfficeStation host computers in Lab 3 with the following specs:

• Core2Duo 2.4ghz cpu
• Asus P5B-MX motherboard (built-in network, sound, video cards, 4 USB 2.0 ports)
• 2gb ddr2 memory
• 160gb sata hard disk
• 600VA UPS
• 15″ crt monitor

The OfficeStation devices are modeled L-110 (no USB ports). Each device has video, mouse, keyboard, microphone, speaker, network and power slots. They only consume 5watts of electricity making them a practical choice for basic computer subjects. The following items are attached to each L-110 OfficeStation device:

• keyboard
• mouse
• UTP wire (network cable)
• 15″ crt monitor
• 500watts avr

The personal computers at Lab 3 ranges from the following specifications:

• Celeron 1.2ghz to Pentium 4 1.4ghz
• 256mb or 512mb DDR1 memories
• 40gb ide hard disks
• 15″ crt monitor
• 500watts avr

You could say that Lab 3 is not the favorite laboratory.
top

NETWORKING
All computers use motherboards with built-in network cards that make networking in the laboratories easy. Each laboratory is networked using two 24-port switches. Each laboratory is attached to an 8-port switch that connects to the Internet gateway.

Each computer is configured to automatically get a network IP address from a DHCP server.

The Internet connection of a laboratory is turned-off by default. Meaning, it is disconnected from that 8-port network switch. This means also that there is no IP address automatically assigned to a computer.

A teacher who wishes to use the Internet for a subject will just request an ITC staff to connect that laboratory to the switch. With this setup, even if there are no ITC staff available, the teacher can connect the UTP wire himself/herself to use the Internet in a laboratory.
top

INTERNET
The Internet gateway is a Linux server which is also a DHCP server. It has a public static IP address that connects to the Internet and a secondary private static IP address that connects to the 8-port switch. It uses Untangle 6.2.0, a software that is an operating system and a web filter in one package.
top

FILE SERVER
There is a Linux computer that serves as the file server (FS) for the students and teachers. It uses Ubuntu 8.04 server, with Samba and OpenLDAP. It acts as the Primary Domain Controller (PDC) for the Windows XP computers in the laboratories.

Each student and teacher is created an account in the FS. There is also a visitor account for guest users of the laboratories.

Each student is given their own home folders. Inside that folder is a subject folder which is named based on their enrolled subjects. Students must save their exercises and other files related to the subject into that subject folder. Whoever teaches that particular subject has read-only access to that directory. There is a 100mb disk quota for each student.

Each teacher also has their own home folders. They have read-only access to the subject folders of their students. There is a 100mb disk quota for each teacher.

With this setup, students could not complain of “lost or deleted” exercises which is rampant in stand-alone, shared computers. Teachers has a centralized location of which to check their students’ exercises.
top

PRINTING
A standby LX-300 printer is available for use by the students. The teacher can request for its installation and use during a class from the ITC staff. Papers must be provided by the students, only the printer and it’s ribbon are provided by the I.T. Center.
top

COMPUTER UPGRADE
Computers are replaced every 3 years and they are purchased in bulk of 40 computers. With 3 computer laboratories, you could say that we replace computers every year.

New computers are put in Lab 1. Existing units at the Lab 1 are put in Lab 2, and those in Lab 2 are put in Lab 3. Existing Lab 3 units are:

• set aside as standby computers; or
• re-used in the offices; or
• transferred in a new computer laboratory; or
• sold in a garage sale.

Computers with defective parts are replaced with standby computers (usually with much lesser specifications) while being serviced. Standby computers are necessary so that classes can continue with minimal or no disruption at all.
top

BLACK-OUTS
In Midsayap, electrical black-out happens at least 20 hours in a week. The school has a standby generator but it can supply only enough power for lights, fans, and some appliances during office and class hours.

When on generator power, airconditioning and computer units are not used; only wall fans and lights can be used.

Whew, that was quite a long list.