("michael yap");

For a typical software engineer systems administration is not part of their field and scope anymore. Simply because there is a part of I.T industry that handles these tasks. Obviously they are called System administrator. These guys are responsible for the entire I.T infastructure, from server, networks and hardware.

Started it out as obligation (which my history tells about being a working student before) that become a serious hobby until now. I also wanted to become a System Admin that is why a couple of years ago I established my own server and hosting several sites in the web. Actual experience and implementation (and trial & error ofcourse) of several administration makes my confidence in this field.

Servers used (both 32 and 64bit has been used)

Ubuntu Server Edition (from feisty fawn to Hardy Heron LTS)

Debian Lenny (currently using now)

Microsoft Windows Server (from 2003 to 2008 R2)

Implementations

DNS (BIND and MS DNS)

FTP (ProFTPd and MS FTP 7.5)

SMTP (Posfix and Kerio)

WWW (Apache,Ngix,Tomcat 6 and IIS 6-7.5)

compiled a custom Ngix-PHP FPM for a High Performance server

SVN (Apace DAV/SVN and VisualSVN for Windows)

Database (MySQL and MS SQL 2005-2008)

Hosting (VirtualMin)

Admin tools (has years of experience in Webmin)

Firewall (iptables,shorewall and MS Windows Server 2008 Firewall)

Can write Shell and Perl Sripts (not fully for programming level/development)

Virtualization (been using VMware Server and ESXi)

BitRate Throttling, Dynamic IP restriction and Media Streaming Server (2008 R2)

Application Request Routing / Proxy Server (2008 R2)

VPN Server(SSTP,PPTP with NPS implementation in 2008 R2 and PPTP in Linux)

Can Setup/Configure full load balancing Server/Router (using RAS in 2008 R2 and Shorewall in Linux)

XMPP/IM Server using Openfire (with Kraken IM Gateway) in Linux.

LDAP (also made a .Net application ported via Mono (Novell library not Windows AD)

Jira,Confluence,Fisheye,Nagios,Centreon,Chef (also made receipes)