4.1: Traditional IT Administration Overview

Introduction to Cloud Computing · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    4.1: Traditional IT Administration Overview

    Traditional IT administration refers to managing computing infrastructure that is hosted on-premises (within an organization’s own facilities or data centers). In this model, the organization’s IT staff has full control and full responsibility over the hardware and software stack – from procurement and installation of servers to ongoing maintenance, updates, and security [15]. Key characteristics of traditional administration include:

    On Premises Environment. Details in caption.

    Figure \(\PageIndex{1}\): A layered diagram showing the full scope of responsibility in an on-premises environment, from physical hardware at the bottom through networking, operating systems, applications, and data at the top, with the organization responsible for every layer. (CC BY 4.0; Felix Amoruwa) Access to a detailed description of Figure \(\PageIndex{1}\)
    • Tools & Interfaces: Administrators typically interact directly with servers and network equipment. Common tools are operating system consoles (e.g., Windows Server GUI, Linux shell), remote desktop (RDP) for Windows servers, and Secure Shell (SSH) for Linux/UNIX systems. Virtualization platforms like VMware vSphere or Hyper-V might provide a management console for VMs, but these run on local hardware. Many processes are manual or use scripts developed in-house (e.g., PowerShell scripts for automating Windows tasks). There is often no single unified interface for all systems; admins might juggle multiple tools for different purposes.
    • Access Methods: Access to systems is usually through the corporate network. Admins might physically sit in a server room console or more commonly use remote network access. Credentials are often Active Directory domain usernames/passwords for Windows environments or local accounts for Linux, sometimes secured via VPN when off-site. Direct hardware access (e.g., console cables, KVM switches) may be needed for certain maintenance. In on-prem environments, authentication might be integrated with corporate identity systems (like AD), and multifactor authentication is used primarily for remote/VPN access rather than local console logins.
    • User Roles: Traditional IT departments often have specialized roles such as system administrators (managing servers and OS), network administrators (managing switches, routers, firewalls), database administrators, and storage administrators. Each role focuses on a segment of the infrastructure. Privileges are typically controlled via internal processes and tools – for example, Windows sysadmins might be Domain Administrators in AD, and network admins have privileged accounts on network devices. There is usually a clear separation of duties (e.g., a database admin might not have full rights on network firewalls, etc.).
    • Skills Required: Traditional admins develop deep expertise in hardware and OS management. Important skills include installing/configuring servers, managing operating systems (Windows or Linux), networking (TCP/IP, DNS, DHCP), virtualization, and scripting for automation. They need to handle disaster recovery (backups, redundancy), and often perform repetitive maintenance tasks like patching OS and firmware, replacing failing hardware, and monitoring system performance. The focus is on ensuring on-prem systems run reliably, which demands troubleshooting skills and sometimes 24/7 availability for critical outages.
    • Security Mechanisms: Security in a traditional model is often centered on perimeter defense and internal trust. Organizations use firewalls, VPNs, and physical security controls to ensure only authorized personnel can access the environment. Data is stored locally, giving a sense of control over sensitive information. User access within the network is typically managed through directory services (e.g., Active Directory) with group policies to enforce security settings. Patching and updating software is the organization’s responsibility – failing to do so can leave vulnerabilities. Ensuring security involves significant investment in both time and money (for example, setting up intrusion detection systems, maintaining backup systems, etc.). On-premises admins also manage credentials like passwords or key files for various systems, and often rely on role-based access via AD groups or similar to limit privileges.

    In summary, the traditional model gives IT teams complete control over their infrastructure, but also burdens them with all aspects of management – from hardware provisioning to software updates and physical security. This can offer advantages in data privacy and customized setups, but at the cost of scalability and agility. Next, we contrast this with cloud administration.


    This page titled 4.1: Traditional IT Administration Overview was last modified on Tue, 22 Sep 2026 21:13:27 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Felix Amoruwa.