System Administrator Appreciation Day

Originally posted @ Friday, July 31, 2009

A sysadmin unpacked the server for this website from its box, installed an operating system, patched it for security, made sure the power and air conditioning was working in the server room, monitored it for stability, set up the software, and kept backups in case anything went wrong. All to serve this webpage.

A sysadmin installed the routers, laid the cables, configured the networks, set up the firewalls, and watched and guided the traffic for each hop of the network that runs over copper, fiber optic glass, and even the air itself to bring the Internet to your computer. All to make sure the webpage found its way from the server to your computer.
A sysadmin makes sure your network connection is safe, secure, open, and working. A sysadmin makes sure your computer is working in a healthy way on a healthy network. A sysadmin takes backups to guard against disaster both human and otherwise, holds the gates against security threats and crackers, and keeps the printers going no matter how many copies of the tax code someone from Accounting prints out.
A sysadmin worries about spam, viruses, spyware, but also power outages, fires and floods.

Direct Access LAB

Originally posted @ Thursday, July 30, 2009

For the last 2 days I was trying to set up a Direct Access connection here on my house with virtual machines by reproducing the follwing lab on a virtualized envoirement:

Quoting Microsoft
DirectAccess is a new feature in the Windows® 7 and Windows Server® 2008 R2 operating systems that enables remote users to securely access intranet shares, Web sites, and applications without connecting to a virtual private network (VPN). This paper contains an introduction to DirectAccess and instructions for setting up a test lab to demonstrate DirectAccess with a simulated Internet, intranet, and home network using the Release Candidate versions of Windows 7 and Window Server 2008 R2.

This lab came on the right time, I just installed Hyper-V R2 Server on a machine I have here at home just testing stuff, currently an AMD X2 5400+ with 4GB ram, but I got stuck when it required me 2 Public IP address… I didn’t reproduced the full lab, I wanted to make it for real, like accessing to my home from outside without having to create any kind of VPN… so I’ve skipped the creation of a virtual “internet” as described on the paper…

It might have worked If I routed all my trafic by a second subnet but I didn’t wanted to go that far… I’ve registered on a webcast that will be held by Keith Combs on 19/08/2008 called “TechNet Webcast: Connect Remotely Using Windows 7 Direct Access (Level 300)”

I’ll keep in touch regarding this subject on a near future…

Right now I’m thinking on my next LAB using virtualization…