Sunday, November 2, 2014

Technology Tribulations (Introduction To Servers)

Note I'm still learning the the arena of servers, and network administration so take this into consideration whilst I write my experiences here.

Since I've been in the enterprise world I've only had the opportunity recently to delve into servers. At first I felt intimidated, and a tad overwhelmed.

Most of what I learned about AD(Active Directory), Domain Controllers with my nascent but brief touch of Server (2003), and being thrown into the lava pit with Server 2008 is how they function with the network. My initial time with a unnamed company didn't have the right recourse to setup the proper server, so I was tasked with modifying the server to fit a much more secure format.

Each of these systems (at first) seemed pretty straightforward. Only if you understand how Tree's and Forests work. Since my time with Linux definitely prepared me, yet I'm still learning the ins and outs, but there are lots of little things to consider with servers.

What can a server do? Why are there so many variations of servers out there? First question tends to be the most obvious in that servers do a lot of little things behind the scenes, pretty much servers are the network backbone of the entire internet (if we want to use that term). The second question is more specific about flavor, what a server is typically used for. There again is the networking component, you could use it as a file server, you can setup a domain controller, you could use it as developer box, there are many considerations to think about with what a server can do for business and an average home user.

I have learned servers are a central point for application use, networking, (some) endpoint protection, development, virtualization, cloud hosting, heck this list can continue on and on.

The other aspect of servers is the robustness, yet there are rules in which to understand the functioning aspect of a server. One doesn't need to figure out that a single mistake can totally botch an entire setup, and/or network connection. (I have done this by accident) All it takes is that proverbial oops, and that is the last thing one wants to hear if your a systems admin.

In the last year I've had some time to acclimate (as it were) to Server 2012. I've been working through two pieces, the Domain Controller (AD, and Powershell). Two specific things that I think make what an IT person does more efficient at management.

I must stress that Server 2012 is different. It is a paradigm shift. Going away from the typical point and click GUI of prior versions, there is this extra step that can overwhelm.


It is powerful, there really neat things with virtualization aspect, I didn't get into the Azure yet, cloud service, and program development, but for what I want it is only ever going to be a basic box with admin rights (more or less).

Making the seamless transition to automation makes sense especially if there are a lot of networked computers, but...they have to share a common connection for automation, Windows 8 Pro or Enterprise, and I learned later that through Windows there is an option for access granting without the need to be connected to a domain per say.

Microsoft is in the business of software as a service at this point, so having a understanding of Exchange aspect helps, I'm also learning this too, which at on first experience was completely confusing.

So I decided to jump in on the server thing, and tried out a couple options. CentOS, Debian, and Windows Server 2012. Having something I can build my own cloud/storage/DLNA box makes more sense as the climate of pay as you go doesn't appeal to me.Yes there is the big cost, upgrades and whatnot but, I like the control I have with information I own.

I think more people should consider this as the option to not give various cloud streaming cartels any continued support. Only real concern I have is ISP monopoly. That will change (I hope) as I'm looking forward to fiber. I desperately want it but it is hard to get here in the area.

As I delve further into the server field I'll write my experiences here. Thanks for reading.

B.




No comments:

Post a Comment