Fresh Installations on Windows Server 2003 Platforms on Page 1-2

Total Page:16

File Type:pdf, Size:1020Kb

Fresh Installations on Windows Server 2003 Platforms on Page 1-2 Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files, release notes, and the latest version of the applicable user documentation, which are available from the Trend Micro website at: http://docs.trendmicro.com/en-us/enterprise/officescan.aspx Trend Micro, the Trend Micro t-ball logo, and OfficeScan are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners. Copyright © 2015 Trend Micro Incorporated. All rights reserved. Release Date: November 2015 Protected by U.S. Patent No. 5,623,600; 5,889,943; 5,951,698; 6,119,165 Table of Contents Chapter 1: OfficeScan Server Installations Fresh Installations on Windows Server 2003 Platforms ..................................................................................................................................................................................... 1-2 Fresh Installations on Windows Server 2008 Platforms ..................................................................................................................................................................................... 1-4 Fresh Installations on Windows Server 2012 Platforms ..................................................................................................................................................................................... 1-6 Fresh Installations on Windows MultiPoint Server Platforms .......................................................................................................................................................................... 1-7 Chapter 2: OfficeScan Agent Installations Fresh Installations on Windows Endpoint Platforms ......................................................................................................................................................................................... 2-2 Fresh Installations on Windows Embedded System Platforms ........................................................................................................................................................................ 2-4 Fresh Installations on Windows Server Platforms .............................................................................................................................................................................................. 2-5 Update Agents ......................................................................................................................................................................................................................................................... 2-11 Chapter 3: Upgrades and Virtualization Support OfficeScan Server Upgrade Requirements ........................................................................................................................................................................................................... 3-2 OfficeScan Agent Upgrade Requirements ............................................................................................................................................................................................................ 3-2 OfficeScan Server Web Console Requirements ................................................................................................................................................................................................... 3-3 Virtualization Support .............................................................................................................................................................................................................................................. 3-4 Index Index ........................................................................................................................................................................................................................................................................ IN-1 i Chapter 1 OfficeScan Server Installations This section outlines the OfficeScan server system requirements on supported Windows Server platforms. • Fresh Installations on Windows Server 2003 Platforms on page 1-2 • Fresh Installations on Windows Server 2008 Platforms on page 1-4 • Fresh Installations on Windows Server 2012 Platforms on page 1-6 • Fresh Installations on Windows MultiPoint Server Platforms on page 1-7 1-1 OfficeScan 11.0 SP1 System Requirements Fresh Installations on Windows Server 2003 Platforms Note Trend Micro only guarantees continued support for Windows Server 2003 platforms until January 30th, 2017. Please prepare a migration plan in order to continue receiving the highest level of security on all endpoints. 1-2 OfficeScan Server Installations Web Server and Third Party Programs Servic Available Disk Operating System Edition Processor RAM Apache and Others e Pack Space IIS and Third- Third- Party Party Programs Programs Windows 32-bit / Standard SP2 At least 1.86 1GB minimum 6.5GB minimum if Microsoft IIS 6.0 Apache™ web Gigabit Network Server 2003 64-bit GHz Intel™ with at least installing the server 2.2.25 (with Interface Card FastCGI 1.5-RTW, Enterprise Core™2 Duo 500MB OfficeScan server, SSL enabled) (NIC) 32- bit or 64-bit exclusively for OfficeScan agent, depending on the Monitor that Datacenter OfficeScan and integrated system architecture Note supports 1024 x Smart Protection Windows Standard SP2 2GB 768 resolution at Server PHP 5.4.38 VC9, If an earlier Server 2003 recommended 256 colors or 32-bit, Non Thread version of the R2 Enterprise higher Safe with the CURL, Apache web server exists Datacenter GMP, LDAP, SQL Server MBSTRING, on the • 2008 R2 Windows N/A None OPENSSL, endpoint, Express SP2 Compute PDO_SQLITE, OfficeScan installs Cluster Server SOAP, • 2008 2003 COM_DOTNET Apache • 2008 R2 extensions 2.2.25 and enables SSL. • 2012 The existing Apache web • 2014 server is not Microsoft Visual C+ removed. + 2008 Redistributable PHP 5.4.38 VC9, Package (x86) 32-bit, Thread Safe with the CURL, Note GMP, LDAP, PDO_SQLITE, SQL Server COM_DOTNET 2008 R2 extensions Express SP2 is not supported by Windows Server 2003 SP1. 1-3 OfficeScan 11.0 SP1 System Requirements Fresh Installations on Windows Server 2008 Platforms Web Server and Third Party Programs Servic Available Disk Operating System Edition Processor RAM Apache and Others e Pack Space IIS and Third- Third- Party Party Programs Programs Windows 32-bit / Standard SP1 / At least 1.86 1GB minimum 6.5GB minimum if Microsoft IIS 7.0 or Apache™ web Gigabit Network Server 2008 64-bit SP2 GHz Intel™ with at least installing the later server 2.2.25 (with Interface Card (NIC) Enterprise Core™2 Duo 500MB OfficeScan server, SSL enabled) FastCGI 1.5-RTW, Monitor that exclusively for OfficeScan agent, 32- bit or 64-bit supports 1024 x Datacenter AMD™ 64 OfficeScan and integrated depending on the Note 768 resolution at processor Smart Protection Web 2GB system architecture 256 colors or higher Server If an earlier Intel 64 recommended version of the Windows 64-bit Standard With/ processor PHP 5.4.38 VC9, SQL Server 32-bit, Non Thread Apache web Server 2008 Without • 2008 R2 Safe with the server exists R2 Enterprise SP1 Express SP2 CURL, GMP, LDAP, on the endpoint, Datacenter MBSTRING, • 2008 OPENSSL, OfficeScan • 2008 R2 Web PDO_SQLITE, installs Apache SOAP, • 2012 COM_DOTNET 2.2.25 and • 2014 extensions enables SSL. The existing Microsoft Visual C+ Apache web + 2008 server is not Redistributable removed. Package (x86) PHP 5.4.38 VC9, Note 32-bit, Thread Safe with the CURL, SQL Server GMP, LDAP, 2008 R2 PDO_SQLITE, Express SP2 COM_DOTNET is not extensions supported by Windows Server 2008 SP1. 1-4 OfficeScan Server Installations Web Server and Third Party Programs Servic Available Disk Operating System Edition Processor RAM Apache and Others e Pack Space IIS and Third- Third- Party Party Programs Programs Windows HPC 32-bit / N/A None At least 1.86 1GB minimum 6.5GB minimum if Microsoft IIS 7.5 Apache™ web Gigabit Network Server 2008 64-bit GHz Intel™ with at least installing the server 2.2.25 (with Interface Card (NIC) Core™2 Duo 500MB OfficeScan server, FastCGI 1.5-RTW, SSL enabled) Windows HPC 64-bit N/A None exclusively for OfficeScan agent, 32- bit or 64-bit Monitor that Server 2008 AMD™ 64 OfficeScan and integrated depending on the supports 1024 x R2 processor Smart Protection system architecture Note 768 resolution at 2GB 256 colors or higher Server If an earlier Intel 64 recommended PHP 5.4.38 VC9, processor 32-bit, Non Thread version of the Microsoft Visual C+ Safe with the Apache web + 2008 CURL, GMP, LDAP, server exists Redistributable MBSTRING, on the Package (x86) OPENSSL, endpoint, PDO_SQLITE, OfficeScan SOAP, installs COM_DOTNET Apache extensions 2.2.25 and enables SSL. The existing Apache web server is not removed. PHP 5.4.38 VC9, 32-bit, Thread Safe with the CURL, GMP, LDAP, PDO_SQLITE, COM_DOTNET extensions 1-5 OfficeScan 11.0 SP1 System Requirements Fresh Installations on Windows Server 2012 Platforms Web Server and Third Party Programs Servic Available Disk Operating System Edition Processor RAM Apache and Others e Pack Space IIS and Third- Third- Party Party Programs Programs Windows 64-bit Standard None At least 1.86 2GB minimum 6.5GB minimum if Microsoft IIS 8.0 or Apache™ web Gigabit Network Server 2012 GHz Intel™ with at least installing the later server 2.2.25
Recommended publications
  • Illustrated Tutorial: Creating a Bootable USB Flash Drive for Windows XP
    Illustrated tutorial: Creating a bootable Version 1.0 February 15, 2007 USB flash drive for Windows XP By Greg Shultz The ability to boot Windows XP from a USB Flash Drive (UFD) offers endless possibilities. For example, you might make an easy-to-use troubleshooting tool for booting and analyzing seemingly dead PCs. Or you could transport your favorite applications back and forth from home to work without having to install them on both PCs. However, before you can create a bootable UFD, you must clear a few hurdles. You saw that one coming didn’t you? The first hurdle is having a PC in which the BIOS will allow you to configure the USB port to act as a bootable device. The second hurdle is having a UFD that that will work as a bootable device and that’s large enough and fast enough to boot an operating system such as Windows XP. The third hurdle is finding a way to condense and install Windows XP on a UFD. If you have a PC that was manufactured in the last several years, chances are that its BIOS will allow you to configure the USB port to act as a bootable device. If you have a good qual- ity UFD that’s at least 512 KB and that was manufactured in the last couple of years, you’ve probably cleared the second hurdle. And once you’ve cleared those first two hur- dles, the third one is a piece of cake. All you have to do is download and run some free soft- ware to create the bootable UFD.
    [Show full text]
  • Windows Server 2012 Refresh: How to Manage the Migration
    WINDOWS SERVER 2012 REFRESH: HOW TO MANAGE THE MIGRATION A guide to overcoming the challenges during the transition from Windows Server 2003 to Windows Server 2012 TABLE OF CONTENTS 5 Performing an application inventory 8 Upgrading Active Directory 9 Considering a hardware refresh 12 A move to virtualization 13 Certification, compliance and security 2 “Let’s face it. It’s the applications you’re running that are driving use of Windows Server 2003. Those are the things that are the beginning and end of what the Windows migration is all about.” AL GILLIN Program Vice President for Servers and System Software at IDC 3 INTRODUCTION With support ending for Windows Server 2003 in July 2015, companies need to ensure that their servers will adequately support the latest server OS and critical applications. By upgrading to Windows Server 2012, companies can increase their parallel computing capabilities and gain improved control over power consumption. Upgrading to the latest version of Windows Server brings the opportunity for businesses to lower their operating costs. “It’s an expensive proposition to continue supporting those old operating systems,” said Al Gillin, program vice president for servers and system software at IDC. Running one operating system rather than varieties of Server 2008, 2008 R2 and Server 2003R2 will make IT data centers more efficient. “If you have four different versions in place like that, that makes it more difficult for you to run your infrastructure,” Gillin said. When preparing for a Windows Server migration, companies should test all applications using a software tool such as Dell ChangeBASE before going live in the new OS.
    [Show full text]
  • Microsoft Service Pack & Security Bulletin Support
    Microsoft Service Pack & Security Bulletin Support ReadMe Revision History Date Revised Changes Made March 23, 2020 March 2020 Microsoft Security Update Contents What’s New? . 1 Microsoft Security Bulletins . 2 Current Microsoft Security Bulletin Status . 2 Enabling Windows Updates on Avid Systems . 6 Using a Microsoft WSUS Server for distributing Windows Updates. 7 Historical List of Microsoft Security Bulletin Exceptions . 7 What’s New? For March security bulletins, see “Current Microsoft Security Bulletin Status” on page 2. The section on “Notification Regarding the January 2020 Windows Updates” on page 3 has been updated to include information on MediaCentral Asset Management and MediaCentral Newsroom Management. See also http://avid.force.com/pkb/articles/en_US/Troubleshooting/en239659. Microsoft Security Bulletins Microsoft Security Bulletins Install Windows Security Patches and Service Packs. To download patches, run Windows Update. By default Avid supports all Windows Service Packs and security patches (sometimes referred to as “hot fixes”) which apply to the environments in which Avid products are deployed. We refer to them as Windows Updates in this document. Customers can schedule the download and installation of Windows Updates whenever they are available and make sense in their production environment. Avid tests the updates within several days of their availability. However, customers do not have to wait for the testing to be complete before installing the updates. Our current testing methodology is to utilize Windows Update on a representative sample of Avid products upon notification of new Security Bulletin availability by Microsoft. These systems are updated and observed while under test. Once the test period has completed (approx.
    [Show full text]
  • Windows XP History and Versions
    Lecture 23: Windows XP History and Versions n Mid-80ies Microsoft and IBM cooperated to develop OS/2 n Windows XP is produced by Microsoft Co. n 1988 - Microsoft started to develop its own new technology (NT) OS n XP is multi-user, multi-process, preemptive multitasking OS, 30M lines of source code capable of running OS/2, Windows and Unix apps. Hired Dave Cutler - architect of DEC VAX/VMS to head the design n It is developed to support multiple platforms and targeted towards enterprise workstations and server market as well as n NT v. 3.1 first released commercially July 1993 desktops n NT v 4.0 adopted Windows 95 user interface, graphics code moved into kernel to improve performance n In today’s lecture n 2000 – improved networking and laptop support, support for plug-and- u XP’s predecessors, the history of XP design, XP versions play devices, support for more processors (up to 8) and memory, u design principles becomes true multi-user through terminal server u components n XP (released Oct 2001) – update for 2000 replacement for 95/98 F hardware abstraction layer u simplifies user interface, improved reliability, performance F executive improvements, partial 64-bit support F environmental subsystems n versions F file system u desktop: XP personal – 95/98 replacement, professional – advanced features like POSIX support, some network features 1 u server: .NET – support for web/print service, clusters, large memory2 and multiple processors Design goals Components n XP is microkernel-based, modular n security – NT was C-2 certified (US
    [Show full text]
  • System Requirements
    Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice. Before installing and using the software, please review the readme files, release notes, and the latest version of the applicable user documentation, which are available from the Trend Micro website at: http://docs.trendmicro.com/en-us/enterprise/officescan.aspx Trend Micro, the Trend Micro t-ball logo, and OfficeScan are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners. Copyright © 2017 Trend Micro Incorporated. All rights reserved. Release Date: October 2017 Protected by U.S. Patent No. 5,623,600; 5,889,943; 5,951,698; 6,119,165 Table of Contents Chapter 1: OfficeScan Server Installations Fresh Installations on Windows Server 2008 R2 Platforms .............................................................................................................................................................................. 1-2 Fresh Installations on Windows Server 2012 Platforms ..................................................................................................................................................................................... 1-3 Fresh Installations on Windows Server 2016 Platforms ..................................................................................................................................................................................... 1-4 Fresh Installations
    [Show full text]
  • Windows Server, System Center, and Forefront Pricing and Licensing Guide
    1 Comprehensive Resource for Licensing and Pricing Windows Server, System Center, and Forefront Licensing Guide Table of Contents What’s New in This Guide 2 Windows Server 2008 R2 Offerings 2 Windows Server 2008 R2 Licensing 5 General Windows Server Licensing Construct 5 Windows Server 2008 R2 Foundation 6 Windows Server 2008 R2 Standard 6 Windows Server 2008 R2 Enterprise 7 Windows Server 2008 R2 Datacenter 9 Windows Server 2008 R2 for Itanium-Based Systems 9 Windows Web Server 2008 R2 10 Windows HPC Server 2008 R2 10 Windows Server 2008 Client Access Licensing: Decision Trees, Types, and Modes 12 Remote Desktop Services Licensing Requirements 14 External Connector License Requirements for Windows Server 2008 15 Virtual Desktop Infrastructure Suites Licensing 16 System Center Offerings 18 System Center Licensing 19 General System Center Licensing Construct 19 System Center Server Management for Enterprise 20 System Center Client Management for Enterprise 24 System Center Server and Client Management for Midmarket 25 Enrollment for Core Infrastructure Licensing 26 Core Infrastructure Server Suites 27 Program Requirements 27 ECI Migration Paths 28 Pricing Tables and SKUs 30 Windows Server 30 System Center 34 Best Practices and Resources 35 Windows Server Licensing Scenarios 35 Windows Server Upgrade and Downgrade Options 37 Tracking Windows Server Licenses 40 Forefront 2010 Overview 43 Forefront 2010 Offerings 43 FF 2010 Management Product Offerings 43 Forefront 2010 Protection & Access Product Offerings 43 Forefront 2010 Licensing Overview
    [Show full text]
  • Migrating Active Directory to Windows Server 2012 R2
    Windows Server 2012 R2 Migrating Active Directory to Windows Server 2012 R2 Hands-on lab In this lab, you will complete a migration of a Windows Server 2008 R2 domain environment to Windows Server 2012 R2 with no downtime to clients. All roles currently held including FSMO, DHCP and DNS will be transferred to enable the Windows Server 2008 R2 domain controller to be retired. Produced by HynesITe, Inc. Version 1.0 12/15/2013 This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
    [Show full text]
  • No More Excuses: Windows 7 Makes It Easy to Manage Computer Power
    • Products that earn the ENERGY STAR® prevent greenhouse gas emissions by meeting strict energy efficiency guidelines set by the U.S. Environmental Protection Agency and the U.S. Department of Energy. www.energy star.gov NO MORE EXCUSES: WINDOWS 7 MAKES IT EASY TO MANAGE COMPUTER POWER CONSUMPTION ORGANIZATION-WIDE Here’s how you can take advantage of Windows 7’s new power management features The University of Wisconsin at Oshkosh is no stranger to the idea of sustainability. In 2003 it became the first university in the state to join the Environmental Protection Agency’s Green Power Partnership. Its green initiatives also earned the university high marks from the Sierra Club, which ranked the university nationally in its Cool Schools survey. Given this commitment to green, it’s no surprise that the university first deployed computer power management back in 2005, and that it was one of the first Energy Star power management success stories. At that time, the University’s computers ran the Windows XP and Windows 2000 operating systems, neither of which included native tools for the central administration of power management features. To implement power management settings on these machines, the University used third-party software from ENERGY STAR called EZ GPO. For detailed information and resources concerning Now that Windows 7 has CPM client management features built in, it’s much the power management of easier to administer power management. This case study will show you how the University of Wisconsin at Oshkosh took full advantage of computer power PCs running Windows XP, management features on Windows Vista and Windows 7 clients managed by please see the ENERGY STAR Windows Server 2008.
    [Show full text]
  • Security Policy for FIPS 140-2 Validation
    BitLocker Windows Resume Security Policy for FIPS 140‐2 Validation BitLocker® Windows Resume (winresume) in Microsoft Windows 8.1 Enterprise Windows Server 2012 R2 Windows Storage Server 2012 R2 Surface Pro 3 Surface Pro 2 Surface Pro Windows Embedded 8.1 Industry Enterprise StorSimple 8000 Series DOCUMENT INFORMATION Version Number 2.0 Updated On April 22, 2015 © 2015 Microsoft. All Rights Reserved Page 1 of 19 This Security Policy is non‐proprietary and may be reproduced only in its original entirety (without revision). BitLocker Windows Resume The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. This work is licensed under the Creative Commons Attribution-NoDerivs- NonCommercial License (which allows redistribution of the work). To view a copy of this license, visit http://creativecommons.org/licenses/by-nd-nc/1.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
    [Show full text]
  • Chapter 15-70-411FINAL[1]
    Lesson 15: Configuring Service Authentication MOAC 70-411: Administering Windows Server 2012 Overview • Exam Objective 5.1: Configure Service Authentication • Configuring Service Authentication • Managing Service Accounts © 2013 John Wiley & Sons, Inc. 2 Configuring Service Authentication Lesson 15: Configuring Service Authentication © 2013 John Wiley & Sons, Inc. 3 Authentication • Authentication is the act of confirming the identity of a user or system and is an essential part used in authorization when the user or system tries to access a server or network resource. • Two types of authentication that Windows supports are NT LAN Manager (NTLM) and Kerberos. • Kerberos is the default authentication protocol for domain computers. • NTLM is the default authentication protocol for Windows NT, standalone computers that are not part of a domain, and situations in which you authenticate to a server using an IP address. © 2013 John Wiley & Sons, Inc. 4 Understanding NTLM Authentication • NT LAN Manager (NTLM) is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. • NTLM is an integrated single sign-on mechanism. • NTLM uses a challenge-response mechanism for authentication in which clients are able to prove their identities without sending a password to the server. © 2013 John Wiley & Sons, Inc. 5 Managing Kerberos Kerberos: • Is a computer network authentication protocol, which allows hosts to prove their identity over a non-secure network in a secure manner. • Can provide mutual authentication
    [Show full text]
  • Starburn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started
    StarBurn Software Technical Reference Series StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started April 18, 2016 StarBurn Software www.starburnsoftware.com Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 1 of 13 StarBurn Software Technical Reference Series INTRODUCTION .................................................................................................. 4 KEY BENEFITS ..................................................................................................... 5 KEY FEATURES .................................................................................................... 7 SUPPORTED PLATFORMS .................................................................................. 11 SYSTEM REQUIREMENTS................................................................................... 12 CONTACTS........................................................................................................ 13 StarBurn CD/DVD/Blu-Ray/HD-DVD Toolkit: Getting Started Page 2 of 13 StarBurn Software Technical Reference Series COPYRIGHT Copyright © Rocket Division Software 2001-2016. All rights reserved. Copyright © StarBurn Software 2009-2016. All rights reserved. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written
    [Show full text]
  • In Windows Server 2008 R2 and Windows Server 2008 (The Former Containing the Later Release of Hyper-V)
    Hyper-V Microsoft Hyper-V Developer(s) Microsoft Initial release July 26, 2008 (KB950050)[1][2] R2 Service Pack 1 Stable release (KB976932)[3][4] / March 15, 2011; 15 months ago Windows 8 (both its server and client versions) (future) and Operating system Windows Server 2008 or standalone Type Virtual machine License Proprietary Hyper V Slide 1 of 21 Microsoft Hyper-V ■ Microsoft Hyper-V, ✦ codenamed Viridian ✦ and formerly known as Windows Server Virtualization, ✦ is a hypervisor-based virtualization system for x86-64 systems ■ A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008, and the finalized version (automatically updated through Windows Update) was released on June 26, 2008 ■ Hyper-V has since been released in a free stand-alone version, and has been upgraded to Release 2 (R2) status Hyper V Slide 2 of 21 Versions and variants ■ Hyper-V exists in two variants: ✦ as a stand-alone product called Microsoft Hyper-V Server 2008 (Hyper-V Server 2008 R2 for the second release), ✦ and as an installable role in Windows Server 2008 R2 and Windows Server 2008 (the former containing the later release of Hyper-V). ■ The stand-alone version of Hyper-V is free, and was released on October 1, 2008. ■ It is a variant of the core installation of Windows Server 2008 that includes full Hyper-V functionality; other Windows Server 2008 roles are disabled, and there are limited Windows Services. ■ The free Hyper-V Server 2008 variant is limited to a command line interface (CLI), where configuration of the "Host" or "Parent" (Hyper-V Server 2008) OS, physical hardware and software is done using shell commands.
    [Show full text]