Server Core is a minimalistic Microsoft Windows Server installation option, debuted in Windows Server 2008 . Server Core provides a server environment with functionality scaled back to core server features, and because of limited features, it has reduced servicing and management requirements, attack surface, disk and memory usage. Andrew Mason, a program manager on the Windows Server team, noted that a primary motivation for producing a Server Core variant of Windows Server 2008 was to reduce the attack surface of the operating system, and that about 70% of the security vulnerabilities in Microsoft Windows from the prior five years would not have affected Server Core. Most notably, no Windows Explorer shell is installed. All configuration and maintenance is done entirely through command-line interface windows, or by connecting to the machine remotely using Microsoft Management Console (MMC), remote server administration tools, and PowerShell .
40-400: As Server Core implementations matured, it has evolved from an installation option to a configuration level. Server Core is less looked down as a stripped version, instead the full GUI version is being thought of having a rarely needed client layer on top of the server layer In newer Windows versions there is more granularity in configuration levels: [REDACTED] Windows Server 2008 was
80-514: A Usenet newsgroup as a pun on the name Titanic , the "unsinkable" ocean liner that sank on its maiden voyage in 1912. The very next day on 5th October 1999, AMD announced their plans to extend Intel's x86 instruction set to include a fully downward compatible 64-bit mode, additionally revealing AMD's newly coming x86 64-bit architecture, which the company had already worked on, to be incorporated into AMD's upcoming eighth-generation microprocessor, code-named SledgeHammer . AMD also signaled
120-448: A cluster with high availability using failover clustering or network load balancing . As Server Core is not a different version of Windows Server 2008, but simply an installation option, it has the same file versions and default configurations as the full server version. In Windows Server 2008 and 2008 R2, if a server was installed as Server Core, it cannot be changed to the full GUI version and vice versa. To make administration of
160-418: A Server Core machine easier, a Windows script called "scregedit.wsf" was included to make basic changes like turning Automatic Updates on or off, turning Remote Desktop on or off and change page file settings. In Windows Server 2008 R2 , Server Core includes a subset of the .NET Framework, so that some applications (including ASP.NET web sites and Windows PowerShell 2.0) can be used. Having .NET support, it
200-487: A common operating system kernel (OS). In recent times, containerization technology has been widely adopted by cloud computing platforms like Amazon Web Services , Microsoft Azure , Google Cloud Platform , and IBM Cloud . Containerization has also been pursued by the U.S. Department of Defense as a way of more rapidly developing and fielding software updates, with first application in its F-22 air superiority fighter. Container orchestration or container management
240-457: A data dependency exists between data before and after the stop. All instructions between a pair of stops constitute an instruction group , regardless of their bundling, and must be free of many types of data dependencies; this knowledge allows the processor to execute instructions in parallel without having to perform its own complicated data analysis, since that analysis was already done when the instructions were written. Within each slot, all but
280-460: A few instructions are predicated, specifying a predicate register, the value of which (true or false) will determine whether the instruction is executed. Predicated instructions which should always execute are predicated on pr 0 , which always reads as true. The IA-64 assembly language and instruction format was deliberately designed to be written mainly by compilers, not by humans. Instructions must be grouped into bundles of three, ensuring that
320-740: A full disclosure of the architecture's specifications and further details to be available in August 2000. As AMD was never invited to be a contributing party for the IA-64 architecture and any kind of licensing seemed unlikely, AMD's AMD64 architecture-extension was positioned from the beginning as an evolutionary way to add 64-bit computing capabilities to the existing x86 architecture, while still supporting legacy 32-bit x86 code , as opposed to Intel's approach of creating an entirely new, completely x86-incompatible 64-bit architecture with IA-64. In January 2019, Intel announced that Kittson would be discontinued, with
360-641: A last order date of January 2020, and a last ship date of July 2021. In November 2023, IA-64 support was removed from the Linux kernel and is since then maintained out-of-tree . Intel has extensively documented the Itanium instruction set and the technical press has provided overviews. The architecture has been renamed several times during its history. HP originally called it PA-WideWord . Intel later called it IA-64 , then Itanium Processor Architecture (IPA), before settling on Intel Itanium Architecture , but it
400-412: A particular subset of the instruction set , and each unit executes at a rate of one instruction per cycle unless execution stalls waiting for data. While not all units in a group execute identical subsets of the instruction set, common instructions can be executed in multiple units. The execution unit groups include: Ideally, the compiler can often group instructions into sets of six that can execute at
440-435: Is operating-system–level virtualization or application-level virtualization over multiple network resources so that software applications can run in isolated user spaces called containers in any cloud or non-cloud environment, regardless of type or vendor . Note that the word "container" is an overloaded term. That is why Marc Brooker recommends that whenever you use the word "container", check whether your audience uses
SECTION 10
#1732855366888480-1077: Is Server Core) and Windows Server 2016 Desktop Experience. Switching between these versions, as is available in Server 2012, is not supported (the possibility was removed in Technical Preview 3). Subset of Control Panel regedit.exe - Registry Editor notepad.exe - Notepad cmd.exe - Command prompt msinfo32.exe - System Information msiexec.exe - Windows Installer taskmgr.exe - Task Manager powershell.exe - Windows PowerShell iscsicpl.exe - ISCSI Initiator Properties subset of Explorer function - all what can be done from File - Open dialog like adexplorer.exe - Sysinternals Active Directory Explorer procexp.exe - Sysinternals Process Explorer procmon.exe - Sysinternals Process Monitor tcpview.exe - Sysinternals TCPview vmmap.exe - Sysinternals VMMap rammap.exe - Sysinternals RamMap 1.50 portqueryui.exe - Microsoft PortQueryUI Version 1.0 IA-64 IA-64 ( Intel Itanium architecture )
520-542: Is also the first Server Core version where Microsoft SQL Server can be installed (a supported scenario only with SQL Server 2012+). Server Manager has become remoteable. New roles had been enabled to run on Server Core, including Active Directory Certificate Services and the File Server Resource Manager component of the File Services role. WoW64 is available by default, but can be disabled. In addition to
560-552: Is available in a Server Core installation, and is installed and enabled by default. Windows Server 2016 has a minimal footprint installation option (smaller than Server Core) called Nano Server, optimized for Windows Server Containers and Hyper-V Containers, as well as other cloud-optimized scenarios. Microsoft removed the GUI stack, WoW64 and Windows Installer . There is no local logon or Remote Desktop support. On installation, Server 2016 offers two options: Windows Server 2016 (which
600-436: Is mostly used in the context of application containers. Implementations providing such orchestration include Kubernetes and Docker swarm . Container clusters need to be managed. This includes functionality to create a cluster, to upgrade the software or repair it, balance the load between existing instances, scale by starting or stopping instances to adapt to the number of users, to log activities and monitor produced logs or
640-707: Is now the default configuration level. There is also a new installation option, "minimal server interface" that allows some GUI elements such as MMC and Server Manager to run, but without the normal desktop, shell or default programs like File Explorer . The "minimal server interface" is in fact a server role (Server-Gui-Mgmt-Infra) , the full GUI version contains the Server-Gui-Shell role as well. Some new roles are available, like Windows Server Update Services (WSUS), Active Directory Rights Management Server , and Routing and Remote Access Server , and many new features as well. In Windows Server 2012 R2 , Windows Defender
680-510: Is now usually referred to as the Itanium bus. The speed of the bus has increased steadily with new processor releases. The bus transfers 2×128 bits per clock cycle, so the 200 MHz McKinley bus transferred 6.4 GB/s, and the 533 MHz Montecito bus transfers 17.056 GB/s Itanium processors released prior to 2006 had hardware support for the IA-32 architecture to permit support for legacy server applications, but performance for IA-32 code
720-485: Is still widely referred to as IA-64 . It is a 64-bit register-rich explicitly parallel architecture. The base data word is 64 bits, byte-addressable. The logical address space is 2 bytes. The architecture implements predication , speculation , and branch prediction . It uses variable-sized register windowing for parameter passing. The same mechanism is also used to permit parallel execution of loops. Speculation, prediction, predication, and renaming are under control of
760-414: Is the instruction set architecture (ISA) of the discontinued Itanium family of 64-bit Intel microprocessors . The basic ISA specification originated at Hewlett-Packard (HP), and was subsequently implemented by Intel in collaboration with HP. The first Itanium processor, codenamed Merced , was released in 2001. The Itanium architecture is based on explicit instruction-level parallelism , in which
800-447: The DISM command, a new command line Server Configuration tool (Sconfig.cmd) has arrived to configure and manage several common aspects of Server Core installations. Server Manager can be used to remotely administer a Server Core machine. Unlike its predecessors, Windows Server 2012 can switch between "Server Core" and server with a DE installation option without reinstallation. Server Core
840-476: The compiler decides which instructions to execute in parallel. This contrasts with superscalar architectures, which depend on the processor to manage instruction dependencies at runtime. In all Itanium models, up to and including Tukwila , cores execute up to six instructions per cycle . In 2008, Itanium was the fourth-most deployed microprocessor architecture for enterprise-class systems , behind x86-64 , Power ISA , and SPARC . In 2019, Intel announced
SECTION 20
#1732855366888880-402: The architecture, including Microsoft Windows , Unix and Unix-like systems such as Linux , HP-UX , FreeBSD , Solaris , Tru64 UNIX , and Monterey/64 (the last three were canceled before reaching the market). In 1999, Intel led the formation of an open-source industry consortium to port Linux to IA-64 they named "Trillium" (and later renamed "Trillian" due to a trademark issue), which
920-495: The compiler were much more difficult to implement than originally thought, and the delivery of Itanium began slipping. Since Itanium was the first ever EPIC processor, the development effort encountered more unanticipated problems than the team was accustomed to. In addition, the EPIC concept depended on compiler capabilities that had never been implemented before, so more research was needed. Several groups developed operating systems for
960-670: The compiler: each instruction word includes extra bits for this. This approach is the distinguishing characteristic of the architecture. The architecture implements a large number of registers: Each 128-bit instruction word is called a bundle , and contains three slots each holding a 41-bit instruction , plus a 5-bit template indicating which type of instruction is in each slot. Those types are M-unit (memory instructions), I-unit (integer ALU, non-ALU integer, or long immediate extended instructions), F-unit (floating-point instructions), or B-unit (branch or long branch extended instructions). The template also encodes stops which indicate that
1000-452: The density of code. Additional instructions for speculative loads and hints for branches and cache are impractical to generate optimally, because a compiler cannot predict the contents of the different cache levels on a system running multiple processes and taking interrupts. From 2002 to 2006, Itanium 2 processors shared a common cache hierarchy. They had 16 KB of Level 1 instruction cache and 16 KB of Level 1 data cache. The L2 cache
1040-539: The discontinuation of the last of the CPUs supporting the IA-64 architecture. In 1989, HP began to become concerned that reduced instruction set computing (RISC) architectures were approaching a processing limit at one instruction per cycle . Both Intel and HP researchers had been exploring computer architecture options for future designs and separately began investigating a new concept known as very long instruction word (VLIW) which came out of research by Yale University in
1080-406: The early 1980s. VLIW is a computer architecture concept (like RISC and CISC ) where a single instruction word contains multiple instructions encoded in one very long instruction word to facilitate the processor executing multiple instructions in each clock cycle. Typical VLIW implementations rely heavily on sophisticated compilers to determine at compile time which instructions can be executed at
1120-449: The fastest Itanium 2, at 1.67 GHz, was rated at 6.67 GFLOPS. In practice, the processor may often be underutilized, with not all slots filled with useful instructions due to e.g. data dependencies or limitations in the available bundle templates. The densest possible code requires 42.6 bits per instruction, compared to 32 bits per instruction on traditional RISC processors of the time, and no-ops due to wasted slots further decrease
1160-841: The first Windows Server with the Server Core option (in all editions, except IA-64 ). Though no Windows Explorer shell is installed, Notepad and some control panel applets, such as Regional Settings, are available. Server Core on Windows Server 2008 does not include the Internet Explorer or many other features not related to core server features. A Server Core machine can be configured for several basic roles: Active Directory Domain Services , Active Directory Application Mode (ADAM), DNS Server , DHCP server , file server , print server , Windows Media Server , IIS 7 web server and Hyper-V virtual server. Server Core can also be used to create
1200-535: The lead on the design and commercialization process, while HP contributed to the ISA definition, the Merced/Itanium microarchitecture, and Itanium 2. The original goal year for delivering the first Itanium family product, Merced, was 1998. Intel's product marketing and industry engagement efforts were substantial and achieved design wins with the majority of enterprise server OEMs, including those based on RISC processors at
1240-442: The same definition. Each container is basically a fully functional and portable cloud or non-cloud computing environment surrounding the application and keeping it independent of other environments running in parallel. Individually, each container simulates a different software application and runs isolated processes by bundling related configuration files, libraries and dependencies. But, collectively, multiple containers share
Server Core - Misplaced Pages Continue
1280-470: The same time and the proper scheduling of these instructions for execution and also to help predict the direction of branch operations. The value of this approach is to do more useful work in fewer clock cycles and to simplify processor instruction scheduling and branch prediction hardware requirements, with a penalty in increased processor complexity, cost, and energy consumption in exchange for faster execution. During this time, HP had begun to believe that it
1320-428: The same time. Since the floating-point units implement a multiply–accumulate operation , a single floating-point instruction can perform the work of two instructions when the application requires a multiply followed by an add: this is very common in scientific processing. When it occurs, the processor can execute four FLOPs per cycle. For example, the 800 MHz Itanium had a theoretical rating of 3.2 GFLOPS and
1360-558: The three instructions match an allowed template. Instructions must issue stops between certain types of data dependencies, and stops can also only be used in limited places according to the allowed templates. The fetch mechanism can read up to two bundles per clock from the L1 cache into the pipeline. When the compiler can take maximum advantage of this, the processor can execute six instructions per clock cycle. The processor has thirty functional execution units in eleven groups. Each unit can execute
1400-472: The time. Industry analysts predicted that IA-64 would dominate in servers, workstations, and high-end desktops, and eventually supplant both RISC and CISC architectures for all general-purpose applications. Compaq and Silicon Graphics decided to abandon further development of the Alpha and MIPS architectures respectively in favor of migrating to IA-64. By 1997, it was apparent that the IA-64 architecture and
1440-424: Was led by Intel and included Caldera Systems , CERN , Cygnus Solutions , Hewlett-Packard, IBM, Red Hat , SGI , SuSE , TurboLinux and VA Linux Systems . As a result, a working IA-64 Linux was delivered ahead of schedule and was the first OS to run on the new Itanium processors. Intel announced the official name of the processor, Itanium , on October 4, 1999. Within hours, the name Itanic had been coined on
1480-575: Was much worse than for native code and also worse than the performance of contemporaneous x86 processors. In 2005, Intel developed the IA-32 Execution Layer (IA-32 EL), a software emulator that provides better performance. With Montecito, Intel therefore eliminated hardware support for IA-32 code. In 2006, with the release of Montecito , Intel made a number of enhancements to the basic processor architecture including: Container (virtualization) In software engineering , containerization
1520-543: Was no longer cost-effective for individual enterprise systems companies such as itself to develop proprietary microprocessors. Intel had also been researching several architectural options for going beyond the x86 ISA to address high-end enterprise server and high-performance computing (HPC) requirements. Intel and HP partnered in 1994 to develop the IA-64 ISA, using a variation of VLIW design concepts which Intel named explicitly parallel instruction computing (EPIC). Intel's goal
1560-442: Was to leverage the expertise HP had developed in their early VLIW work along with their own to develop a volume product line targeted at the aforementioned high-end systems that could be sold to all original equipment manufacturers (OEMs), while HP wished to be able to purchase off-the-shelf processors built using Intel's volume manufacturing and contemporary process technology that were better than their PA-RISC processors. Intel took
1600-468: Was unified (both instruction and data) and is 256 KB. The Level 3 cache was also unified and varied in size from 1.5 MB to 24 MB. The 256 KB L2 cache contains sufficient logic to handle semaphore operations without disturbing the main arithmetic logic unit (ALU). Main memory is accessed through a bus to an off-chip chipset . The Itanium 2 bus was initially called the McKinley bus, but
#887112