Windows Domain Implementation Guide for Windows Server 2016

Total Page:16

File Type:pdf, Size:1020Kb

Windows Domain Implementation Guide for Windows Server 2016 Experion PKS Release 516 Windows Domain Implementation Guide for Windows Server 2016 EPDOC-X472-en-516A August 2020 Disclaimer This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be repro- duced, published, or disclosed to a third party without the express permission of Honeywell Inter- national Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright 2020 - Honeywell International Sàrl - 2 - Contents Contents Contents 3 About this guide 8 Revision history 8 8 Intended audience 8 Prerequisite skills 8 Related documents 8 Getting started 10 Hardware and software requirements 10 Software requirements for a Domain Controller 10 System requirements for a Domain Controller 10 Guidelines 12 General guidelines for implementing a domain controller 12 Installing a Windows Domain Controller 15 Hardware and software requirements 15 Domain configuration worksheet 15 Preparing a Windows Domain Controller 16 Installing Microsoft Windows Server 2016 operating system 16 Defining an alternate Administrative User 17 Changing the computer name 18 Configuring TCP/IP settings 19 Preconfiguring Network Configuration for FTE 20 Installing Microsoft service packs and Windows updates 20 Preparing a Windows Domain Controller 20 Preparing Microsoft Windows Server 2016 to be a Domain Controller 22 Configuring Microsoft Windows Server 2016 as a Domain Controller 23 Setting up a new domain in a new forest 24 - 3 - Contents Adjust Alternate Administrative User’s Group membership 26 Setting up a new domain in an existing forest 26 Adding a Domain Controller to an existing domain 27 Setting up a Read-only Domain Controller 29 Common tasks for setting up a Domain Controller 31 Adding Microsoft Windows Server 2016 to a Windows domain 31 Verifying that the DNS server role is active 32 Verifying that the Global Catalog server role is active 33 Adding a reverse lookup zone 35 Adjusting a DNS Configuration 35 Post Installation Tasks 38 Configuring Active Directory sites 38 Creating a site in the Active Directory 38 Moving Domain Controllers to sites 38 Verifying the availability of a Global Catalog server in a site 39 Adjusting replication intervals for a site 40 Creating an Organizational Unit 41 Prerequisites 41 Creating a Active Directory users and groups 41 Creating Honeywell Active Directory users 41 Creating a Active Directory groups 42 Changing group membership 42 Configuring time synchronization in a domain 43 Adding workstation/server to a Windows domain 44 Setting the DNS server IP address 44 Adding a node to a Windows domain 44 Viewing the workstation/server added to a domain 46 Configuring time synchronization on the workstations/servers added to a Windows domain 46 Prerequisites 46 - 4 - Contents Honeywell Experion PKS Software Support for Domain Controllers 49 Initiating Setup 49 Installing the Domain Controller Policies 50 Installing the .Net Framework 53 Installing Experion Optional Features 53 Preparing the domain for migration 56 Recording the current domain controller configuration information 56 Migration planning worksheet 56 Inventorying the current domain controller configuration 57 Installing Windows Support Tools on Windows Server 2003 domain controllers 57 Identifying the domain controllers holding the FSMO roles 57 Identifying GC servers configured in the domain 58 Identifying DNS servers configured in the domain 59 Identifying the domain operation mode 60 Verifying domain controller readiness for migration 61 Checking the domain health 62 Run the Network Diagnostics (NetDiag) utility 62 Ensuring availability of multiple domain controllers 63 Ensuring availability of multiple DNS servers 63 Preparing the Active Directory 64 Evaluating the functional level of the domain 64 Upgrading existing Domain Controllers to Windows Server 2016 65 Raising the functional level of the domain 65 Expanding the Active Directory schema 66 Joining a Server 2016 Domain Controller to replace an existing Controller 67 Remove the DNS Role (if configured) 67 Installing a new Windows Server 2016 Domain Controller 67 Promote and Join Existing Domain 69 Transfer roles and functions from Old DC to New DC 70 - 5 - Contents Decommission Old DC 71 Raising Functional Levels 71 FRS to DFS Migration 73 Experion domain group policy settings 77 Security Model specific permissions 151 - 6 - CHAPTER - 7 - About this guide About this guide This guide describes how to perform the following: l Implementing Microsoft Windows domain controllers for Experion. l Implementing stand-alone Microsoft Windows domain controllers. l Migrating existing domain controllers to the latest supported Windows operating system for domain controllers. l Demoting domain controllers. Revision history Update the revision history table whenever the document is updated. A revision history table is optional for revision A of a document. If there is a revision B of a document, a revision history table must be added to the document. You can add revisions as A, B, C, D, and so on. Revision Date Description A August 2020 Initial release of the document. Intended audience l Customers who want to integrate their process domains into their corporate hierarchy and IT staffs who support them. l Customers with limited networking and IT experience who are using stand-alone domains. l Projects group and Services group. Prerequisite skills It is assumed that you are familiar with the operation of Experion system software and the plant pro- cesses which Experion controls, Microsoft Windows operating systems, Windows domains and domain controllers, and network administration tasks. Related documents l Windows Domain and Workgroup Implementation Guide l For planning information, refer to Windows Domain and Workgroup Planning Guide l For operation system migration information, refer the appropriate operating system-specific implementation guide Windows Domain Implementation Guide for Windows Server 2008 R2 l Getting Started with Experion Software Guide l Software Installation User's Guide l Experion migration documentation l Supplementary Installation Tasks Guide l Server and Client Overview and Planning Guide l Server and Client Configuration Guide - 8 - CHAPTER - 9 - Getting started Getting started Hardware and software requirements Software requirements for a Domain Controller To implement a domain controller in Experion, you need the following media/software: l Microsoft Windows Server 2016 l Experion PKS R511.1 or Higher System requirements for a Domain Controller Component Microsoft Windows Server 2016 Computer and processor l Minimum – 1.4 GHz (x64) l Recommended – 2GHz or faster Memory l Minimum – 2 GB or greater (Desktop Experience is required) l Recommended – 4GB or greater Hard disk l Minimum – 32GB l Recommended – 32GB or more Attention In virtual environments Honeywell recommends that you have at least one DC on each network level serviced by the virtual environment, this would include a domain controller on level 2.5 and each level 2 network. If the entire domain is hosted on virtual machines, you must ensure that the virtual domain is always availability. Refer to the latest version of the following documents on http://www.honeywellprocess.com for the hardware and software requirements of VM. l HPS Virtualization Specification l Virtualization Planning and Implementation Guide Ensure that at least one domain controller is in real environment. - 10 - CHAPTER - 11 - Guidelines Guidelines General guidelines for implementing a domain controller The following table describes some general guidelines and Honeywell recommendations for imple- menting a domain controller in a domain. Guideline Honeywell recommendation Operating It is recommended to have a Standard Edition with Desktop Experience System Edi- tion Data Center Edition is supported, but not required. Note This guide was developed using only Standard Edition. Server Core, Containers, Nano and other variations/configurations are currently not supported. Honeywell’s installation, utilities, and software require that a user interface be present on the system, so it is required that the system have the “Desktop Exper- ience” present in the Operating System. (This includes the GUI and various sup- porting applications, like Internet Explorer.) Number of It is recommended to have a minimum of two domain controllers per domain. In domain cases where multiple network configurations are used, each network configuration controllers must include at least one domain controller. If you have multiple level 2 with a level 3 per domain network. It is recommend having at least one domain controller on each network level. Domains with multiple OUs must have at least one domain controller per OU. Operating The version of the Windows Server operating system installed on all the domain con- system trollers in a domain should be the same. installed on domain It is recommended to use different versions of the Windows Server operating sys- controllers tem only during a migration scenario. After completing the migration, any servers
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]
  • The Downadup Codex a Comprehensive Guide to the Threat’S Mechanics
    Security Response The Downadup Codex A comprehensive guide to the threat’s mechanics. Edition 2.0 Introduction Contents Introduction.............................................................1 Since its appearance in late-2008, the Downadup worm has become Editor’s Note............................................................5 one of the most wide-spread threats to hit the Internet for a number of Increase in exploit attempts against MS08-067.....6 years. A complex piece of malicious code, this threat was able to jump W32.Downadup infection statistics.........................8 certain network hurdles, hide in the shadows of network traffic, and New variants of W32.Downadup.B find new ways to propagate.........................................10 defend itself against attack with a deftness not often seen in today’s W32.Downadup and W32.Downadup.B threat landscape. Yet it contained few previously unseen features. What statistics................................................................12 set it apart was the sheer number of tricks it held up its sleeve. Peer-to-peer payload distribution...........................15 Geo-location, fingerprinting, and piracy...............17 It all started in late-October of 2008, we began to receive reports of A lock with no key..................................................19 Small improvements yield big returns..................21 targeted attacks taking advantage of an as-yet unknown vulnerability Attempts at smart network scanning...................23 in Window’s remote procedure call (RPC) service. Microsoft quickly Playing with Universal Plug and Play...................24 released an out-of-band security patch (MS08-067), going so far as to Locking itself out.................................................27 classify the update as “critical” for some operating systems—the high- A new Downadup variant?......................................29 Advanced crypto protection.................................30 est designation for a Microsoft Security Bulletin.
    [Show full text]
  • Administrative Guide for Windows 10 and Windows Server Fall Creators Update (1709)
    Operational and Administrative Guidance Microsoft Windows 10 and Windows Server Common Criteria Evaluation for Microsoft Windows 10 and Windows Server Version 1903 (May 2019 Update) General Purpose Operating System Protection Profile © 2019 Microsoft. All rights reserved. Microsoft Windows 10 GP OS Administrative Guidance Copyright and disclaimer 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 VLicense (which allows redistribution of the work). To view a copy of this license, visithttp://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. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred.
    [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]
  • List of CMD COMMANDS a PDF by MYEDUKIT
    List OF CMD COMMANDS A PDF BY MYEDUKIT CMD command Description Basics: call calls a batch file from another one cd change directory cls clear screen cmd start command prompt color change console color date show/set date dir list directory content echo text output exit exits the command prompt or a batch file find find files hostname display host name pause pauses the execution of a batch file and shows a message runas start a program as another user shutdown shutdown the computer sort sort the screen output start start an own window to execute a program or command taskkill terminate a process or an application tasklist display applications and related tasks time display/edit the system time timeout wait any time title set title for prompt ver display operating system version w32tm setting time synchronisation/time server/time zone Network: ftp transfer files to an FTP server ftype display file type and mapping getmac display MAC address ipconfig display IP network settings netsh configure/control/display network components netstat display TCP/IP connections and status nslookup query the DNS pathping test the connection to a specific IP address ping pings the network route display network routing table, add static routes systeminfo displays computer-specific properties and configurations telnet establish a Telnet connection tftp transfer files to a TFTP server tracert trace routes similar to patchping Files: attrib display file attributes comp compare file contents compact display/change file compression copy / xcopy copy files diskcomp
    [Show full text]
  • © Iquila Ltd 2018-2019 - 1
    Rev-1 Joining a Client PC to a Domain Controller using iQuila Server Setup 1. Install the iQuila client software on your windows domain controller server (please note if you have more than one domain controller, you must install the iQuila client software on each domain controller in your network.) 2. Assign a static IP address to the iQuila virtual network adaptor. (Please see Help Document for using Static IP addresses) 3. Go to Control Panel then select view network status and tasks, select change adaptor settings, right click on the iQuila network adaptor (VPN – VPN Client) and client properties. 4. Select Internet protocol version v (TCP/IPv4) and click properties. Select use the following IP address and enter an IP address in your given range, i.e. 192.168.30.9. Enter your given subnet mask i.e. 255.255.255.0 Leave the default gateway setting blank Under the DNS section select use the preferred DNS server address and enter the same address as you entered for the IP address 192.168.30.9 Click ok to save IP address and click on the exit the adaptor properties window. © iQuila Ltd 2018-2019 - www.iquila.com 1 Client Setup 1. Install the iQuila client software on the client computers that you would like to join to the domain and ensure they have registered with the iQuila Cloud server. 2. You now need to set the DNS server address on the iQuila virtual adaptor or contact iQuila support and request the change of DNS address in your Virtual DHCP Server settings.
    [Show full text]
  • Windows 7 End of Life Is Coming: Don't Put Your
    WINDOWS 7 END OF LIFE IS COMING: DON’T PUT YOUR BUSINESS AT RISK BY NOT MIGRATING INTRODUCTION After January 14, 2020, Microsoft will no longer provide free security updates or support for Windows 7 and Windows Server 2008/ 2008 R2 operating systems (OS). This means there will be no more patches available and no more technical support from Microsoft’s support center. If you continue using Windows 7 and Windows Server 2008/R2 after that date, your systems will be at risk due to potential new vulnerabilities and cyber attacks, unless you plan on paying for Windows Extended Security Updates (ESU). With ESU support fees starting at 25~30€ per device and doubling each year after 2020, running Windows 7 and Windows Server 2008/R2 in your environment will quickly become very expensive. To avoid paying these high support costs and to enable successful migration, companies should begin planning for the inevitable upgrade to Windows 10. WHAT ARE THE MAJOR RISKS? Risk of Vulnerabilities and Cyberattacks In 2018, there were 499 Windows desktop OS vulnerabilities reported across Windows Vista, Windows 7, Windows RT, Windows 8/8.1, and Windows 10. Of these, 169 were considered critical vulnerabilities. During the same period, there were 449 Windows Server vulnerabilities, of which 136 were critical. While there was a slight drop in the number of Windows vulnerabilities from 2017 to 2018, over the past 6 years the number has nearly doubled.1 The infamous WannaCry ransomware attack, which infected over 200,000 computers worldwide in May 2017, was the result of an unpatched vulnerability that affected Windows OS.
    [Show full text]
  • Microsoft Windows Server 2016 on Hp Z2 Mini G4, Z240, Z440, Z640, and Z840 Workstations
    TECHNICAL WHITE PAPER CONTENTS & NAVIGATION 1 Before you begin 2 Things you need before you begin Support plan 2-5 Operating system installation process 6 Summary Appendix A: Additional HP support URLs INSTALLING MICROSOFT WINDOWS SERVER 2016 ON HP Z2 MINI G4, Z240, Z440, Z640, AND Z840 WORKSTATIONS BEFORE YOU BEGIN Before starting this process, note the following: • It is very important to be aware of the Microsoft Windows operating system licensing requirements. Contact your Microsoft licensing representative for the proper licensing requirements. • The Web URLs listed in this document are for additional reference. URLs are subject to change or termination. HP makes no attempt to assure that these URLs are current. • By providing this document, HP is not liable for providing any additional consulting services. Contact your HP Sales Representative or Channel Partner to arrange for additional HP Consulting Services. • This document is not meant to be comprehensive in supporting all the possible configurations of the HP Z G4, HP Zx40, and HP Z2 Mini G4 Workstations. Instead, it provides sufficient information to enable key hardware devices. Warning You should always back up all important data (such as personal files, photos, videos, documents, applications, software) before beginning the converter process to avoid any possibility of losing your data. See https://support.hp.com/us-en/document/c03270359 for more information. Following the installation steps outlined in this document will erase your hard drive. If your hard drive already contains information you need to retain, be sure to make a backup copy to a separate location before 1. proceeding with the installation.
    [Show full text]
  • Prepare Customer Site Servers
    Prepare Customer Site Servers • Prepare Customer Site Servers, on page 1 • Prepare Cisco UCS C-Series Customer Site Servers, on page 1 • Prepare HyperFlex M5 series Customer Site Servers, on page 3 • NTP and Time Synchronization, on page 4 • Global Catalog Requirements, on page 5 Prepare Customer Site Servers Perform all the procedures in this section on the Side A and the Side B servers. Prepare Cisco UCS C-Series Customer Site Servers Configure RAID for C240 M4SX The disk array configuration for the C240 M4SX is already set up to match what is required for Packaged CCE. Verify the settings as follows. Using Cisco Integrated Management Controller, check that the following settings are configured correctly: • Virtual Drive Info: RAID 5 with 5 (Physical Disks) * 4 (Virtual Drives/Datastores) • Stripe Size: 128KB • Write Policy: Write Back with BBU • Read Policy: Read Ahead Always For more information regarding RAID configuration for C240 M4SX in Configure RAID with GUI (UCS C-Series M4 Servers) section, see Cisco Collaboration on Virtual Servers Guide at: https://www.cisco.com/ c/en/us/td/docs/voice_ip_comm/cucm/virtual/CHCS_BK_C7C7ED05_00_cisco-collaboration-on-virtual-servers/ CHCS_BK_C7C7ED05_00_cisco-collaboration-on-virtual-servers_chapter_01.html#CUCM_TK_C2DC4F2D_ 00. Prepare Customer Site Servers 1 Prepare Customer Site Servers Run the RAID Config Validator Utility Run the RAID Config Validator Utility After you set up RAID configuration and add the datastores, run the RAID Config Validator utility to ensure that your datastore configuration is correct. Before you begin To run the utility, Java 7 (any update) must be installed. Java 8 and later releases are not supported.
    [Show full text]
  • Platform Support Matrix for SAP Business
    Platform Support Matrix PUBLIC SAP Business One Document Version: 1.28 – 2021-05-07 SAP Business One Platform Support Matrix Release 9.0 and higher Typographic Conventions Type Style Description Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example Emphasized words or expressions. EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE Keys on the keyboard, for example, F2 or ENTER. PUBLIC © 2021 SAP SE or an SAP affiliate company. All SAP Business One Platform Support Matrix 2 rights reserved. Typographic Conventions Document History Version Date Change 1.0 2014-02-12 Release Version 1.01 2014-05-08 SAP Note 1787431 link added on XL Reporter platform support restrictions 1.02 2014-07-08 SAP Business One 9.1 added to the overview
    [Show full text]
  • For Those in Operating System Limbo
    By Merle Windler, Thoroughbred Systems, Inc. ComputerComputerCornerCorner TenTen TipsTips forfor WindowsWindows 10,10, PartPart 11 .. .. .. Ah,Ah, Yes,Yes, ThatThat MeansMeans FiveFive forfor Now,Now, FiveFive LaterLater y the time this issue of The Lifeline is delivered, the announced deadline of June 29, 2016 will have passed Bfor a FREE Windows 10 upgrade for those with qualifying versions of Windows 7, Windows 8, or Windows 8.1. Hopefully the information provided on this subject in an earlier Computer Corner article helped readers not only in making up their minds when or if to update within the "FREE UPDATE" period, but also aided those who did so in making those updates go smoothly and without data loss. Some of Microsoft's customers were taken by surprise at the boldness of that corporate giant. As the deadline date Tip 1: Classic Shell Windows XP or approached, many found Microsoft's tactics to be nothing Windows 7 Style Menus short of pushy. We received scores of morning phone calls First, If you are a "creature of habit" and prefer the "old in the past month when municipal and rural water district style" classic Windows Menu style of Windows XP and staff realized that computers left on overnight had Windows 7 over the new “Menu and Tiles” and "Metro automatically begun the Windows 10 upgrade process Style Apps" appearance of Windows 10, don't worry, and they were faced with a screen asking them to there's a very popular FREE program called "Classic Shell" continue the Windows 10 upgrade by choosing “Next”, or that'll fix you right up.
    [Show full text]
  • Ultimate Spider-Man™ README Last Updated: 6/28/05
    Ultimate Spider-Man™ README Last Updated: 6/28/05 TABLE OF CONTENTS INTRODUCTION INSTALLATION & SET UP 1. Minimum System Requirements 2. Autoplay 3. DirectX(R) Detection & Installation VIDEO ISSUES 1. Monitors 2. In-game and Desktop Resolutions 3. Graphical Corruption When Changing Video Settings 4. Windowed Mode/Standby Mode 5. Changing Brightness and Contrast GENERAL ISSUES 1. Alt-Tab & Alt-Enter 2. Uninstalling with Antivirus Software Enabled 3. Gamepad Options 4. Invert Controls Setting 5. Options for Lower End Systems INTRODUCTION Refer to this document if you encounter difficulties with one or more aspects of installation or running the Ultimate Spider-Man™ game. Many of the most commonly encountered issues are covered here. INSTALLATION & SET UP 1. Ultimate Spider-Man™ Minimum System Requirements • 3D hardware accelerator card required - 100% DirectX(R) 9.0c-compliant 64 MB video card and drivers* • Microsoft(R) Windows(R) 2000/XP • Pentium(R) III 1.2 GHz or Athlon(TM) 1.2 GHz or higher processor • 256 MB of RAM • 3500 MB of uncompressed hard disk space (plus 400 MB for the Windows(R) swap file) • A 100% Windows(R) 2000/XP - compatible computer system including: • DirectX(R) 9.0c (Included) • 100% DirectX(R) 9.0c-compliant true 16-bit sound card and drivers • 100% Windows(R) 2000/XP - compatible mouse, keyboard and drivers • 100% Windows(R) 2000/XP - compatible quad speed CD-ROM drive (600 K/sec sustained transfer rate) and drivers *Supported Chipsets for Windows 2000/XP All NVIDIA(R) GeForce2(TM) and better chipsets All ATI(R) Radeon 7500(TM) and better chipsets *Important Note: Some 3D accelerator cards with the chipsets listed here may not be compatible with the 3D acceleration features utilized by Ultimate Spider-Man™.
    [Show full text]