1. Trang chủ
  2. » Công Nghệ Thông Tin

Tài liệu Module 4: Minimizing the Impact on Network Operations During an Upgrade doc

48 384 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Định dạng
Số trang 48
Dung lượng 1,43 MB

Nội dung

# &RQWHQWV## # 2YHUYLHZ#4 # 0DLQWDLQLQJ#1HWZRUN#6HUYLFHV## 'XULQJ#DQ#8SJUDGH#5 # 0DLQWDLQLQJ#6HFXULW\#'XULQJ#DQ#8SJUDGH#49 # 'HWHUPLQLQJ#WKH#,PSDFW#RI#DQ## 8SJUDGH#RQ#$SSOLFDWLRQV#57 # /HYHUDJLQJ#([LVWLQJ#'LUHFWRU\#,QIRUPDWLRQ#58 # 0DLQWDLQLQJ#1HWZRUN#3HUIRUPDQFH## 'XULQJ#DQ#8SJUDGH#5: # /DE#$=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN## 2SHUDWLRQV#'XULQJ#DQ#8SJUDGH#64 # 5HYLHZ#74 # # Module 4: Minimizing the Impact on Network Operations During an Upgrade # Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. 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.  2000 Microsoft Corporation. All rights reserved. Microsoft, MS, Windows, Windows NT, Active Directory, and Windows 2000 are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Other product and company names mentioned herein may be the trademarks of their respective owners. Project Lead/Instructional Designer: Sangeeta Garg (NIIT (USA) Inc.) Lead Program Manager: Angie Fultz Instructional Designer: Robert Deupree (S&T OnSite) Subject Matter Expert : Brian Komar (3947018 Manitoba Inc) Technical Contributors: John Pritchard, Greg Parsons, David Cross, Rodney Fournier, Tony de Freitas, Christoph Felix, Shaun Hayes, Megan Camp, Richard Maring, Glenn Pittaway, Anne Hopkins, Bob Heath, Jeff Newfeld, Jim Glynn, Paul Thompson (Mission Critical Software, Inc.), David Stern, Lyle Curry, Steve Tate, Bill Wade (Wadeware LLC). Testing Leads: Sid Benavente, Keith Cotton Testing Developer: Greg Stemp (S&T Onsite) Testers: Testing Testing 123 Instructional Design Consultants: Susan Greenberg, Paul Howard Instructional Design Contributor: Kathleen Norton Graphic Artist: Kirsten Larson (S&T OnSite) Editing Manager: Lynette Skinner Editors: Marilyn McCune (Sole Proprietor), Wendy Cleary (S&T OnSite), Jane Ellen Combelic (S&T OnSite) Copy Editor: Shawn Jackson ( S&T Consulting) Online Program Manager: Debbi Conger Online Publications Manager: Arlo Emerson (Aditi) Online Support: Eric Brandt (S&T Onsite) Multimedia Development: Kelly Renner (Entex) Testing Leads: Sid Benavente, Keith Cotton Testing Developer: Greg Stemp (S&T OnSite) Courseware Testing: Data Dimensions, Inc. Production Support: Lori Walker (S&T Consulting) Manufacturing Manager: Rick Terek (S&T Onsite) Manufacturing Support: Laura King (S&T Onsite) Lead Product Manager, Development Services: Bo Galford Lead Product Managers: Dean Murray, Ken Rosen Group Product Manager: Robert Stewart # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH##LLL# ,QVWUXFWRU#1RWHV# This module provides students with the ability to develop a strategy for upgrading from Microsoft ® Windows NT ® version 4.0 to Microsoft Windows ® 2000 while maintaining network reliability, security, availability, and performance. At the end of this module, students will be able to: „# Examine existing network services and develop a strategy for ensuring their reliability during an upgrade. „# Determine how a domain upgrade will modify existing security and develop a strategy for maintaining desired security levels during the upgrade. „# Determine in advance how server applications will behave in a Windows 2000 environment. „# Describe how the Active Directory ™ Connector (ADC) allows migration of user attributes to the Active Directory directory service. „# Develop a strategy for regulating traffic to optimize network performance during the upgrade. 0DWHULDOV#DQG#3UHSDUDWLRQ# This section provides you with the required materials and preparation tasks that are needed to teach this module. 5HTXLUHG#0DWHULDOV# To teach this module, you need the following materials: „# Microsoft PowerPoint ® file 2010A_04.ppt „# Module 4, “Minimizing the Impact on Network Operations During an Upgrade” 3UHSDUDWLRQ#7DVNV# To prepare for this module, you should: „# Read all of the materials for this module. „# Read all of the delivery tips. „# Complete the lab. „# Read chapter 10 of the Windows 2000 Server Deployment Planning Guide, “Determining Domain Migration Strategies,” on the Student Materials compact disc. „# Read chapter 21 of the Windows 2000 Server Deployment Planning Guide, “Testing Applications for Compatibility with Windows 2000,” on the Student Materials compact disc. „# Read chapter 23 of the Windows 2000 Server Deployment Planning Guide, “Defining Client Administration and Configuration Standards,” on the Student Materials compact disc. 3UHVHQWDWLRQ=# 93#0LQXWHV# # /DE=# 93#0LQXWHV# LY##0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH# 0RGXOH#6WUDWHJ\# Use the following strategy to present this module: Make sure that students understand that the strategies outlined in this module are steps that must be added to the basic upgrade plan if an organization’s current network environment warrants it. Not all upgrade plans will include all strategies outlined in this module. Be prepared throughout this module to provide a quick review of each service to students who may not have an extensive Windows NT 4.0 background. You may wish to use the Glasgow computer in class to demonstrate various Windows NT 4.0 tools or to draw comparisons. This module is one of the longer modules of the course. Consider taking a short break in the middle of the module. Keep students’ attention and interest by asking questions about what services, security, needs, or requirements exist in their environment and how each topic might impact them. „# Maintaining Network Services During an Upgrade For many students, network reliability will be the area of greatest concern. Several of the topics in this section discuss differences in the way that Windows NT 4.0 and Windows 2000 manage common networking services. Although these topics reveal potential pitfalls, you will also discuss why other areas should not be an issue during the domain upgrade. Emphasize the importance of careful planning when considering network reliability. Be prepared to provide a short review of basic concepts of the Domain Name System (DNS), to put the first topic of this section into context for students who lack prerequisite knowledge. You may wish to summarize a few of the benefits of Active Directory integrated zones. Consolidating DNS and Active Directory replication eliminates the need to maintain multiple replication topologies; multi-master writes eliminate the single point of failure in the DNS hierarchy, and secure dynamic updates prevent unauthorized changes to resource records. Whichever method is chosen for DNS server upgrades, it is best if the DNS server that holds the primary zone data is a Windows 2000 Server to support SRV (service) resource records and dynamic update. The proper SRV record format in the zone text files on a Windows NT 4.0 DNS server is maintained and is displayed once the DNS server is upgraded to Windows 2000. Make sure that students understand that a pure Windows 2000 network contains only Windows 2000 clients and servers Students should remember from prerequisite courses that Dynamic Host Configuration Protocol (DHCP) can be configured to always update DNS or only when the client requests it. It can also be configured to clean up host (A) resource records when a lease expires. Supporting LAN Manager replication during an upgrade is a rather complex topic because it involves many different components and steps. Make sure that students begin with a clear understanding of the difference between NTLM protocol replication, File Replication service (FRS) and multi-master replication. Students may have many questions on this topic, so be prepared to provide background information and communicate the need for planning this service’s integration with Windows 2000. # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH##Y# Supporting Remote Access Service (RAS) during an upgrade is also a complex topic to explain because of the many different scenarios in which an organization can find its RAS servers as an upgrade proceeds. Take the time to thoroughly explain all the different gyrations. Make sure you read the Group Policy documents referenced in the module. Many students may still be confused about the function and purpose of Group Policy. „# Maintaining Security During an Upgrade An upgrade to Windows 2000 will have a minimal effect on user accounts, group accounts, user profiles, and trust relationships. Students working with sensitive information will be particularly interested in how changes to trusts affect administrative access. Emphasize that these changes are designed to take advantage of new Active Directory features and will likely result in tightened security in the long term; but in migrating to the new environment, students need to change the way they think about security administration and implementation, and security templates. „# Determining the Impact of an Upgrade on Applications The only way to determine the impact that an upgrade will have on an application is to perform a test. Emphasize to students that testing applications is just one component of the much larger domain upgrade test. Developing a test plan is covered in more detail in module 7 “Planning to Deploy a Migration Strategy” of course 2010A, Designing a Microsoft Windows 2000 Migration Strategy. „# Leveraging Existing Directory Information Many applications store user attributes that can be ported into Active Directory. This topic focuses on Microsoft Exchange 5.5 as an example of how an application information store can be used to facilitate migration operations. Since this is a planning course, you do not need to detail the configuration options of or demonstrate the ADC. Refer students to their compact discs for more information. Emphasize that identifying these types of information stores is an important part of planning the early phases of domain upgrade. „# Maintaining Network Performance During an UpgradeThe key to network performance during an upgrade is site implementation. Be prepared for questions from students that deviate from the topic. Handle their questions in a way that doesn’t distract from the main upgrade-related planning issues. (Students should have a full understanding of replication and topology design from prerequisite courses). Make sure students understand that the site topology is defined during the Active Directory design, prior to upgrade planning. The key during upgrade is implementing the sites in a timely manner to control replication and logon traffic. # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH##4# 2YHUYLHZ# „ 0DLQWDLQLQJ#1HWZRUN#6HUYLFHV#'XULQJ#DQ#8SJUDGH „ 0DLQWDLQLQJ#6HFXULW\#'XULQJ#DQ#8SJUDGH „ 'HWHUPLQLQJ#WKH#,PSDFW#RI#DQ#8SJUDGH#RQ#$SSOLFDWLRQV „ /HYHUDJLQJ#([LVWLQJ#'LUHFWRU\#,QIRUPDWLRQ „ 0DLQWDLQLQJ#1HWZRUN#3HUIRUPDQFH#'XULQJ#DQ#8SJUDGH One of your primary migration goals will be to ensure continuous network functionality with minimal impact on business productivity. Potential benefits of upgrading your existing Microsoft ® Windows NT ® 4.0 domains to Microsoft Windows ® 2000 include improved manageability, scalability, security, and availability. Achieving these benefits while maintaining network operations may introduce additional considerations to your basic upgrade plan. This module explores the effects of a domain upgrade on various components of a Windows NT 4.0 network and suggests planning steps and techniques to reduce or eliminate interruptions during the upgrade. At the end of this module, you will be able to: „# Examine existing network services and develop a strategy for ensuring their reliability during an upgrade. „# Determine how a domain upgrade will modify existing security and develop a strategy for maintaining your desired security levels during the upgrade. „# Determine in advance how server applications will behave in a Windows 2000 environment. „# Describe how the Active Directory ™ Connector allows migration of user attributes to the Active Directory directory service. „# Develop a strategy for regulating traffic to optimize network performance during the upgrade. 6OLGH#2EMHFWLYH# 7R#SURYLGH#DQ#RYHUYLHZ#RI# WKH#PRGXOH#WRSLFV#DQG# REMHFWLYHV1# /HDG0LQ# ,Q#WKLV#PRGXOH/#\RX#ZLOO#OHDUQ# DERXW#PLQLPL]LQJ#WKH#LPSDFW# RI#D#GRPDLQ#XSJUDGH#RQ# \RXU#QHWZRUN#UHOLDELOLW\/# VHFXULW\/#DYDLODELOLW\/#DQG# SHUIRUPDQFH1# 'HOLYHU\#7LS# 7HOO#VWXGHQWV#WKDW#PRGXOH#6/# ³'HYHORSLQJ#D#'RPDLQ# 8SJUDGH#6WUDWHJ\/´#LQ# FRXUVH#5343$/#'HVLJQLQJ#D# 0LFURVRIW#:LQGRZV#5333# 0LJUDWLRQ#6WUDWHJ\/#FRQWDLQV# VWHSV#WKDW#DOO#RUJDQL]DWLRQV# PXVW#LQFOXGH#LQ#WKHLU# XSJUDGH#SODQV1#7KH#FXUUHQW# PRGXOH#ZLOO#FRYHU#DGGLWLRQDO# SODQQLQJ#VWHSV#WKDW#PD\#EH# UHTXLUHG#GHSHQGLQJ#RQ#WKH# FXUUHQW#QHWZRUN# HQYLURQPHQW1# 5# # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH# ‹‹ #0DLQWDLQLQJ#1HWZRUN#6HUYLFHV#'XULQJ#DQ#8SJUDGH# „ 3URYLGLQJ#5HOLDEOH#'16#6HUYLFHV „ 3URYLGLQJ#5HOLDEOH#1HW%,26#5HVROXWLRQ#6HUYLFHV „ 3URYLGLQJ#5HOLDEOH#'+&3#6HUYHU#6HUYLFHV „ 6XSSRUWLQJ#/$1#0DQDJHU#5HSOLFDWLRQ „ 6XSSRUWLQJ#5HPRWH#$FFHVV#6HUYLFHV „ 3ODQQLQJ#IRU#,QWHUDFWLRQ#%HWZHHQ#*URXS#3ROLF\#DQG# 6\VWHP#3ROLFLHV „ 0LJUDWLQJ#DQG#$SSO\LQJ#/RJRQ#6FULSWV For many network administrators, the biggest risk during a domain upgrade will be potential interruptions to network operations. Because an upgrade will affect numerous network services, careful planning is necessary to ensure a smooth transition. Important planning issues include: „# Examining how Domain Name System (DNS) data will be replicated in a Windows 2000 network so that you can provide reliable DNS naming services during the upgrade. „# Determining your current usage of NetBIOS names so that you can evaluate the possibility of removing the Windows Internet Name Service after the upgrade. „# Identifying normal interruptions to Dynamic Host Configuration Protocol (DHCP) Server services during the upgrade process so that you can maintain maximum reliability. „# Maintaining NTLM protocol replication functionality after Windows 2000 File Replication service (FRS) is implemented. „# Developing a strategy for planning Routing and Remote Access support during the upgrade process. „# Developing a strategy for transitioning from Windows NT 4.0 System Policies to Windows 2000 Group Policy. „# Developing a strategy for transitioning from Windows NT 4.0 logon scripts to Windows 2000 Group Policy. 6OLGH#2EMHFWLYH# 7R#GHVLJQ#D#VWUDWHJ\#IRU# PDLQWDLQLQJ#UHOLDEOH#QHWZRUN# VHUYLFHV#GXULQJ#D#GRPDLQ# XSJUDGH1# /HDG0LQ# $#GRPDLQ#XSJUDGH#ZLOO#DIIHFW# VHYHUDO#QHWZRUN#VHUYLFHV1# &DUHIXO#SODQQLQJ#LV#UHTXLUHG# WR#PDLQWDLQ#UHOLDEOH#QHWZRUN# FRQQHFWLYLW\1# 'HOLYHU\#7LS# 8VH#WKH#VOLGH#WR#SRLQW#RXW# HDFK#VHUYLFH#WKDW#ZLOO#EH# GLVFXVVHG#LQ#WKLV#VHFWLRQ1# # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH##6# 3URYLGLQJ#5HOLDEOH#'16#6HUYLFHV# „ (IIHFW#RI#DQ#8SJUDGH#RQ#'16#6HUYLFHV z =RQHV#FDQ#EH#FRQILJXUHG#WR#DFFHSW#659#UHVRXUFH#UHFRUG# UHJLVWUDWLRQV z 5HVRXUFH#UHFRUGV#FDQ#EH#G\QDPLFDOO\#XSGDWHG „ 8SJUDGLQJ#'16#6HUYHUV „ '16#8SJUDGH#&RQVLGHUDWLRQV z :LQGRZV#5333#'16#DQG#:LQGRZV#17#713#'16#PXVW#EH# PDQDJHG#ZLWK#WKHLU#RZQ#'16#PDQDJHPHQW#WRROV z $FWLYH#'LUHFWRU\0LQWHJUDWHG#]RQHV#FDQQRW#EH#UHSOLFDWHG# EHWZHHQ#GRPDLQV z :LQGRZV#5333#'16#VHUYHUV#FDQ#EH #PDVWHU#VHUYHUV#IRU# :LQGRZV#17#713#'16#VHUYHUV Windows 2000 depends on DNS as a locator service for its clients to find important Windows 2000 services. During an upgrade to Windows 2000, it is essential to migrate the Windows NT 4.0 DNS service to Windows 2000 as quickly as possible to provide the required support for SRV resource records. These are used to locate network servers hosting Lightweight Directory Access Protocol (LDAP) or Kerberos authentication. 7KH#(IIHFW#RI#DQ#8SJUDGH#RQ#'16#6HUYLFHV# Upgrading the primary DNS server to Windows 2000, or switching the primary zone to be hosted on a Windows 2000 server, gains the immediate benefit of enabling the configuration of zones to accept SRV resource record registrations and dynamic updates of resource records. DNS zones hosted on a Windows 2000 domain controller can also be configured as Active Directory Integrated. 8SJUDGLQJ#'16#6HUYHUV# Your upgrade plan must include upgrading any Windows NT 4.0 DNS services to Windows 2000 DNS services and moving the writable copy of the DNS zone data to Windows 2000. You can do this in one of two ways: „# Upgrade the existing Windows NT 4.0 server containing the DNS primary zone to Windows 2000 and then configure the zone to allow dynamic updates. If the primary zone is stored on a primary domain controller (PDC), the Active Directory Installation wizard will start after the upgrade is completed. You can configure the zones to allow updates before the wizard is completed. 6OLGH#2EMHFWLYH# 7R#GHWHUPLQH#D#VWUDWHJ\#IRU# SURYLGLQJ#UHOLDEOH#'16# VHUYLFHV#GXULQJ#D#GRPDLQ# XSJUDGH1# /HDG0LQ# 3ULRU#WR#SURPRWLQJ#WKH#ILUVW# GRPDLQ#FRQWUROOHU#LQ#WKH#ILUVW# GRPDLQ/#'16#VHUYLFHV#PXVW# EH#LQVWDOOHG#WKDW#VXSSRUW# 659#UHFRUGV1# 'HOLYHU\#7LS# 5HPLQG#VWXGHQWV#WKDW#$FWLYH# 'LUHFWRU\#LQWHJUDWHG#]RQHV# FDQ#RQO\#EH#LPSOHPHQWHG#RQ# GRPDLQ#FRQWUROOHUV1#,I#'16#LV# LQVWDOOHG#RQ#D#PHPEHU# VHUYHU/#LW#FDQ#RQO\#EH#D# SULPDU\#RU#VHFRQGDU\#'16# VHUYHU1# # (PSKDVL]H#WKDW#$FWLYH# 'LUHFWRU\#LQWHJUDWHG#]RQHV# DUH#UHFRPPHQGHG#IRU#DQ\# '16#GRPDLQV#WKDW#ZLOO# FRQWDLQ#$FWLYH#'LUHFWRU\± UHODWHG#UHVRXUFH#UHFRUGV1# # .H\#3RLQWV# ,I#DW#OHDVW#RQH#'16#VHUYHU#LV# QRW#XSJUDGHG#WR#:LQGRZV# 5333/#659#UHFRUGV#UHTXLUHG# E\#$FWLYH#'LUHFWRU\#PXVW#EH# PDQXDOO\#DGGHG1# 7LS# 7# # 0RGXOH#7=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN#2SHUDWLRQV#'XULQJ#DQ#8SJUDGH# „# Install a new Windows 2000 server and configure it as the secondary DNS server for the existing zone. After the zone transfer has taken place, reverse the roles so that the Windows 2000 DNS server is the primary DNS server for the zone. The zone can then be configured to allow dynamic updates. After a domain controller with the DNS service is upgraded to Windows 2000, convert the DNS zone to Active Directory Integrated to take advantage of secure dynamic updates and multi-master writes. If you do not upgrade the Windows NT 4.0 DNS service to Windows 2000 on at least one DNS server, you must manually add all Windows 2000–related SRV resource records to the zone text file at the primary DNS server. In the Windows NT 4.0 DNS Manager, SRV records will appear as generic resource records in the interface; however, queries to a Windows NT 4.0 DNS server for SRV resource records will succeed. '16#8SJUDGH#&RQVLGHUDWLRQV# To minimize the impact of your domain upgrade on DNS services, consider the following: „# Windows 2000 DNS and Windows NT 4.0 DNS must be managed with their own DNS management tools. Windows NT 4.0 DNS cannot be managed with the Windows 2000 DNS management tool, and vice versa. Similarly, the Windows NT 4.0 DNS tool cannot be run on a Windows 2000 Server, and vice versa. „# Active Directory-integrated zones cannot be replicated between domains. If you require zones to be hosted on DNS servers in different domains, you will need to configure DNS servers in domains other than the local domain to be secondary DNS zones. „# Windows 2000 DNS servers can be master servers for Windows NT 4.0 DNS servers. Likewise, Windows NT 4.0 DNS servers can be master servers for Windows 2000 DNS servers. 7LS# 1RWH# [...]... result in the availability of multiple methods of authentication In addition to LAN Manager and NTLM authentication, Windows 2000 authentication is available in upgraded domains 1HWZRUN#6HUYLFHV#8VHG#IRU#$XWKHQWLFDWLRQ# The key to optimizing the network for Windows 2000 authentication is to understand what network services are used during the authentication process By locating these services on the network. .. define the following steps to integrate the LAN Manager replication service and FRS: „# Identify all Windows NT 4.0 export and import servers If the export server is the PDC, move the export services to another computer This allows the PDC to be upgraded and allows LAN Manager replication to continue to replicate scripts and policies for the non-upgraded backup domain controllers (BDCs) remaining in the. .. can be configured to periodically run the lbridge.cmd script An interval of two hours is commonly configured „# Reconfigure the LAN Manager replication service as the upgrade proceeds As you upgrade each import server to Windows 2000, remove the upgraded server from the list of servers to which the export server replicates „# Decommission the bridge between the replication systems The LAN Manager replication... a domain controller is upgraded to Windows 2000, user-based logon scripts stored in the NETLOGON share are unaffected and will continue to be available when clients authenticate The FRS synchronizes the contents of this folder with all Windows 2000 domain controllers To synchronize the contents of this folder with domain controllers in the domain not yet upgraded, the LAN Manager replication service... Server uses the LAN Manager replication service to replicate logon scripts, System Policies, and other data Windows 2000 does not support LAN Manager replication service but offers the same functionality through FRS LAN Manager replication service and FRS are distinct services with different configurations With LAN Manager replication service, a single server (usually a domain controller) hosts an export... Your upgrade plan should include steps to apply these templates to upgraded servers, to take advantage of new security features and maintain consistency between upgraded and newly installed servers 2SWLPL]LQJ#'RPDLQ#6HFXULW\#DQG#(QVXULQJ#&RQVLVWHQF\# If any of the computers in the network have new installations of Windows 2000 on them, they will have a higher default security configuration than the upgraded... domain controllers can host the SYSVOL 7KH#(IIHFW#RI#DQ#8SJUDGH#RQ#5HSOLFDWLRQ#6HUYLFHV# A non-upgraded export server will continue to replicate the contents of its export directories to non-upgraded import servers As Windows NT 0 domain controllers are upgraded, the LAN Manager replication service is removed When the last Windows NT computer is upgraded to Windows 2000, the LAN Manager replication service... domain, and the computer account in another, additional factors need to be considered 1RWH# Group Policies are only applied to Windows 2000 clients They are not applied to Windows NT 4.0 clients at any time For more information on policy behavior in a mixed environment, see Chapter 23, “Defining Client Administration and Configuration Standards”, in the Windows 2000 Server Deployment Planning Guide on the. .. directory, and a number of domain controllers or member servers import the contents of the export directory to an import folder stored on the server FRS automatically configures every domain controller to host a replicated System Volume (SYSVOL) Changes made to the contents of the SYSVOL at any domain controller are replicated in multiplemaster fashion to all other domain controllers in the domain Only domain... logon scripts and System Policies, regardless of the version of the operating system running on the authenticating domain controller Integrating the two services will also ensure that updates made to these files are propagated to all domain controllers in the domain To reliably provide logon scripts and System Policies to clients in a domain that is being upgraded, it is important that an upgrade plan . &RQWHQWV## # 2YHUYLHZ#4 # 0DLQWDLQLQJ#1HWZRUN#6HUYLFHV## 'XULQJ#DQ#8SJUDGH#5 # 0DLQWDLQLQJ#6HFXULW#'XULQJ#DQ#8SJUDGH#49 # 'HWHUPLQLQJ#WKH#,PSDFW#RI#DQ## 8SJUDGH#RQ#$SSOLFDWLRQV#57 # /HYHUDJLQJ#([LVWLQJ#'LUHFWRU#,QIRUPDWLRQ#58 # 0DLQWDLQLQJ#1HWZRUN#3HUIRUPDQFH## 'XULQJ#DQ#8SJUDGH#5: # /DE#$=#0LQLPL]LQJ#WKH#,PSDFW#RQ#1HWZRUN## 2SHUDWLRQV#'XULQJ#DQ#8SJUDGH#64 # 5HYLHZ#74 # # Module 4: Minimizing the Impact on Network Operations During an Upgrade # Information in this document is subject to change without notice. The. implementation, and security templates. „# Determining the Impact of an Upgrade on Applications The only way to determine the impact that an upgrade will have on an

Ngày đăng: 18/01/2014, 05:20

TỪ KHÓA LIÊN QUAN