Install Windows Updates on Windows Server 2008 R2 Core

[fumble]

Windows 2008 Servers, which require no graphical user interface can be installed as the core. Only a minimal system is installed, which out-of-the-box is administered through a command line interface. Since only the required features are included, the footprint is smaller than a full installation of Windows Server. Fewer Bits & Bytes also means a smaller attack surface and thus less patches.

As a Server Core installation not the familiar Windows user interface is used, "are given) for the completion of the server configuration does not standard procedure (" Out-of-Box Experience. Instead, the initial configuration manually run with Command prompt tools, so the popularity of the server core keeps administrators in the unfortunately still quite limited. In order to show easier ways like a server faster and easier it will be put into operation, following a brief overview of the Server Core Management Tools.

Model-based virtualization host Virtual Server, which required running virtualization on top of your computer operating system, Hyper-V is a virtual environment that works directly on the hardware level, without exchanges with the operating system. Hyper-V architecture consists of a microkernel hypervisor, as well as parent and child partitions.

All versions of Hyper-V has one parent partition. This section controls the functions of the Hyper-V. From the parent partition running the console Windows Server Virtualization. In addition, the parent section is used to run virtual machines (VM), supporting streaming emulation of old hardware. Such VM, built on the ready-made templates that emulate the hardware, are analogues of VM, working with virtualization products on the basis of the host, such as Virtual Server.

Hyper-V offers more features than Virtual Server 2005 R2. Since Hyper-V only works on 64-bit platforms, the host system allocates up to 1 TB of RAM. Hyper-V does not limit the number of active VM: the maximum number determined by the capacities of the hardware host. In addition, VM Hyper-V are more scalable than VM Virtual Server. Hyper-V supports both 32-bit and 64-bit guest operating systems. Guest systems may use high-performance architecture VMBus, as well as get more RAM and CPU resources than offer Virtual Server. Technology, Virtual Server 2005 R2 does not support symmetric multiprocessing and has a limitation in the allocation of memory (up to 3.6 GB per VM). Hyper-V allocates for each VM to four virtual processors and up to 32 GB of RAM. To harness these opportunities fully, the host system must have at least four processing cores and more than 32 GB of physical RAM.

Hyper-V provides a new data storage technology. Support for Storage Area Network (SAN) allows you to download the VM and implement clustering interception refusal guest systems, and virtual servers. Package Hyper-V also provides data storage with access via the VM. With the help of technology Hyper-V can apply to the images of virtual hard disks without mounting the VHD image to the active VM. Hyper-V also allows you to use the service Volume Shadow Copy Service (VSS) for backing up VM. At the network level technology Hyper-V allows you to install a new virtual switch with support for the mechanism of Windows Network Load Balancing (NLB) to connect the VM and the various servers. In addition, Hyper-V allows you to make snapshots of active VM and provides an opportunity to make a return of virtual systems on any of the stored snapshots.

Hyper V on Windows Server 2008

Hyper-V is not installed by default with the system of Server 2008. To install the component Hyper-V using Server Manager from the Windows Server 2008. In the Start menu, select Programs, Administrative Tools, then click Server Manager. In the Server Manager add the role of virtualization. To do this, click Add Roles Wizard, and then Add Roles Wizard.

In the wizard Add Roles Wizard to mention the role of Windows Server Virtualization. Next, click Next and see the wizard screens, allowing to explore and configure Hyper-V. The first thing the wizard will explain that, you may need to configure support for virtualization in the BIOS. The program will link to the files Relief Services Windows Server Virtualization Online Help. Next you'll be prompted to specify the network connection that you want to associate with the virtual networks. By default, the wizard creates a virtual network for each actually installed network adapter. Next will be asked to confirm the information, and reboot the system

Systems technology AMD-V virtualization by default. However, if the system uses virtualization technology Intel-VT, will have to see the BIOS settings at boot time and make sure that virtualization is enabled. When you work with motherboards from Intel to press the F2 key during startup to view your BIOS. You can set the parameter Enable VT, to allow the processor to support virtualization. After the reboot screen Resume Configuration Wizard. Use it to finish adding the role of Windows Server Virtualization. The new role will be added to the container-established roles in Server Manager.

[fumble]

Windows Management Tools

A Windows Server, installed as Server Core, can also be managed with these tools

• Command Prompt
• Remote Desktop Connection
• Windows Remote Shell

• Windows PowerShell (Windows Server 2008 R2)
• MMC Snap-In

• Server Manager (Windows Server 2008 R2)

This however can be accessed using one of these tools on the server, a network, domain, firewall, feature, etc. provided configuration. Already known as HVCONFIG Hyper-V Server, this tool is now in Windows Server 2008 R2 under the name "$ config" integrated.

• The following configurations can be made with the Microsoft tool:
• Domain join
• Rename Computer
• Configure Remote (enable management via Server Manager and PowerShell including properly configuring the firewall)
• Configuring Windows Update
• Enabling Remote Desktop
• Configuring Networking (vs. static. And DHCP for multiple NICs)

The tool is on the Command Prompt with " sconfig "is called. If this future is to be opened at each logon, this can be configured via registry entry:

Key: HKLM \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run 
Entry: $ config 
Type: REG_SZ 
Value: C: \ Windows \ system32 \ sconfig.cmd

If you would like to customize the header is simply the line "const L_Msg005_Text in existing VB Script adapt:" notepad.exe C:\Windows\system32\en-US\sconfig.vbs . If that color scheme blue / white is not acceptable, is of course free to select "color" in the CMD file to adapt: notepad.exe C:\Windows\system32\en-US\sconfig.cmd

Core Configurator

Also out of the house is the Microsoft Core Configurator. This is, however, Microsoft's Open Source Project Web site CodePlex and was developed by the consulting colleagues, Andrew and Tony. Core Configurator is specifically enhanced for Windows Server 2008 R2. Version 2.0 is completely based on Windows PowerShell, which, thanks to the base of WinForm, can now be displayed as GUI.

The following configurations can be made with the Core Configurator:

• Product Licensing
• Networking Features
• DCPromo Tool
• iSCSI Settings
• Server Roles and Features
• User and Group Permissions
• Share Creation and Deletion
• Dynamic firewall settings
• Display, Screen Saver Settings
• Add & Remove Drivers
• Proxy settings
• Windows Updates (Including WSUS)
• Multipath I / O
• Hyper-V virtual machine including thumbnails
• Join Domain and Computer rename
• Add / remove programs
• Services
• WinRM
• Complete logging of all commands executed

[fumble]

Smart-X Core Configurator

Since the launch of Windows Server 2008 RTM is therefore caused some management tools. The best known tool is certainly the Core Configurator smart-X - only because of the moving story about the development. This little tool gives the server administrator core so to speak, the GUI and therefore allows quick and easy configuration. It was set mainly on familiar icons and names, so you should quickly find without big words correctly.

The following configurations can be made with the Smart-X Tool:

• Regional and Language options
• Services Panel
• Network Connections
• Automatic Update
• Product Activation
• Configuration of display resolution
• Clock and time zone configuration
• Remote Desktop configuration
• Management of local user accounts (creation, deletion, group membership, passwords)
• Firewall configuration
• WinRM configuration
• IP configuration
• Computer name and domain / workgroup membership
• Installation of Server Core features / roles

How Core Configurator can be used also in the related Manual ( PDF / HTML ) is described in detail. In my own tests with Windows Server 2008 RTM and Windows Server 2008 R2, the tool worked perfectly. The only downside, the binaries must be installed on any server first. Plus point for virtualized environments, the source is, along with the *. exe (zipped), also available as an ISO image.

Hyper-V on Windows Server 2008 Core

What has just been introduced as a beta on the side-host for Windows Server 2008 R2: Novell has contributed directly to work on the interoperability of the OS in the laboratory when he started close partnership with Microsoft and ensure that the performance boost This version (which introduces support for SMP) is appreciable. Always assuming that it is a good idea. Personally I feel more useful and secure the opposite, namely to create a Windows virtual machine as a guest of a Linux distribution: the beta version of Hyper-V for Windows Server can be downloaded using a valid Windows Live ID, you can virtualize up to 4 CPUs , synchronize time and manage the Linux system shutdown Windows.

Hyper-V is provided free to all owners of the latest version of Windows Server. Obviously you must have purchased the operating system. Hyper-V is characterized by the ability to assign fixed resources to each virtual machine (CPU, ram) and the priorities of running a virtual machine than the other. Features very comfortable especially when they are most active environments.

The management of a server virtualization can be accomplished easily using the tool Hyper-V manager from Administrative tools in the Start menu.

Hyper-V Manager

• In the right section of Hyper-V Manager, the first code creates a new virtual machine.
• In the second screen appears that there is an opportunity to provide a custom name to the virtual machine and choose the path where you store it
• In the next part you must indicate the amount of RAM reserved for the new VM.
• But in the diagram below you can choose which network interface is connected to the machine, does not offer any connectivity.
• Then you can attach a virtual hard disk or a file in which to store all data in the operating system that will put the virtual machine.
• There is the possibility of creating a file from scratch, use existing disk or not to allocate any space (useful if you have to try some software or live distribution). And 'better abound with the size (size) of the disc, since then more space may be problematic especially since the space is really used only to actual need.
• In section luck, you can indicate which media available to the VM to install an operating system. Microsoft has finally made it possible to use an ISO image as a means of installation, in addition to the CD and use the network.
• After this procedure you will get a summary of your choices, with the ability to backtrack.

Configuring a virtual machine

• Before starting the virtual machine you just created with Hyper-V, you can still see and adjust a few settings to get the maximum insured benefits from Hyper-V.
• Always in the right section of the manager of virtualization software is the "Settings". Clicking on it opens a configuration window that allows you to change many things.
• You can add special devices such as SCSI controllers, network cards grafted on the computer after creating the virtual machine.
• Under 'BIOS' you can specify the order of boot devices, if you want to install an operating system using the network is good that the option is higher than FDI, as for the floppy.
• In Memory you can change the amount of RAM the virtual machine attributes.
• Extremely interesting is the Processor, here you can assign multiple CPUs to the virtual machine based on the number of those available on your computer. More may be assigned an execution priority to the virtual environment or limited (and protect) the resources.
• With Hyper-V is not only possible to use an image file as a virtual disk, but also use a hard case. The disk you want to use must be empty and not in use, can be selected from the pull down menu Controller and Location. Similarly with the CD or DVD player.
• Even the network interface can be configured in advanced mode. He can put a fixed or dynamic MAC address.
• Hyper-V can also use both serial ports on the computer whether they are elsewhere.
• You can select a floppy disk for the virtual machine or if you have a floppy drive you can use that.
• In section integrated services can enable functions to allow clock synchronization or some comfort, it is said that all operating systems that are installed are compatible.
• It 'can indicate whether the virtual machine should boot with the operating system on the server or if the startup has to be done manually. Interesting option that allows a late departure is the fastest operating system on the host virtual machines, because they are avoided peak demand (and limited govern well in a particular way of I / O).

[fumble]

Methods for Installation Updates on the Server Core

First Method

• There is a way to manually update the same. For that you will need to pass the following command in the command prompt.
• Click on Start > Run > Cmd and then type - cscript scregedit.wsf /AU /v
• If by chance the automatic updates are disabled then you can in the same way enable it.
• Click on Start > Run > Cmd and then type - cscript scregedit.wsf /AU 4

Second Method

• There is a readymade script provided for the same. I had provided you link for the same. Go on the site and run the script. For this you will need to create a file WUA_SearchDownloadInstall.vbs by copying the script. And then move this in the System32 folder of your main Windows directory.

VBS Script

Third Method

• The third way is by using SCONFIG. It is a nice tool for doing the same process. This tool can control the settings of Windows Update.
• Windows Service Pack installation on Server Core
• Service Pack 2 for Windows Vista and Server 2008 has reached the Release to Manufacturing (RTM). Pleasant is the version for which may be used for operating system, all the architectures and multiple languages:
• An upgrade to Service Pack 2, by means of software distribution (SCCM), patch management (WSUS), or manually is done as a stand-alone.

Installation
With a Core server, the server without GUI, the manual installation is done on the command line level. To install the service pack, the following steps must be made.

• ISO mount, insert DVD, or copy binaries to the server
• The same EXE (IA64, X64, X86) with the / unattend call, for example: Windows6.0-KB948465-X64.exe /unattend
• After a reboot, the installation is complete. It is displayed the message "Windows Server Service Pack 2 is now installed.
• The setup takes a few minutes. The task force should be made in a maintenance window. Importantly, pre-RTM build cannot be updated. These releases must be removed before the upgrade.
• In order to install through Windows Update could be prevented, there is the Windows Service Pack Blocker Tool Kit. Important to install the Service Pack is only after accepting the EULA anyway.

Windows Updates Service

With the Windows Server Update Services (WSUS) is a patch and update software from Microsoft, comprising a server and a client component. WSUS supports the administrators, Microsoft updates in large local networks to be delivered. He invites update packages from the Internet (Microsoft Update) and offers it to the Windows clients to install. The WSUS server at the administrator can specify which computers to install the updates. Microsoft provides the Windows Server Update Services free of charge.

The WSUS server software on Windows Server 2003 SP1 or Windows Server 2008 installed. After the client has been configured via Group Policy or registry, administrators can deploy the distribution of all published by Microsoft Update Software Updates on computers in the corporate network under control centrally through the Microsoft Management Console (MMC). In addition, the WSUS server can serve as an update source for secondary WSUS server. Installation on Windows 2000 Server is not possible.

The task of the Windows Update Client

• The WSUS client regularly invites an XML file containing the list of the Administrator for his group to detect or install approved updates, check this and report back the result to the server.
• The WSUS client to users before downloading any outstanding patches indicate the. The administrator can a group policy but also to automatically download without asking prescribe over.
• The WSUS client installed the updates without the prior question or query, depending on the setting of Group Policy
• The WSUS client starts the PC restarts after. This function may also be in the logout / shutdown procedure.

Benefits through WSUS

In the corporate network, it is necessary that a separate service request, the client requests. This brings tangible benefits for which you server and some time no more need to invest a down. The WSUS server itself is free.
Single central download : The server invites updates down once. Your end users do not have any updates to download and install.

Central release of patches : They give as an administrator to detect and install patches for free in their network. This release can be certain updates and computer groups can also be done automatically.

Reporting : generated on demand a report on the computer and for missing or installed updates and which systems has long been linked not have WSUS.

Setting a Deadline : If a patch device only after confirmation by the user is installed on one, you can set a deadline after which the update is installed each case on.