Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Uncategorized»Windows Server 2008 Core

    Windows Server 2008 Core

    0
    By Ronni Pedersen on June 11, 2007 Uncategorized

    Windows Server 2008, when it ships later this year, will include an installation option called “Server Core” that allows admins to set up a minimal environment to run a handful of roles. At TechEd 2007 in Orlando, Microsoft announced that it will be adding yet another admin-selectable role option to Server Core: Internet Information Services 7.0 (IIS7), Microsoft’s Web server.

    Windows Server 2008 (the product which was known, until quite recently as Longhorn Server) has been designed since its inception to consist of a core foundation with roles layered atop it. Instead of uninstalling functionality, customers will add on specific roles and features that they want/need to run.

    You can enable 8 different types of role in Core:

    • Active Directory Domain Services
    • Active Directory Lightweight Directory Services (AD LDS)
    • Dynamic Host Configuration Protocol (DHCP) Server
    • DNS Server
    • File Services
    • Print Server
    • Streaming Media Services
    • IIS 7 (just added)
    • Codename Viridian (Hypervisor virtualisation) – Confirmed june 8th. ny Microsoft.

    There’s also some basic functionality that you can use:

    • Microsoft Failover Cluster
    • Network Load Balancing
    • Subsystem for UNIX-based Applications
    • Windows Backup
    • Multipath I/O
    • Removable Storage Management
    • Windows Bitlocker Drive Encryption
    • Simple Network Management Protocol (SNMP)
    • Windows Internet Naming Service (WINS)
    • Telnet client
    • Quality of Service (QoS)

    For example, you could have a branch office that requires a lightweight DC but does not have appropriate physical security.  They’ll probably also want DHCP and DNS.  The answer?  Install a Core OS, enable the AD Services, DHCP and DNS roles, promote it to be a read-only domain controller and use BitLocker to encrypt the hard drive.  You’ve now provided the necessary network services for the branch office and protected the infrastructure against potential theft of a DC (something that is very, very bad).

    I can also see how Core would be great for organisations with a huge web presence, e.g. hosting companies.  You can deploy many lightweight virtual Core servers with IIS enabled.  Their OS caused disk and RAM footprint will be small which is perfect for virtualisation.  Now you can sell many exclusive use servers to your clients with little impact on your infrastructure and at a much reduced cost.

    Microsoft lists the following benefits:

    • Reduced maintenance. Because a Server Core installation installs only what is required to have a manageable DHCP, File, Print, DNS, Media Services, AD LDS, or Active Directory server, less maintenance is required.
    • Reduced attack surface. Because Server Core installations are minimal, fewer services and applications run on the server, thereby decreasing the attack surface.
    • Reduced management. Because fewer applications and services are installed on a server running the Server Core installation, there is less to manage.
    • Less disk space required. A Server Core installation only requires about 1 gigabyte (GB) of disk space to install and approximately 2 GB for operations after the installation.

    Check it out if this sounds of interest to you.  Beta 3 of Windows Server 2008 was released to the public (for testing and evaluation only) about a month ago.

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Successful Adoption of a “Cloud First” Strategy

    Workplace Ninja User Group Denmark Meetup – May 2022

    IT Camp: Windows 8.1 in the Enterprise

    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • Setting OSDComputerName using CustomSettings.ini
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • SCCM: Failed to Get Client Identity (80004005)
    • Updating the Windows Update Agent on Windows 7 clients
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.