Installing & Configuring Windows Server 2012 R2: Tulus Pardamean Simanjuntak
Installing & Configuring Windows Server 2012 R2: Tulus Pardamean Simanjuntak
Maximum RAM for Standard Edition is 32GB and 4TB for Datacenter Edition.
Server Core eliminates some of the most memory-intensive and processor-intensive elements of the
Windows Server 2012 R2 operating system, thus devoting more of the system hardware to running
essential services.
Server Core requires less disk space for the installed operating system elements and less swap space,
which maximizes the utilization of the servers storage resources.
The graphical elements of Windows Server 2012 R2 are among the most frequently updated, so
running Server Core reduces the number of updates that administrators must apply. Fewer updates
also mean fewer server restarts and less downtime.
The less software there is running on the computer, the fewer entrance points for attackers to exploit.
Server Core reduces the potential openings presented by the operating system, increasing its overall
security.
1. Click Manage > Remove Roles and Features. The Remove Roles and Features Wizard appears,
showing the Before You Begin page.
2. Click Next. The Server Selection page appears.
3. In the Server Pool list, select the server you want to modify and click Next. The Remove Server
Roles page appears.
4. Click Next. The Remove Features page appears.
5. Scroll down the Features list and expand the User Interfaces and Infrastructure feature.
6. Clear the Server Graphical Shell check box and click Next. The Confirm Removal Selections
page appears.
7. Click Remove. The Removal Progress page appears.
8. When the removal is complete, click Close.
9. Restart the server.
The only drawback of this arrangement is that the WinSxS directory permanently occupies
approximately 5 GB of disk space, much of which is, in many cases, devoted to data that will never be
used after the initial server deployment.
Feature Disabled with payload removed only provided by Features on Demand because in versions of
the operating system prior to Windows Server 2012, features could only be Enabled or Disabled.
The new Server Manager, for example, is designed to enable administrators to manage Windows
servers without having to interact directly with the server console, either physically or remotely.
However, there are some tasks that administrators might have to perform immediately after the
operating system installation that require direct access to the server console:
Configuring the network connection
Setting the time zone
Enabling Remote Desktop
Renaming the computer
Joining a domain
In Switch Dependent Mode, you can choose static teaming, a generic mode that balances the traffic
between the adapters in the team, or you can opt to use the Link Aggregation Control Protocol defined
in IEEE 802.3ax, assuming that your equipment supports it.
The Server Manager interface consists of a navigation pane on the left containing icons representing
various views of server resources. Selecting an icon displays a home page in the right pane, which
consists of a number of tiles containing information about the resource.
Although only the local server appears in Server Manager when you first run it, you can add other
servers, enabling you to manage them together. The servers you add can be physical or virtual and
can be running any version of Windows Server since Windows Server 2003. After you add servers to
the interface, you can create groups containing collections of servers, such as the servers at a
particular office location or those performing a particular function. These groups appear in the
navigation pane, enabling you to administer them as a single entity.