DOCSLIB.ORG

Installing Windows Server 2003

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Installing Windows Server 2003 Installing Windows Server 2003 This guide covers only the setup of Windows Server 2003, Standard Edition. For information on setting up your network hardware, consult a qualified network technician. The process of installing Windows Server 2003® involves three steps: 1 Extract mass storage device drivers. 2 Install the Windows 2003 Server operating system. 3 Install hardware device drivers. 1 Installing Windows Server 2003 Extracting drivers When you install Windows Server 2003, some drivers are not automatically installed and must be installed manually. If you have one of the following devices, extract the correct driver from the Server Companion CD to a diskette before you begin the Windows Server 2003 installation: ■ Gigabit Ethernet NIC (for Gateway 920, 960, 980, 955, and 975 servers) ■ Integrated Adaptec SCSI controller with RAID (for Gateway 955 and 975 servers) ■ Third IDE channel (for Gateway 920 server) To extract drivers: ■ See Using Your Server Companion CD for instructions on extracting drivers. System Requirements Important Important: your server may be able to support more memory than your operating system can recognize. Requirement Standard Edition Enterprise Edition Web Edition Recommended 256 MB 256 MB 256 MB minimum memory Maximum memory 4GB 32GB 2GB supported Maximum number of 482 physical processors Disk space for setup 1.5 GB 1.5 GB 1.5 GB 2 www.gateway.com Installing Windows Server 2003 Installing Windows Server 2003 Selecting the disk file system Any partitions you create during installation must be formatted. You can format each partition using the FAT file system or NTFS. You can also convert an existing FAT partition to NTFS. If you plan to dual boot Windows 2003 Server with MS-DOS® or Windows® 95, you must select the FAT file system. Consider the following when selecting your file system: Considerations NTFS FAT Security Supports complete Files are not protected by the Windows Server 2003 security, so security features of you can control access to files or Windows Server 2003. folders. Activity log Keeps a log of activities to restore Does not keep a log. the disk in the event of power failure or other problems. File sizes Maximum file size is 4 GB to 64 GB, Maximum file size is 4 GB. depending on the size of the clusters. File compression Supports flexible per-file Does not support file compression. compression. Operating system Only recognized by Windows NT, Allows access to files when your compatibility Windows Server 2003, and computer is running another Windows XP. When the computer is operating system, such as running other operating systems, MS-DOS or OS/2. such as MS-DOS or OS/2®, those operating systems cannot access files on an NTFS partition on the same computer. MS-DOS data sharing Does not let you share data with Lets you share data with MS-DOS MS-DOS on the same partition. on the same partition. www.gateway.com 3 Installing Windows Server 2003 To install Windows Server 2003: 1 Insert the Windows Server 2003 Setup CD into the CD drive, then restart your server. 2 When you see the prompt “Boot from CD,” press any key. Your server starts from the CD, and the Window Server 2003, Standard Edition Setup screen opens. A message reminds you that you have 14 days to activate this installation before it is deactivated. 3 Press ENTER. The Welcome to Setup screen opens. 4 Press ENTER. The Licensing Agreement screen opens. 5 To agree to the license agreement conditions, press F8. If an old operating system installation is found and listed on the screen, press ESC to close the message box. The Partition screen opens, which displays existing hard drive partitions. 6 Use the arrow keys to select a partition to install to, then press ENTER. If a message tells you that another operating system was found on this partition, press C. The Choose Format Options screen opens. 7 Use the arrow keys to select a partition format, then press ENTER. We recommend that you select NTFS file system (Quick). You can also choose to leave the current file system intact (no changes). The Format Confirmation screen opens. Tips & Tricks When you choose to run a regular format on a volume, files are removed from the volume you are formatting and the hard drive is then scanned for bad sectors. The scan for bad sectors is responsible for the majority of the time it takes to format a volume. If you choose the Quick format option, format removes files from the partition but does not scan the disk for bad sectors. This option should only be used if your hard drive has been previously formatted and you are sure that your hard drive is not damaged. If you installed Windows on a partition that was formatted by using the Quick format option, you can check your hard drive by using the chkdsk /r command after the installation has completed. 4 www.gateway.com Installing Windows Server 2003 8 To begin formatting, press F. The hard drive is formatted, setup files are copied to the hard drive, then your server restarts. 9 When you see the prompt Boot to CD after your server restarts, do not press any key or the installation process will restart. Wait several seconds until the Regional and Language Options dialog box opens. 10 If you want to change regional settings, click Customize, make your changes, then click OK. 11 If you want to change the keyboard layout, click Details, make your changes, then click OK. 12 Click Next. The Personalize Your Software dialog box opens. 13 Type your name and organization name, then click Next. 14 If you are prompted for your Product Key, type your Product Key in the boxes, then click Next. Your Product Key is located on the Microsoft Certificate of Authenticity label found on the back or side of your server. The Licensing Modes dialog box opens. 15 For your licensing mode, select Per Server and specify the number of concurrent connections (each connection must have its own Client Access License). - OR - Select Per Device or Per User (each device or user must have a separate Client Access Licence). 16 Click Next. The Computer Name and Administrator Password dialog box opens. 17 Type a unique name for your server in the Computer Name box, type an administrator password in the Administrator password and Confirm password boxes, then click Next. The Date & Time Settings dialog box opens. Important When creating a password for your server, we recommend you follow these guidelines to help keep the password secure: ■ Make it at least six characters long. ■ Do not include the words “admin” or “administrator.” ■ Use a mixture of both uppercase and lowercase letters. ■ Include numerals. ■ Include non-alphanumeric characters. www.gateway.com 5 Installing Windows Server 2003 18 Select the Date, Time, and Time Zone, then click Next. The Networking Settings dialog box opens. 19 Click Typical Settings or Custom Settings, then click Next. If you do not want special settings, we recommend you select Typical Settings. The Workgroup or Computer Domain dialog box opens. 20 Click Workgroup and type the workgroup name or click Domain and type the domain name, then click Next. After the installation has finished, your server reboots, Windows Server 2003 starts, and the Login dialog box opens. 21 Press CTRL+ALT+DELETE to enter your administrator password. Tips & Tricks In order to shut down or restart your server, you must enter an Option and Comment in the Shutdown Event Tracker, then click OK. 6 www.gateway.com Installing Windows Server 2003 Installing hardware device drivers Important Before installing Small Business Server, BackOffice, or other programs, install your server’s hardware device drivers. If you do not install the drivers first, certain program features or components may not be installed. To install hardware device drivers: ■ See Using Your Server Companion CD for instructions on installing hardware device drivers. Disabling the Windows Shutdown Event Tracker The Shutdown Event Tracker enables you to record the reasons for any unexpected shutdowns of your operating system and appears each time you turn on or restart Windows Server 2003. The Shutdown Event Tracker is enabled by default on all editions of Windows Server 2003. To disable the Shutdown Event Tracker: 1 Click Start, then click Run. The Run dialog box opens. 2 Type gpedit.msc, then click OK. The Group Policy Object Editor window opens. 3 Double-click Local Computer Policy, Computer Configuration, Adminstrative Templates, then double-click System. 4 On the right side of the screen, double-click Disable Shutdown Event Tracker. The Display Shutdown Event Tracker Properties dialog box opens. 5 Click Disabled, then click OK. The Shutdown Event Tracker is disabled. www.gateway.com 7 Installing Windows Server 2003 © 2003 Gateway, Inc. All rights reserved. Gateway, Gateway Country, the Gateway stylized logo, and the black-and-white spot design are trademarks or registered trademarks of Gateway, Inc. in the United States and other countries. All other brands and product names are trademarks or registered trademarks of their respective companies. A MAN MS SERVER INSTALL GDE R0 4/03 8 www.gateway.com.
Load more

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]
  • When Windows 2000 Or Windows Server 2003 Is Introduced
    IMPORTANT INFORMATION FOR PRIMERGY CUSTOMERS July 11th, 2007 FUJITSU, LTD. NOTICE: Any server using an Intel Xeon 7100 or higher model CPU and has either Windows 2000, Windows 2000 Server, or Windows 2003 Server installed may encounter a “blue screen.” The problem occurs when the operating system running on a computer with a fast processor and a large L3 cache encounters a timing problem with asynchronous hardware. Although Fujitsu has not received any reports of this problem to date, there is a possibility that PRIMERGY server products may be affected. Problem: Any computer running any edition of Windows 2000, Windows 2000 Server, or Windows 2003 with an Intel Xeon processor (model 7100 or higher) that utilizes a large L3 cache may generate a “blue screen.” An error similar to: STOP 0x0000008E(parameter1, parameter2, parameter3, parameter4) KERNEL_MODE_EXCEPTION_NOT_HANDLED or STOP 0x0000001E(parameter1, parameter2, parameter3, parameter4) KERNEL_MODE_EXCEPTION_NOT_HANDLED may be displayed with Windows 2003-based and Windows 2000-based computers, respectively. Affected Operating Systems: Microsoft® Windows® 2000 Server Microsoft® Windows® 2000 Advanced Server Microsoft® Windows Server® 2003, Standard Edition (*) Microsoft® Windows Server® 2003, Enterprise Edition (*) (*)This problem has been corrected in Service Pack 1 for Windows Server 2003. Therefore Windows 2003 Server SP1 is not affected by this problem. Affected Fujitsu PRIMERGY models: The following models use Intel Xeon 7100 or higher processors. PRIMERGY Models, Product Codes, and CPU z PRIMERGY RX600 S3 (SAS), Product codes PGR603D* and PGR603B* ¾ Dual Core Intel® Xeon® Processor 7140M (3.40GHz)/7120M (3GHz) z PRIMERGY RX600 S3, Product codes PGR6038* and PGR6036* ¾ Dual Core Intel® Xeon® Processor 7140M (3.40GHz)/7120M (3GHz) * Changes by type.
    [Show full text]
  • Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012
    Feature Comparison Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 Contents Introduction ............................................................................... 3 Top Ten Features ...................................................................... 4 General Features Overview .................................................... 8 © 2012 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Feature Comparison: Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 2 Introduction This feature comparison guide compares selected features of Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012. The “Top Ten Features” section provides an overview of some of the most important features of Windows Server 2012, and the “General Features Overview” section compares a wider-range of features across all three releases. The comparison tables in both sections include comments in regard to each release, as well as notation about how well each feature is supported. The legend for this notation is as follows: Level of Feature Support Feature is supported Feature is only partially supported Feature is not supported Feature Comparison: Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 3 Top Ten Features This section provides an overview of the top ten features of Windows Server 2003
    [Show full text]
  • Migrating from Windows 2000 to Windows Server 2003
    23 0672326671 CH17 4/15/04 10:56 AM Page 463 CHAPTER 17 IN THIS CHAPTER •Windows Server 2003 Migrating from Migration Overview • Beginning the Migration Windows 2000 to Process Windows Server 2003 • Upgrading a Single Member Server • Upgrading a Windows 2000 Active Directory Forest Windows Server 2003 • Upgrading Separate AD Migration Overview Forests to a Single Forest In many ways, a migration from Windows 2000 to Windows Using Mixed-Mode Domain Server 2003 is more of a service pack upgrade than a major Redirect migration scenario. The differences between the operating • Consolidating and Migrating systems are more evolutionary than revolutionary, and there Domains Using the Active subsequently are fewer design considerations than in upgrades from the NT 4.0 operating system. Directory Migration Tool v2.0 That said, several immediate improvements to the operating • Consolidating a Windows system can be realized through migration to Windows Server 2000 Domain to a Windows 2003, whether by migrating all servers immediately or by Server 2003 Domain Using using a slow, phased approach. Improvements to Active ADMT v2.0 Directory (AD), such as the ability to rename domains and • Best Practices greater scalability, provide incentive for Windows 2000 Active Directory environments to begin migration. Standalone server improvements such as Terminal Services, File and Print Server improvements, Automated Server Recovery, and many more also serve to encourage migrations. This chapter focuses on the planning, strategy, and logistics of migration from Windows 2000 to Windows Server 2003. In addition, specialized procedures such as using Mixed-Mode Domain Redirect and migrating using the Active Directory Migration Tool (ADMT) are described, and step-by-step instructions complement these processes.
    [Show full text]
  • Windows Server 2003 End of Support One Year Later
    Windows Server 2003 End of Support One Year Later There's an elephant in the room..Windows Server 2003 Windows Server 2003 has been unsupported by Microsoft for almost a year now, with a number of organizations taking a custom support agreement from Microsoft while they plan their modernization. The increased costs & risk incurred with running on an unsupported platform will continue to rise with age, including the doubling, and doubling again of support agreements cost over the next two years. Avanade can help you understand the steps to get started on your modernization journey, how to drive new business value from it, and the ways in which you can achieve it. Avanade’s portfolio of Windows Server 2003 Use Windows Server 2003 end modernization solutions of support as a catalyst for your Business Case – Gain insight into best practices & build your modernization business case IT modernization Modernization Proof of Concept – Full Server 2003 retirement report & migration of two applications ©2016 Avanade Inc. All rights reserved. Windows Server 2003 End of Support One Year Later The Elephant In The Room Enterprises still relying on Windows Server 2003 are faced with two options, do something and purchase a custom support agreement (CSA) from Microsoft or do nothing and run the risk of using an unsupported operating system. Infection rate by server operation system Third and fourth quarters of 2014 8 Microsoft Custom Support Agreements 7 3Q14 Example 1500 server environment 6 4Q14 5 $900k $1.8M $3.6M 4 3 2 Computers cleaned per 1000 scanned 1 2015 2016 2017 0 Server Server Server Server Server 2003 SP2 2008 SP2 2008 R2 2012 2012 SP2 Cost of doing something Cost of doing nothing Microsoft custom support agreement (CSA) fees are set to Microsoft data shows that Windows Server 2003 infection rates double and double again in the next two years1.
    [Show full text]
  • GENESIS32 – DCOM on Windows XP and Server 2003 in a Domain December 2007 Description: Guide to Setup DCOM on a Windows XP Or 4
    GENESIS32 – DCOM on Windows XP and Server 2003 in a Domain December 2007 Description: Guide to setup DCOM on a Windows XP or 4. The My Computer Properties window will open. Click on Windows Server 2003 Operating System when computers are in the Default Properties tab, and match the properties as a domain on the Local Area Network. shown in Figure 2. OS Requirement: Windows XP/Server 2003. General Requirement: In order to communicate OPC data between different PCs via DCOM in a domain, the following requirements apply: • All GENESIS32 machines must be in the same domain on the LAN. • All GENESIS32 machines must be logged in to the operating system with a domain user. • The password must not be blank or “admin”. • The user must have administrative privileges to the local PC to change the DCOM settings. • Windows XP machines must have SP1 installed. Introduction For GENESIS32 Applications to communicate via DCOM, it is necessary to allow Access and Launch permissions for specific users. This application note explains how to setup DCOM on a Windows XP or Windows Server 2003 Operating System, for the most wide-open permissions. It is usually helpful to develop your application with wide-open communications to be sure that it all works properly. After you have completed your Figure 2 - My Computer Default Properties development, you will want to tighten these permissions until you reach a desired level of security 5. Next we have to add user permissions to the Default Security. Click the Default COM Security tab as shown in Editing DCOM Settings Figure 3 1.
    [Show full text]
  • XP on Your Thumb Drive
    Langa Letter: XP On Your Thumb Drive Fred Langa offers a step-by-step and illustrated guide on how to boot XP from an ordinary USB drive. By Fred Langa, InformationWeek Jan. 23, 2006 URL: http://www.informationweek.com/story/showArticle.jhtml?articleID=177102101 Chances are you already either have a USB "thumb" drive, or you will have one in the near future--these little solid-state flash memory devices are inexpensive, nearly ubiquitous, and very, very handy. Not only can they replace floppy drives for casual file transfers, but the larger capacity thumb drives also can serve as the basis for an excellent, fit-in-your-pocket software repair kit, letting you diagnose and repair PCs, including those that might otherwise be unbootable or that are locked by password or other problems. We've discussed USB drives before in "What's Behind The USB Drive Revolution". We also looked at ways to make a USB drive bootable from DOS in "Solving USB Boot Problems". We've also mentioned ways to boot from Linux (such as is discussed in this HowTo or in this Google search.) If you missed either of those earlier articles and references, this would be a good time to click back and catch up so we'll all be starting on the same page. But when we left off our discussion of USB drives, there was no good way to boot XP from a thumb drive because of the way that XP takes over USB control as the operating system starts -- in effect, XP tries to take over the USB system it's already using to boot from, with unpredictable results.
    [Show full text]
  • Assessing Network Security.Pdf
    PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2004 by Ben Smith, David LeBlanc, Kevin Lam All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Cataloging-in-Publication Data Lam, Kevin. Assessing Network Security/ Kevin Lam, David LeBlanc, Ben Smith. p. cm. Includes index. ISBN 0-7356-2033-4 1. Computer networks--Security measures. I. LeBlanc, David, 1960- II. Smith, Ben. III. Title. TK5105.59.L36 2004 005.8--dc22 2004049997 Printed and bound in the United States of America. 1 2 3 4 5 6 7 8 9 QWT 9 8 7 6 5 4 Distributed in Canada by H.B. Fenn and Company Ltd. A CIP catalogue record for this book is available from the British Library. Microsoft Press books are available through booksellers and distributors worldwide. For further information about international editions, contact your local Microsoft Corporation office or contact Microsoft Press International directly at fax (425) 936-7329. Visit our Web site at www.microsoft.com/learning/books/. Send comments to [email protected]. Active Directory, ActiveX, Encarta, FrontPage, Hotmail, InfoPath, Microsoft, Microsoft Press, MSDN, MSN, Outlook, Visual Basic, Win32, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious.
    [Show full text]
  • IBM Barts PE Presenatation
    BarBartt’’ss PPEE JoJossee MeMeddeieiroross MCP+I,MCP+I, MMCSCSE,E, NT4NT4 MCTMCT Course Number Presentation_ID © 1999, Cisco Systems, Inc. 1 WWhhatat iiss BBart’art’ss PEPE?? •Bart's PE Builder is a free tool that helps you build a "BartPE" (Bart Preinstalled Environment) bootable Windows CD-Rom or DVD from the original Windows XP or Windows Server 2003 installation/setup CD, very suitable for PC maintenance tasks. • Bart’s PE gives you a complete Win32 environment with network support, a graphical user interface (800x600) and FAT/NTFS/CDFS filesystem support. Very handy for burn-in testing systems with no OS, rescuing files to a network share, virus scan and so on. •This will replace any Dos bootdisk in no time! Course Number Presentation_ID © 12990090, Cisco Systems, Inc. 2 WWhyhy DDidid II SSwitwitchch toto BBartsarts PPE?E? • DOS Boot Disks Use Lanmanger v2.1 • SMB / CIFS Authentication Issue using Microsoft Active Directory 2003 in Native Mode. • Dos and earlier version of Windows does not support NTLMv2 or SMB signing as well as earlier versions of SAMBA and MAC OS X. Presentation_ID © 1999, Cisco Systems, Inc. 3 BBart’art’ss PEPE UUsesess 3232 BBitit DDririversvers • BartBart''ss PPEE BBuilduilderer usesuses 3232 BBitit NNeetwtworkork CoControllerntroller andand SStoragtoragee CCoontrntroollerller driversdrivers • ThThisis allowallowss yyoouu ttoo accessaccess ddiskisk rraaidid arrayarrayss andand wwitithh NetwoNetworkrk conconttrorollerller ssupuppoportrt alloallowwss yyoouu ttoo imimagagee anan enenttireire serverserver overover etherneethernett ttoo aa NetwoNetworkrk shareshare oonn aa DDASAS,, NNASAS oror SSAANN ArrayArray • BartBart’s’s PPEE hhasas bbuiltuilt inin UUSSBB 2.02.0 susupppportort whwhichich allowallowss yyouou ttoo accessaccess anan exexternalternal UUSSBB 2.02.0 hardhard drive.
    [Show full text]
  • Preparing for Windows Server 2003/R2 EOS
    Preparing for Windows Server 2003/R2 EOS Dell Services & Solutions Fast, flexible path from Windows Server migration to future-ready IT Are you ready? 3 The end of service for Windows Server 2003/R2 1 Directions on Microsoft, Migrating from Windows Server 2003 and 2003 R2, February 24, 2014 2 Microsoft TechEd, Windows Server 2003 End-of-Support Application Migration, June 2014 4 What the end of service will mean to you No No No Now updates compliance safe haven is the time to act WindowsImpactStart37 critical planning on 2003/R2 updates both your servers released migrationImpact will not on and transformingIncreased your datacenter todayDiscontinued passphysicalin 2013 a compliance for and Windows audit ServerMicrosoft Small operations costs support for virtualized2003/R2 Business Server many servers 2003 applications Microsoft TechEd, Windows Server 2003 End-of-Support Application Migration, June 2014 5 What’s your state of readiness? 57% 53% 23% 12% of Microsoft customers are worried about are worried about Are worried about are still running security compliance & increases support costs regulatory compliance WS2003/R21 vulnerability and downtime caused by requirements caused by management caused by WS2003/R2 EOS2 WS2003/R2 EOS2 WS2003/R2 EOS2 94% 40% 94% of those running of those running WS2003/R2 intend to WS2003/R2 are not sure $200,000+ / year migrate, but only 24% of the upgrade path1 an average for custom support costs post- are ready to do so1 WS2003/R2 EOS in order to stay within specific industry regulations3 24% 1 CloudPost,
    [Show full text]
  • Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012
    Feature Comparison Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 Contents Introduction ................................................................................. 3 Top Ten Features ....................................................................... 4 General Features Overview ..................................................... 8 © 2012 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Feature Comparison: Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 2 Introduction This feature comparison guide compares selected features of Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012. The “Top Ten Features” section provides an overview of some of the most important features of Windows Server 2012, and the “General Features Overview” section compares a wider-range of features across all three releases. The comparison tables in both sections include comments in regard to each release, as well as notation about how well each feature is supported. The legend for this notation is as follows: Level of Feature Support Feature is supported Feature is only partially supported Feature is not supported Feature Comparison: Windows Server 2003 R2, Windows Server 2008 R2, and Windows Server 2012 3 Top Ten Features This section provides an overview of the top ten features of Windows Server
    [Show full text]