Windows Domain Implementation Guide for Windows Server 2016
Total Page:16
File Type:pdf, Size:1020Kb
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