Donnie Hamlett Technology Specialist Microsoft Corporation

DownloadDonnie Hamlett Technology Specialist Microsoft Corporation

Advertisement
Download Presentation
Comments
oma
From:
|  
(215) |   (0) |   (0)
Views: 73 | Added: 20-02-2012
Rate Presentation: 0 0
Description:
Agenda. OverviewDirectory Synchronization ServicesMicrosoft File Migration UtilityFile and Print Services for NetWareOther Interoperability ServicesSummary. Services for NetWare Overview. Synchronizes AD with NDS Reduces directory management Simplifies adoption of Windows 2000. Migrates NetWare files to Windows 2000Accelerates migration processesPreserves access control information.
Donnie Hamlett Technology Specialist Microsoft Corporation

An Image/Link below is provided (as is) to

Download Policy: Content on the Website is provided to you AS IS for your information and personal use only and may not be sold or licensed nor shared on other sites. SlideServe reserves the right to change this policy at anytime. While downloading, If for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.











- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -




1. Introduction Today we are going to discuss how Services for NetWare v.5 addresses your key NetWare and Windows 2000 interoperability issues. Services for NetWare, provides a set of synchronization and migration utilities that help simplify the introduction of Windows 2000 Server and its Active Directory service into a NetWare/NDS network environment In today?s agenda we?ll cover: Agenda Overview of What is Services for NetWare? Directory Synchronization Services File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary of SFN5 Benefits However, before we dive in I want to make one point clear: Services for Netware 5.0 refers to the version of Services for NetWare not for the Novell NetWare 5.0 NOS. Specifically, Services for NetWare 5.0 is not only for NetWare 5.0 but all versions of NetWare and NDS.Introduction Today we are going to discuss how Services for NetWare v.5 addresses your key NetWare and Windows 2000 interoperability issues. Services for NetWare, provides a set of synchronization and migration utilities that help simplify the introduction of Windows 2000 Server and its Active Directory service into a NetWare/NDS network environment In today?s agenda we?ll cover: Agenda Overview of What is Services for NetWare? Directory Synchronization Services File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary of SFN5 Benefits However, before we dive in I want to make one point clear: Services for Netware 5.0 refers to the version of Services for NetWare not for the Novell NetWare 5.0 NOS. Specifically, Services for NetWare 5.0 is not only for NetWare 5.0 but all versions of NetWare and NDS.

2. Agenda Overview Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary We?ll begin with an overview of Services for NetWare 5We?ll begin with an overview of Services for NetWare 5

3. Services for NetWare Overview Slide Objective: Services for NetWare includes three new major tools to simplify the adoption of Windows 2000 Server, reduce overall network administration, and facilitate the migration to Windows 2000 Server from NetWare. [Advance Slide Build] Services for NetWare includes three new major tools to simplify the adoption of Windows 2000 Server, reduce overall network administration, and facilitate the migration to Windows 2000 Server from NetWare. They include Microsoft Directory Synchronization Services (or MSDSS), Microsoft File Migration Utility (or FileMigrate), and File and Print Services for NetWare Microsoft Directory Synchronization Services: The administration of multiple directory services often leads to time-consuming and redundant management. For organizations that already have NDS deployed somewhere in their IT environment and are looking at large or small deployments of Windows 2000 Server, MSDSS helps customers reduce their directory management burden while also facilitating the adoption of Windows 2000 Server and its Active Directory service. MSDSS achieves does this by synchronizing the Active Directory and NDS with each other. By establishing a periodic synchronization of both directories, customers can reduce time expended on directory management. MSDSS makes synchronization and even Active Directory set-up easy through its management interface and is fully-featured to allow customers a choice of management, synchronization, and migration options. [Advance Slide Build] Microsoft File Migration Utility: For customers that have selected Windows 2000 Server as their strategic direction, FileMigrate simplifies and accelerates the migration of files stored on NetWare servers to Windows 2000 Server. Customers can choose to migrate at their own pace and ensure that the file permissions unique to each file are preserved during the migration process. [Advance Slide Build] File and Print Services for NetWare 5: Many companies who are using NetWare to perform file and print services are considering consolidating their file and print servers to a single platform, but have built up an investment in NetWare file and print server administration skills that they would like to leverage. File and Print Services of NetWare helps customers preserve their NetWare skill set while consolidating their file and print servers to Windows 2000 Server by making their Windows 2000 Server ?look? like a NetWare file and print server to administrators, users and clients. As a result companies reduce the costs of re-training, while consolidating their file and print servers on a single platform and simplifying overall administration.Slide Objective: Services for NetWare includes three new major tools to simplify the adoption of Windows 2000 Server, reduce overall network administration, and facilitate the migration to Windows 2000 Server from NetWare. [Advance Slide Build] Services for NetWare includes three new major tools to simplify the adoption of Windows 2000 Server, reduce overall network administration, and facilitate the migration to Windows 2000 Server from NetWare. They include Microsoft Directory Synchronization Services (or MSDSS), Microsoft File Migration Utility (or FileMigrate), and File and Print Services for NetWare Microsoft Directory Synchronization Services: The administration of multiple directory services often leads to time-consuming and redundant management. For organizations that already have NDS deployed somewhere in their IT environment and are looking at large or small deployments of Windows 2000 Server, MSDSS helps customers reduce their directory management burden while also facilitating the adoption of Windows 2000 Server and its Active Directory service. MSDSS achieves does this by synchronizing the Active Directory and NDS with each other. By establishing a periodic synchronization of both directories, customers can reduce time expended on directory management. MSDSS makes synchronization and even Active Directory set-up easy through its management interface and is fully-featured to allow customers a choice of management, synchronization, and migration options. [Advance Slide Build] Microsoft File Migration Utility: For customers that have selected Windows 2000 Server as their strategic direction, FileMigrate simplifies and accelerates the migration of files stored on NetWare servers to Windows 2000 Server. Customers can choose to migrate at their own pace and ensure that the file permissions unique to each file are preserved during the migration process. [Advance Slide Build] File and Print Services for NetWare 5: Many companies who are using NetWare to perform file and print services are considering consolidating their file and print servers to a single platform, but have built up an investment in NetWare file and print server administration skills that they would like to leverage. File and Print Services of NetWare helps customers preserve their NetWare skill set while consolidating their file and print servers to Windows 2000 Server by making their Windows 2000 Server ?look? like a NetWare file and print server to administrators, users and clients. As a result companies reduce the costs of re-training, while consolidating their file and print servers on a single platform and simplifying overall administration.

4. Agenda Overview Microsoft Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary So let?s drill into each of these interoperability utilities in a little more detail starting with the Microsoft Directory Synchronization Service.So let?s drill into each of these interoperability utilities in a little more detail starting with the Microsoft Directory Synchronization Service.

5. Microsoft Directory Synchronization Services Overview Microsoft Directory Synchronization Services (MSDSS) synchronizes data between Active Directory and Novell Directory Services (NDS): Reduces Directory Management Simplifies Windows 2000 Server Adoption Easy to Deploy and Use Slide Objective: In order to reduce directory management costs in a mixed AD and NDS environment a directory synchronization service must include essential synchronization services. MSDSS delivers this functionality. Microsoft Directory Synchronization Services is a powerful utility that synchronizes directory information stored in the Windows 2000 Active Directory directory service with Novell?s Directory Services. Through the synchronization of AD and NDS customers can: Reduce Directory Management by administering one, rather than two directories. Simplify the Introduction and adoption of Windows 2000 Server into their NetWare environment Finally, MSDSS is easy to Deploy and use in large or small deployments. Presenter?s Note: The main point here is that MSDSS provides a full-featured synchronization service that reduces directory management, simplifies the introduction of Windows 2000 Server in a NetWare environment and is easy to use and deploy. See benefits slide and their drilldown for additional information.Slide Objective: In order to reduce directory management costs in a mixed AD and NDS environment a directory synchronization service must include essential synchronization services. MSDSS delivers this functionality. Microsoft Directory Synchronization Services is a powerful utility that synchronizes directory information stored in the Windows 2000 Active Directory directory service with Novell?s Directory Services. Through the synchronization of AD and NDS customers can: Reduce Directory Management by administering one, rather than two directories. Simplify the Introduction and adoption of Windows 2000 Server into their NetWare environment Finally, MSDSS is easy to Deploy and use in large or small deployments. Presenter?s Note: The main point here is that MSDSS provides a full-featured synchronization service that reduces directory management, simplifies the introduction of Windows 2000 Server in a NetWare environment and is easy to use and deploy. See benefits slide and their drilldown for additional information.

6. MSDSS Technical Concepts MSDSS is a new and unique way to synchronize AD and NDS As such there are several new synchronization concepts that I?d like to first introduce [Advance Slide Build] Sessions: The first concept to understand are ?sessions?. A session is simply the discrete process of synchronizing NDS and AD at a given time. To keep two directories in sync, sessions are started on a manual or periodic basis. Once begun, a session queries each directory for changes, collects those changes, and then publishes the changes to the other directory resulting in both directories having the same information. [Advance Slide Build] Object-Level Synchronization: The second major concept is object-level synchronization. During a session only the changes made in objects are synchronized, not the entire containers objects they are stored in. This lowers synchronization traffic across the network and allows objects to be organized in each directory any way a customers wants and tracks objects as they move. [Advance Slide Build] 1 vs. 2-way Synchronization: The third major concept is 1 and 2-way synchronization. MSDSS was designed to let customers select how they want information synchronized. In 1-way synchronization, only changes made in AD are synchronized with NDS: NDS changes are not synchronized with AD. In 2-way synchronization, changes made in either AD or NDS are synchronized with the other. Now lets explore these concepts in a little more detail.MSDSS is a new and unique way to synchronize AD and NDS As such there are several new synchronization concepts that I?d like to first introduce [Advance Slide Build] Sessions: The first concept to understand are ?sessions?. A session is simply the discrete process of synchronizing NDS and AD at a given time. To keep two directories in sync, sessions are started on a manual or periodic basis. Once begun, a session queries each directory for changes, collects those changes, and then publishes the changes to the other directory resulting in both directories having the same information. [Advance Slide Build] Object-Level Synchronization: The second major concept is object-level synchronization. During a session only the changes made in objects are synchronized, not the entire containers objects they are stored in. This lowers synchronization traffic across the network and allows objects to be organized in each directory any way a customers wants and tracks objects as they move. [Advance Slide Build] 1 vs. 2-way Synchronization: The third major concept is 1 and 2-way synchronization. MSDSS was designed to let customers select how they want information synchronized. In 1-way synchronization, only changes made in AD are synchronized with NDS: NDS changes are not synchronized with AD. In 2-way synchronization, changes made in either AD or NDS are synchronized with the other. Now lets explore these concepts in a little more detail.

7. Session-Based Synchronization MSDSS synchronizes changes between Active Directory and NDS Each session synchronizes a subtree; multiple subtrees supported Sessions can run on a manual or periodic basis Slide Objective: Sessions are mechanism by which directory information gets synchronized between an OU in AD and an OU in NDS One way to think about what MSDSS does is to view it as a bridge, or a connector, between information stored in Active Directory and information stored in NDS. And just like a bridge, information can flow two ways from AD to NDS and from NDS to AD. As such, MSDSS is the enabling technology that links AD and NDS and allows for centralized cross-directory management. As this slide illustrates at a high level, each session queries for the changes that occur in each directory, collects those changes and then publishes those changes back out to each directory keeping the information stored in each directory synchronized. A session only occurs for a pair of OUs, or a sub tree, in AD and NDS. Since many organizations have multiple OUs, a session needs to be configured for each OU pair that exists. MSDSS supports up to 128 simultaneous synchronization sessions. Organizations with more than 128 sessions need to bring up another MSDSS server (on a Windows 2000 domain controller). In order to make sure changes in an OU of one directory are reflected accurately in the OU of the other directory, MSDSS has a map (that must be initially configured) that relates an object (and its properties) in one directory to its equivalent in another directory. To ensure that conflicts are resolved (such as a user phone number is changed in both AD and NDS in between sessions) a series of rules are applied so that only one value is synchronized. To ensure that synchronized information is transferred and stored securely, the information is stored in Active Directory. Finally, each individual session, is monitored to note the administrator of failures, errors, and status in order to troubleshoot anf monitoring ongoing synchronization. Presenter?s Note: This slide is a concept slide, for more detailed information on synchronization architecture and examples of typical synchronization tasks please refer to the MSDSS Technical Seminar deck.Slide Objective: Sessions are mechanism by which directory information gets synchronized between an OU in AD and an OU in NDS One way to think about what MSDSS does is to view it as a bridge, or a connector, between information stored in Active Directory and information stored in NDS. And just like a bridge, information can flow two ways from AD to NDS and from NDS to AD. As such, MSDSS is the enabling technology that links AD and NDS and allows for centralized cross-directory management. As this slide illustrates at a high level, each session queries for the changes that occur in each directory, collects those changes and then publishes those changes back out to each directory keeping the information stored in each directory synchronized. A session only occurs for a pair of OUs, or a sub tree, in AD and NDS. Since many organizations have multiple OUs, a session needs to be configured for each OU pair that exists. MSDSS supports up to 128 simultaneous synchronization sessions. Organizations with more than 128 sessions need to bring up another MSDSS server (on a Windows 2000 domain controller). In order to make sure changes in an OU of one directory are reflected accurately in the OU of the other directory, MSDSS has a map (that must be initially configured) that relates an object (and its properties) in one directory to its equivalent in another directory. To ensure that conflicts are resolved (such as a user phone number is changed in both AD and NDS in between sessions) a series of rules are applied so that only one value is synchronized. To ensure that synchronized information is transferred and stored securely, the information is stored in Active Directory. Finally, each individual session, is monitored to note the administrator of failures, errors, and status in order to troubleshoot anf monitoring ongoing synchronization. Presenter?s Note: This slide is a concept slide, for more detailed information on synchronization architecture and examples of typical synchronization tasks please refer to the MSDSS Technical Seminar deck.

8. Object-Level Synchronization MSDSS supports situations where Active Directory and NDS have different tree structures MSDSS tracks objects as they change position in the tree from move and prune & graft operations Slide Objective: Illustrate that AD and NDS can maintain separate directory structures while keeping object information stored in each synchronized through 2-way synchronization. As I mentioned, directory information is synchronized at the object-level, not the entire containers that objects are stored in. This lowers synchronization traffic across the network and allows objects to be organized any way a customers wants. This slide illustrates an object-level synchronization benefit where the same objects (in this case users) can be organized in two completely different ways in Active Directory and NDS. For example in Active Directory, User 1 exists as a user object in the Accounting container of the Users OU. However, User 1 can also exist in NDS as a user object in the Chicago container of the User OU. Theses OU s need not have been named the same for synchronization to work. Through two-way synchronization, a local NDS administrator in Chicago can update that user?s personal information like a phone number, While the AD administrator in the accounting team at corporate can define which accounting applications and tools User 1 has access rights to. Through policies that can be implemented in AD, an organization can also restrict the rights of an administrator of one directory from modifying the objects ?owned? by another directory. For example by creating an ?AD admins? and an ?NDS admins? group. This is an example of shared or delegated administration. Another permutation of this slide under 1-way synchronization would allow the AD administrator the right to change all attributes of User 1 and have those changes propagated to NDS to provide centralized directory administration while still allowing both directories to have separate and unique structures. Slide Objective: Illustrate that AD and NDS can maintain separate directory structures while keeping object information stored in each synchronized through 2-way synchronization. As I mentioned, directory information is synchronized at the object-level, not the entire containers that objects are stored in. This lowers synchronization traffic across the network and allows objects to be organized any way a customers wants. This slide illustrates an object-level synchronization benefit where the same objects (in this case users) can be organized in two completely different ways in Active Directory and NDS. For example in Active Directory, User 1 exists as a user object in the Accounting container of the Users OU. However, User 1 can also exist in NDS as a user object in the Chicago container of the User OU. Theses OU s need not have been named the same for synchronization to work. Through two-way synchronization, a local NDS administrator in Chicago can update that user?s personal information like a phone number, While the AD administrator in the accounting team at corporate can define which accounting applications and tools User 1 has access rights to. Through policies that can be implemented in AD, an organization can also restrict the rights of an administrator of one directory from modifying the objects ?owned? by another directory. For example by creating an ?AD admins? and an ?NDS admins? group. This is an example of shared or delegated administration. Another permutation of this slide under 1-way synchronization would allow the AD administrator the right to change all attributes of User 1 and have those changes propagated to NDS to provide centralized directory administration while still allowing both directories to have separate and unique structures.

9. 1-Way & 2-Way Support MSDSS supports 1-way and 2-way synchronization Slide Objective: Describe the differences between 1-way and 2-way synchronization configurations. MSDSS is a flexible synchronization service that supports two different synchronization configurations depending on the requirements of the customer: 1 and 2-way synchronization 1-way Synchronization describes a synchronization process that pushes changes made in Active Directory to NDS, but does not read changes made in NDS. AD to NDS synchronization flow is called forward synchronization. 1-way sync should be used when a customer wants to centralize directory administration in Active Directory. In this configuration NDS users, groups, OUs, and containers can be managed and changed from Active Directory. However, because of the single-point of administration benefits this offers, it also means that object changes made in NDS are not synchronized in Active Directory. 1-way sync should be considered when a single directory management platform is desirable or if the long-term strategy of an organization is migration to AD. 2-way Synchronization describes a synchronization process which reads changes made in both AD and NDS and synchronizes those changes in each directory and therefore performs both a forward and a reverse synchronization. Just like AD to NDS synchronization is called forward synchronization, NDS to AD synchronization flow is called reverse synchronization. Consequently, changes can be made in either directory, read by MSDSS, and then pushed out to the unupdated directory. 2-way sync should be used in network environments where there is a strong need to manage both directories separately and have the information that is changed in one reflected in the other. The downside to this approach is that the full benefits of centralized directory administration are not realized, since two directories, rather than only a single directory, are being actively administered. 2-way sync should be considered when a single directory platform is undesirable or if the long-term strategy of an organization is co-existence or incremental migration to AD. In summary, the decision to synchronize 1-way or 2-way is up to the customer and depends on their requirements. It is always feasible to change a session from 2-way to 1-way, for example.Slide Objective: Describe the differences between 1-way and 2-way synchronization configurations. MSDSS is a flexible synchronization service that supports two different synchronization configurations depending on the requirements of the customer: 1 and 2-way synchronization 1-way Synchronization describes a synchronization process that pushes changes made in Active Directory to NDS, but does not read changes made in NDS. AD to NDS synchronization flow is called forward synchronization. 1-way sync should be used when a customer wants to centralize directory administration in Active Directory. In this configuration NDS users, groups, OUs, and containers can be managed and changed from Active Directory. However, because of the single-point of administration benefits this offers, it also means that object changes made in NDS are not synchronized in Active Directory. 1-way sync should be considered when a single directory management platform is desirable or if the long-term strategy of an organization is migration to AD. 2-way Synchronization describes a synchronization process which reads changes made in both AD and NDS and synchronizes those changes in each directory and therefore performs both a forward and a reverse synchronization. Just like AD to NDS synchronization is called forward synchronization, NDS to AD synchronization flow is called reverse synchronization. Consequently, changes can be made in either directory, read by MSDSS, and then pushed out to the unupdated directory. 2-way sync should be used in network environments where there is a strong need to manage both directories separately and have the information that is changed in one reflected in the other. The downside to this approach is that the full benefits of centralized directory administration are not realized, since two directories, rather than only a single directory, are being actively administered. 2-way sync should be considered when a single directory platform is undesirable or if the long-term strategy of an organization is co-existence or incremental migration to AD. In summary, the decision to synchronize 1-way or 2-way is up to the customer and depends on their requirements. It is always feasible to change a session from 2-way to 1-way, for example.

10. MSDSS Benefits Slide Objective: MSDSS substantially reduces multi-directory management, is easy to deploy and use, and is full featured to provide both a comprehensive and flexible multi-directory synchronization solution. MSDSS provides multiple benefits to organizations who want to reduce directory management, simplify the introduction of Windows 2000 Server into their NetWare environments, and easily deploy and use synchronization services to achieve these ends. [Advance Slide Build] Reduces Directory Management: By synchronizing information stored in one directory with another, customers can significantly reduce the time and cost spent on directory management and administration by: Providing a single point of administration of both AD and NDS in one directory, Keeping information changed in one directory updated with the other directory, preserving data integrity Synchronizing a variety of the most common object types and changes Synchronizing passwords so that a user can use the same password to log-in to each directory. [Advance Slide Build] Simplifies Windows 2000 Adoption: MSDSS is also a very useful tool in simplifying the adoption of Windows 2000 Server into a NetWare environment since it: Preserves existing investments of time into structuring NDS, including reverse initial synchronization (that populates AD with NDS objects) Allows for unique AD and NDS tree structures, Supports multiple NDS/bindery versions and Provides a migration feature which greatly simplified NDS to AD migrations. [Advance Slide Build] Easy to Use and Deploy: MSDSS also makes the deployment and use of Active Directory in a mixed NDS environment easier with: Easy to set-up and configure sessions through GUIs and wizards, A central console to centralize and monitor sync administration Configurable synchronization timing support and Integrated security Let?s explore some of the features that enable each of these high-level benefits in more detailSlide Objective: MSDSS substantially reduces multi-directory management, is easy to deploy and use, and is full featured to provide both a comprehensive and flexible multi-directory synchronization solution. MSDSS provides multiple benefits to organizations who want to reduce directory management, simplify the introduction of Windows 2000 Server into their NetWare environments, and easily deploy and use synchronization services to achieve these ends. [Advance Slide Build] Reduces Directory Management: By synchronizing information stored in one directory with another, customers can significantly reduce the time and cost spent on directory management and administration by: Providing a single point of administration of both AD and NDS in one directory, Keeping information changed in one directory updated with the other directory, preserving data integrity Synchronizing a variety of the most common object types and changes Synchronizing passwords so that a user can use the same password to log-in to each directory. [Advance Slide Build] Simplifies Windows 2000 Adoption: MSDSS is also a very useful tool in simplifying the adoption of Windows 2000 Server into a NetWare environment since it: Preserves existing investments of time into structuring NDS, including reverse initial synchronization (that populates AD with NDS objects) Allows for unique AD and NDS tree structures, Supports multiple NDS/bindery versions and Provides a migration feature which greatly simplified NDS to AD migrations. [Advance Slide Build] Easy to Use and Deploy: MSDSS also makes the deployment and use of Active Directory in a mixed NDS environment easier with: Easy to set-up and configure sessions through GUIs and wizards, A central console to centralize and monitor sync administration Configurable synchronization timing support and Integrated security Let?s explore some of the features that enable each of these high-level benefits in more detail

11. Reduces Directory Management Provides a single point of administration Centralized directory management 1-way (AD to NDS) synchronization Efficient network synchronization Preserves data integrity across directories Replicates a variety of object information Monitors sessions for consistency Synchronizes a variety of objects and changes Supports users, group, organizational units & containers objects with their attributes Captures add, delete, rename, move and modify operations Supports password synchronization Changes made in Active Directory can be ?pushed? to NDS Slide Objective: MSDSS reduces the burden of directory management in a number of ways. [Advance Slide Build] Single Point of Directory Administration: Perhaps the single largest benefit of MSDSS is the ability to manage both AD and NDS from a single directory. Through 1-way synchronization, changes made in Active Directory are propagated to NDS via synchronization. By enabling 1-way synchronization, organizations can manage both AD and NDS through Active Directory alone. This is a desirable configuration of MSDSS in customer scenarios who prefer to centralize directory administration in Active Directory and/or are sensitive to network traffic costs. Network traffic is reduced by having AD being the single point of directory administration since only the object attribute (or property) changes in Active Directory are synchronized rather than the whole object itself - resulting in lower overall network traffic. In contrast, 2-way synchronization requires full object (or all of the attributes) synchronization for NDS to AD synchronization ? although AD to NDS synchronization still occurs at the attribute level. [Advance Slide Build] Ensures Data Integrity Across Multiple Directories: Most companies have multiple directories that maintain the same information, like a user?s first and last name. However, these repositories of information generally lack easy ways to synchronize with other directories, and the information stored in them either has to be manually checked or synchronized to stay consistent or, more commonly, simply becomes increasingly inconsistent. MSDSS solves this problem for information stored and synchronized in AD and NDS (and those applications which are tied to them, like Exchange 2000 and AD for example). With 2-way synchronization, information changed in either directory is quickly and exactly replicated in the other directory keeping the data consistent on a near real-time basis. In addition, MSDSS provides monitoring and event log tools that inform an administrator when they don?t synchronize, so that data doesn?t drift out of sync. [Advance Slide Build] Synchronizes a Variety of Objects and Changes: MSDSS was designed to synchronize the most common kinds of changes for the most frequently changed objects. Generally, the objects most frequently altered are users, groups, OUs, containers and their associated attributes. MSDSS synchronizes a variety of changes to these objects such as adds, deletes, renames, moves and modifies. As a result MSDSS, reduces the time spent manually synchronizing or entering data into multiple directories every time an object changes. [Presenter?s Note: machines, devices, and security settings are not synchronized and still need to be performed through the interface of each directory, however these types of objects are the kind least likely to change]. [Advance Slide Build] Password Synchronization: A clear benefit to both users and administrators who have to either remember multiple passwords or reset those passwords when a user forgets them is the support for password synchronization included in MSDSS. By administering passwords centrally in AD those passwords are pushed to NDS resulting in a single password that users can use to access servers managed by AD or NDS. [Presenter?s Note: 2-way password synchronization is not possible since NDS does not provide a way to query for passwords in NDS] In conclusion, MSDSS reduces directory management of AD and NDS by consolidating directory administration, preserving data integrity across directories, synchronizing a variety of objects and types of changes, and synchronizing passwords. Slide Objective: MSDSS reduces the burden of directory management in a number of ways. [Advance Slide Build] Single Point of Directory Administration: Perhaps the single largest benefit of MSDSS is the ability to manage both AD and NDS from a single directory. Through 1-way synchronization, changes made in Active Directory are propagated to NDS via synchronization. By enabling 1-way synchronization, organizations can manage both AD and NDS through Active Directory alone. This is a desirable configuration of MSDSS in customer scenarios who prefer to centralize directory administration in Active Directory and/or are sensitive to network traffic costs. Network traffic is reduced by having AD being the single point of directory administration since only the object attribute (or property) changes in Active Directory are synchronized rather than the whole object itself - resulting in lower overall network traffic. In contrast, 2-way synchronization requires full object (or all of the attributes) synchronization for NDS to AD synchronization ? although AD to NDS synchronization still occurs at the attribute level. [Advance Slide Build] Ensures Data Integrity Across Multiple Directories: Most companies have multiple directories that maintain the same information, like a user?s first and last name. However, these repositories of information generally lack easy ways to synchronize with other directories, and the information stored in them either has to be manually checked or synchronized to stay consistent or, more commonly, simply becomes increasingly inconsistent. MSDSS solves this problem for information stored and synchronized in AD and NDS (and those applications which are tied to them, like Exchange 2000 and AD for example). With 2-way synchronization, information changed in either directory is quickly and exactly replicated in the other directory keeping the data consistent on a near real-time basis. In addition, MSDSS provides monitoring and event log tools that inform an administrator when they don?t synchronize, so that data doesn?t drift out of sync. [Advance Slide Build] Synchronizes a Variety of Objects and Changes: MSDSS was designed to synchronize the most common kinds of changes for the most frequently changed objects. Generally, the objects most frequently altered are users, groups, OUs, containers and their associated attributes. MSDSS synchronizes a variety of changes to these objects such as adds, deletes, renames, moves and modifies. As a result MSDSS, reduces the time spent manually synchronizing or entering data into multiple directories every time an object changes. [Presenter?s Note: machines, devices, and security settings are not synchronized and still need to be performed through the interface of each directory, however these types of objects are the kind least likely to change]. [Advance Slide Build] Password Synchronization: A clear benefit to both users and administrators who have to either remember multiple passwords or reset those passwords when a user forgets them is the support for password synchronization included in MSDSS. By administering passwords centrally in AD those passwords are pushed to NDS resulting in a single password that users can use to access servers managed by AD or NDS. [Presenter?s Note: 2-way password synchronization is not possible since NDS does not provide a way to query for passwords in NDS] In conclusion, MSDSS reduces directory management of AD and NDS by consolidating directory administration, preserving data integrity across directories, synchronizing a variety of objects and types of changes, and synchronizing passwords.

12. Simplifies Windows 2000 Adoption Preserves investments in NDS Requires no changes in NDS/NetWare Synchronizes NDS schema extensions Imports existing NDS structure into Active Directory Supports different tree structures No need to reorganize tree structures Namespace and object mapping Supports multiple NDS/bindery Versions NDS 4.x, NDS 5.x, NDS 8 NetWare bindery 3.x Supports TCP/IP and IPX/SPX networking Simplifies NDS to AD migrations Full or incremental migrations Migration management interface wizard Slide Objective: MSDSS is a full-featured synchronization service that simplifies the introduction of Windows 2000 Server into a Novell network environment [Advance Slide Build] Preserves Existing NDS Directory Investments: In order to help customers preserve their existing investments in structuring NDS, MSDSS does not require changes in NDS or NetWare and synchronizes most NDS schema extensions for 1-way synchronization (2-way sync however, requires modification). In addition, MSDSS enables customers to replicate an existing NDS structure and import it into Active Directory saving AD set-up time and keeping an existing tree structure that may work for them. This is done via a process called ?reverse initial synchronization?. This is a full reverse sync and preserves NDS attributes and most NDS schema extensions (those that have equivalency in AD). Moreover it does not require any changes in NDS to perform. This is a quick way to retain and quickly use an existing NDS tree structure in AD whether the goal is co-existence of migration. [Advance Slide Build] Supports Different Tree Structures: Directory objects contain a variety of information that needs to be available across multiple directories, but the objects themselves should be able to be organized separately in each directory to meet customer organization requirements. MSDSS meets these requirements by providing full object-level support which means an object with a different namespace in each directory, can be synchronized by mapping the object class and attribute type to each other in a static mapping table stored within an individual session. In addition, since synchronization is rooted at the object-level, both AD and NDS can have completely different tree structures giving substantial flexibility to AD and NDS admins to structure their directory trees to reflect their organization?s requirements. [Advance Slide Build] Supports all NDS/bindery versions: Many Novell customers have a variety of network operating systems and directories present in their environments. MSDSS supports synchronization with all NDS versions including NDS 4, 5, and 8 (and other intermediate versions) as well as all versions of bindery present on NetWare 3.x servers. By providing synchronization services for all NetWare and NDS versions, MSDSS provides a method for Novell customers to synchronize their directory information regardless of the platform or version it resides on even in a mixed environment and with either TCP/IP or IPX/SPX present as the Core Network Protocol. [Presenter?s Note: NetWare bindery synchronization is only 1-way. 2-way support is not provided due to the limited information stored in binderies] [Advance Slide Build] Simplifies NDS to AD Migrations: In addition to synchronization, MSDSS also supports and uniquely simplifies the process of migrating an NDS directory to AD for those customers who want to reduce directory administration even more or have no compelling need to maintain multiple NOS directories. In fact, migration is actually a relatively simple task relative to synchronization, because once a 1-way or 2-way synchronization process is established and the information is synchronized all that is required is to turn off your NDS Servers using the migration management interface wizard included in MSDSS. Because migrations have other impacts on organizations, MSDSS fully supports incremental as well as full migrations and supports migration from all versions of NDS as well as NetWare 3.x binderies to Active Directory. [Presenter?s Note: customers will have to use other tools or manually migrate other information such as machine accounts, printer queues, ACLs, and files ? see MSFileMigrate for latter two] Slide Objective: MSDSS is a full-featured synchronization service that simplifies the introduction of Windows 2000 Server into a Novell network environment [Advance Slide Build] Preserves Existing NDS Directory Investments: In order to help customers preserve their existing investments in structuring NDS, MSDSS does not require changes in NDS or NetWare and synchronizes most NDS schema extensions for 1-way synchronization (2-way sync however, requires modification). In addition, MSDSS enables customers to replicate an existing NDS structure and import it into Active Directory saving AD set-up time and keeping an existing tree structure that may work for them. This is done via a process called ?reverse initial synchronization?. This is a full reverse sync and preserves NDS attributes and most NDS schema extensions (those that have equivalency in AD). Moreover it does not require any changes in NDS to perform. This is a quick way to retain and quickly use an existing NDS tree structure in AD whether the goal is co-existence of migration. [Advance Slide Build] Supports Different Tree Structures: Directory objects contain a variety of information that needs to be available across multiple directories, but the objects themselves should be able to be organized separately in each directory to meet customer organization requirements. MSDSS meets these requirements by providing full object-level support which means an object with a different namespace in each directory, can be synchronized by mapping the object class and attribute type to each other in a static mapping table stored within an individual session. In addition, since synchronization is rooted at the object-level, both AD and NDS can have completely different tree structures giving substantial flexibility to AD and NDS admins to structure their directory trees to reflect their organization?s requirements. [Advance Slide Build] Supports all NDS/bindery versions: Many Novell customers have a variety of network operating systems and directories present in their environments. MSDSS supports synchronization with all NDS versions including NDS 4, 5, and 8 (and other intermediate versions) as well as all versions of bindery present on NetWare 3.x servers. By providing synchronization services for all NetWare and NDS versions, MSDSS provides a method for Novell customers to synchronize their directory information regardless of the platform or version it resides on even in a mixed environment and with either TCP/IP or IPX/SPX present as the Core Network Protocol. [Presenter?s Note: NetWare bindery synchronization is only 1-way. 2-way support is not provided due to the limited information stored in binderies] [Advance Slide Build] Simplifies NDS to AD Migrations: In addition to synchronization, MSDSS also supports and uniquely simplifies the process of migrating an NDS directory to AD for those customers who want to reduce directory administration even more or have no compelling need to maintain multiple NOS directories. In fact, migration is actually a relatively simple task relative to synchronization, because once a 1-way or 2-way synchronization process is established and the information is synchronized all that is required is to turn off your NDS Servers using the migration management interface wizard included in MSDSS. Because migrations have other impacts on organizations, MSDSS fully supports incremental as well as full migrations and supports migration from all versions of NDS as well as NetWare 3.x binderies to Active Directory. [Presenter?s Note: customers will have to use other tools or manually migrate other information such as machine accounts, printer queues, ACLs, and files ? see MSFileMigrate for latter two]

13. Easy to Use and Deploy Easy to set-up and configure MMC snap-in and Wizard-based GUI ?Point and click? configuration Supports session ?cloning? Centralizes synchronization administration Centralized monitoring functions Granular view logs Up to 128 sessions per server Configurable scheduling Manual or scheduled Configurable intervals Forward and Reverse Sync Integrated security Configuration stored securely in Active Directory Integrated access restriction controls Slide Objective: MSDSS is easy to deploy and use in an existing NDS environment by providing simple ways to set-up synchronization, centrally administer synchronization, configure synchronization timing, and secure the information. [Advance Slide Build] Easy to Set-up and Configure: MSDSS is easy to set-up and configure. Only a single Windows 2000 Domain Controller is required to synchronize up to 128 simultaneous synchronization ?sessions?. Configuration is managed through a wizard-based UI installed as an MMC snap-in and includes simultaneous viewing of both NDS and AD trees to enable ?point and click? configuration and object to object mapping. In addition, a session ?cloning? feature is included that allow an administrator to rapidly clone and apply session configurations between one pair of OUs with other OU pairs, rapidly accelerating the set-up process. [Advance Slide Build] Centralizes Synchronization Administration: MSDSS is also easier to administer. MSDSS has built-in monitoring and status tools that provide a system monitor for performance analysis, a network monitor for traffic impact, advanced conflict resolution logic, a complete log of all synchronization sessions through an event viewer, and a granular view of failed operations that allow for simple diagnosis and troubleshooting of synchronization problems which may occur. Finally, MSDSS makes administration easy by supporting up to 128 simultaneous synchronization sessions allowing synchronization to occur frequently and to be managed centrally. [Advance Slide Build] Configurable Scheduling: Information stored in each directory should be synchronized as frequently or as automatically as required by a customer. MSDSS supports this requirement by allowing a customer to set the interval between synchronization sessions as well as allowing synchronization to proceed on a manual or on an automatic basis. Moreover, customers can define different synchronization periods for both forward and reverse synchronization in a 2-way sync mode. It is desirable to have different forward and reverse timing intervals since forward synchronization is at the attribute-level and reverse synchronization is at the object level with the implication that NDS to AD sync consumes substantially more bandwidth than AD to NDS sync. Integrated Security: Synchronizing directory information either over a LAN, WAN, or the Internet requires security. MSDSS provides this by securely storing synchronization configuration and directory information in the Active Directory service. Moreover, MSDSS includes access restriction controls so that only authorized administrators can set-up, administer or monitor synchronization sessions. This is done by the default ?MSDSS Admins? local security group In summary, MSDSS helps customers gain the powerful benefits of synchronization by providing easy to use tools to introduce AD into an existing NDS environment, set-up and configure synchronization, centralize administration of the ongoing synchronization process including timing intervals with the built-in security you expect. Slide Objective: MSDSS is easy to deploy and use in an existing NDS environment by providing simple ways to set-up synchronization, centrally administer synchronization, configure synchronization timing, and secure the information. [Advance Slide Build] Easy to Set-up and Configure: MSDSS is easy to set-up and configure. Only a single Windows 2000 Domain Controller is required to synchronize up to 128 simultaneous synchronization ?sessions?. Configuration is managed through a wizard-based UI installed as an MMC snap-in and includes simultaneous viewing of both NDS and AD trees to enable ?point and click? configuration and object to object mapping. In addition, a session ?cloning? feature is included that allow an administrator to rapidly clone and apply session configurations between one pair of OUs with other OU pairs, rapidly accelerating the set-up process. [Advance Slide Build] Centralizes Synchronization Administration: MSDSS is also easier to administer. MSDSS has built-in monitoring and status tools that provide a system monitor for performance analysis, a network monitor for traffic impact, advanced conflict resolution logic, a complete log of all synchronization sessions through an event viewer, and a granular view of failed operations that allow for simple diagnosis and troubleshooting of synchronization problems which may occur. Finally, MSDSS makes administration easy by supporting up to 128 simultaneous synchronization sessions allowing synchronization to occur frequently and to be managed centrally. [Advance Slide Build] Configurable Scheduling: Information stored in each directory should be synchronized as frequently or as automatically as required by a customer. MSDSS supports this requirement by allowing a customer to set the interval between synchronization sessions as well as allowing synchronization to proceed on a manual or on an automatic basis. Moreover, customers can define different synchronization periods for both forward and reverse synchronization in a 2-way sync mode. It is desirable to have different forward and reverse timing intervals since forward synchronization is at the attribute-level and reverse synchronization is at the object level with the implication that NDS to AD sync consumes substantially more bandwidth than AD to NDS sync. Integrated Security: Synchronizing directory information either over a LAN, WAN, or the Internet requires security. MSDSS provides this by securely storing synchronization configuration and directory information in the Active Directory service. Moreover, MSDSS includes access restriction controls so that only authorized administrators can set-up, administer or monitor synchronization sessions. This is done by the default ?MSDSS Admins? local security group In summary, MSDSS helps customers gain the powerful benefits of synchronization by providing easy to use tools to introduce AD into an existing NDS environment, set-up and configure synchronization, centralize administration of the ongoing synchronization process including timing intervals with the built-in security you expect.

14. Agenda Overview Microsoft Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary The next interoperability utility we?ll cover is the File Migration UtilityThe next interoperability utility we?ll cover is the File Migration Utility

15. Microsoft File Migration Utility Overview Microsoft File Migration Utility (MSFMU) simplifies the process of migrating file data from NetWare to Windows 2000: Accelerates Migration Process Preserves Access Control Information Simplifies Migration Management Slide Objective: In order to reduce the costs and simplify the process of migrating off NetWare, Microsoft?s File Migration Utility provides an easy-to-use service to migrate NetWare files to Windows 2000 Server. FileMigrate is a simple utility that helps customers more easily migrate their NetWare files from NetWare to Windows 2000 Server. Microsoft included this utility to help customers who wanted to reduce the number of network operating systems they have to support by consolidating on the multi-purpose Windows 2000 Server platform, but wanted a simpler and faster way to transfer and preserve their existing NetWare files over to Windows 2000 Server. FileMigrate addresses these customer needs by: Accelerating the Migration Process with multiple volume source and destination support Preserving Access Control Information of all migrated files to avoid re-ACLing. Simplifying Migration Management by providing a single file migration console to perform migrations. [Presenter?s Note: The main point here is that FileMigrate provides a simple way to quickly migrate files from NetWare to Windows 2000 Server while preserving file permissions reducing the time and cost or migration.] Slide Objective: In order to reduce the costs and simplify the process of migrating off NetWare, Microsoft?s File Migration Utility provides an easy-to-use service to migrate NetWare files to Windows 2000 Server. FileMigrate is a simple utility that helps customers more easily migrate their NetWare files from NetWare to Windows 2000 Server. Microsoft included this utility to help customers who wanted to reduce the number of network operating systems they have to support by consolidating on the multi-purpose Windows 2000 Server platform, but wanted a simpler and faster way to transfer and preserve their existing NetWare files over to Windows 2000 Server. FileMigrate addresses these customer needs by: Accelerating the Migration Process with multiple volume source and destination support Preserving Access Control Information of all migrated files to avoid re-ACLing. Simplifying Migration Management by providing a single file migration console to perform migrations. [Presenter?s Note: The main point here is that FileMigrate provides a simple way to quickly migrate files from NetWare to Windows 2000 Server while preserving file permissions reducing the time and cost or migration.]

16. MSFMU Benefits Slide Objective: FileMigrate provides a number of benefits to Novell customers who have decided to consolidate their network operating environment on a single multi-purpose platform: Windows 2000 Server. FileMigrate is a simple tool, integrated with MSDSS, to help Novell customers partially or completely migrate to the multi-purpose Windows 2000 Server network operating system platform. FileMigrate simplifies the migration process because it: [Advance Slide Build] Accelerates the Migration Process by copying NetWare files from one or several NetWare file and print servers to one or many ?destination? Windows 2000 Servers. [Advance Slide Build] Preserves Access Control Information: FileMigrate preserves the file permissions established in NetWare during the migration to Windows 2000 Server [Advance Slide Build] Simplifies Migration Management: FileMigrate also meets the customer requirement of being easy to use and manage for both file migration as well as the whole migration process with centralized management tools and multi-protocol and NetWare version support. Slide Objective: FileMigrate provides a number of benefits to Novell customers who have decided to consolidate their network operating environment on a single multi-purpose platform: Windows 2000 Server. FileMigrate is a simple tool, integrated with MSDSS, to help Novell customers partially or completely migrate to the multi-purpose Windows 2000 Server network operating system platform. FileMigrate simplifies the migration process because it: [Advance Slide Build] Accelerates the Migration Process by copying NetWare files from one or several NetWare file and print servers to one or many ?destination? Windows 2000 Servers. [Advance Slide Build] Preserves Access Control Information: FileMigrate preserves the file permissions established in NetWare during the migration to Windows 2000 Server [Advance Slide Build] Simplifies Migration Management: FileMigrate also meets the customer requirement of being easy to use and manage for both file migration as well as the whole migration process with centralized management tools and multi-protocol and NetWare version support.

17. Accelerates Migration Process MSFMU enables multiple NetWare files to be migrated rapidly to Windows 2000 Server Supports multiple destinations Slide Objective: Illustrate that MSFMU can migrate files from on or more servers to a single Windows 2000 Server and have the same files that existed on two NetWare servers not exist on a single Windows 2000 file server. Migrations from one platform to another are often time-consuming and costly. To minimize the time and expense required to migrate from a NetWare NOS to the Windows 2000 Server platform, Microsoft provides a file migration tool. FileMigrate reduces the time, cost and inconvenience of migration by copying groups of NetWare files from either one or several NetWare file and print servers to one or many ?destination? Windows 2000 Servers. This capability is known as one to many and many to many support. As the diagram illustrates, through the FileMigrate management console, a summary view of files is displayed. Through this console multiple groups of folders from multiple servers (in this case A and B) can be simultaneously copied and migrated to a Windows 2000 Server. Once migration is complete, the NetWare files that existing only on the NetWare server are now present on both. Once this is done the NetWare servers can be retired, upgraded to Windows 2000, or re-purposed for use in other functions. Slide Objective: Illustrate that MSFMU can migrate files from on or more servers to a single Windows 2000 Server and have the same files that existed on two NetWare servers not exist on a single Windows 2000 file server. Migrations from one platform to another are often time-consuming and costly. To minimize the time and expense required to migrate from a NetWare NOS to the Windows 2000 Server platform, Microsoft provides a file migration tool. FileMigrate reduces the time, cost and inconvenience of migration by copying groups of NetWare files from either one or several NetWare file and print servers to one or many ?destination? Windows 2000 Servers. This capability is known as one to many and many to many support. As the diagram illustrates, through the FileMigrate management console, a summary view of files is displayed. Through this console multiple groups of folders from multiple servers (in this case A and B) can be simultaneously copied and migrated to a Windows 2000 Server. Once migration is complete, the NetWare files that existing only on the NetWare server are now present on both. Once this is done the NetWare servers can be retired, upgraded to Windows 2000, or re-purposed for use in other functions.

18. Preserves File Information Preserves NetWare file permissions and ACLs Integrated with MSDSS migration service No need to re-ACL file permissions Granular mapping support Slide Objective: Show how the files (depicted as letters) and their unique permissions (depicted as numbers) are preserved after migration to Windows 2000 Server One of the most time-consuming aspects to migration is not the time required to copy files from one server to another but to recreate the permissions and rights associated with those files present in the source file server to the new destination server. FileMigrate addresses this issue by preserving the file permissions that may have already been set-up in NetWare, eliminating the need to re-ACL or redefine file permissions post-migration. In this diagram the files migrated from NetWare to Windows 2000 Server have preserved the same access rights they had in NetWare. File security is preserved as well as file associations to particular groups through granular object mapping. FileMigrate is also integrated with the directory migration service in MSDSS to to ensure that migrated users have the same rights and permissions to files as they did before. Slide Objective: Show how the files (depicted as letters) and their unique permissions (depicted as numbers) are preserved after migration to Windows 2000 Server One of the most time-consuming aspects to migration is not the time required to copy files from one server to another but to recreate the permissions and rights associated with those files present in the source file server to the new destination server. FileMigrate addresses this issue by preserving the file permissions that may have already been set-up in NetWare, eliminating the need to re-ACL or redefine file permissions post-migration. In this diagram the files migrated from NetWare to Windows 2000 Server have preserved the same access rights they had in NetWare. File security is preserved as well as file associations to particular groups through granular object mapping. FileMigrate is also integrated with the directory migration service in MSDSS to to ensure that migrated users have the same rights and permissions to files as they did before.

19. Simplifies Migration Management Central point of migration administration through a client connected to a Windows 2000 Server Migration status reporting Incremental migration support Supports TCP/IP and IPX/SPX protocols and multiple NetWare versions Slide Objective: Illustrate how a single client can view multiple NetWare servers, select multiple files to migrate and do so through a central point of migration administration. In addition to being fast and complete FileMigrate also meets the customer requirement of being easy to use and manage for both file migration as well as the whole migration process. FileMigrate provides a central point of administration for all file migration tasks through a wizard-based UI so that you can see where file(s) are coming from and where they are being transferred to. In addition, a helpful migration status view allows an administrator overseeing the migration process to monitor status and check post-migration file attributes. FileMigrate is administered through a wizard-based console and is installed as a service on a Windows 2000 Server. FileMigrate also supports incremental migration so that customers can migrate their NetWare files in an orderly, incremental and reversible way. Finally, FileMigrate supports the two major NetWare network protocols IPX/SPX and TCP/IP so that files from NetWare 3.x, 4.x or 5.x can be migrated in the same way for customers with a variety of NetWare versions or protocols. Slide Objective: Illustrate how a single client can view multiple NetWare servers, select multiple files to migrate and do so through a central point of migration administration. In addition to being fast and complete FileMigrate also meets the customer requirement of being easy to use and manage for both file migration as well as the whole migration process. FileMigrate provides a central point of administration for all file migration tasks through a wizard-based UI so that you can see where file(s) are coming from and where they are being transferred to. In addition, a helpful migration status view allows an administrator overseeing the migration process to monitor status and check post-migration file attributes. FileMigrate is administered through a wizard-based console and is installed as a service on a Windows 2000 Server. FileMigrate also supports incremental migration so that customers can migrate their NetWare files in an orderly, incremental and reversible way. Finally, FileMigrate supports the two major NetWare network protocols IPX/SPX and TCP/IP so that files from NetWare 3.x, 4.x or 5.x can be migrated in the same way for customers with a variety of NetWare versions or protocols.

20. Agenda Overview Microsoft Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary Another useful complement to the file and directory migration utilities I?ve discussed is File and Print Services for NetWare.Another useful complement to the file and directory migration utilities I?ve discussed is File and Print Services for NetWare.

21. File and Print Services for NetWare v.5 Overview File and Print Services for NetWare v.5 (FPNW5) enables administrators to manage a Windows 2000 Server as if it were a NetWare file and print server: Reduces Migration Costs Consolidates Hardware Support Costs Simplifies File and Print Server Administration Slide Objective: While not a migration tool itself, FPNW5 facilitates migration by minimizing the impact of migration. The most common use of the NetWare network operating system for Novell customers is as a file and print server. Customers who have used NetWare as the platform to host their file and print services have become accustomed to its interface from both a user and an administrator point of view. However, many customers have found that Windows 2000 Server provides scalable file and print services as well if not better than NetWare and/or are looking to reduce the number of platforms they have to support and are choosing to consolidate on the multi-purpose Windows 2000 Server platform. To help customers more easily achieve their migration objectives while minimizing the collateral impact and cost of that migration, Microsoft developed File and Print services for NetWare which allows a Windows 2000 Server to actually ?look? like a NetWare file and print server. That helps: Reduce the Transition Costs associated with Migration Makes it easier to consolidate hardware and reduce support costs Simplifies file and print server administration. [Presenter?s Note: The main point here is that FPNW5 is a great tool to use to minimize the retraining impact of migrating to Windows 2000 Server from a NetWare file and print server. The key here is Windows 2000 performance and consolidation benefits with lower re-training for all involved.]Slide Objective: While not a migration tool itself, FPNW5 facilitates migration by minimizing the impact of migration. The most common use of the NetWare network operating system for Novell customers is as a file and print server. Customers who have used NetWare as the platform to host their file and print services have become accustomed to its interface from both a user and an administrator point of view. However, many customers have found that Windows 2000 Server provides scalable file and print services as well if not better than NetWare and/or are looking to reduce the number of platforms they have to support and are choosing to consolidate on the multi-purpose Windows 2000 Server platform. To help customers more easily achieve their migration objectives while minimizing the collateral impact and cost of that migration, Microsoft developed File and Print services for NetWare which allows a Windows 2000 Server to actually ?look? like a NetWare file and print server. That helps: Reduce the Transition Costs associated with Migration Makes it easier to consolidate hardware and reduce support costs Simplifies file and print server administration. [Presenter?s Note: The main point here is that FPNW5 is a great tool to use to minimize the retraining impact of migrating to Windows 2000 Server from a NetWare file and print server. The key here is Windows 2000 performance and consolidation benefits with lower re-training for all involved.]

22. FPNW5 Benefits Slide Objective: FPNW5 helps organizations achieve multiple objectives while reducing costs. FPNW5 helps customers reduce the costs of migration to Windows 2000 Server so that customers can realize the benefits of consolidated file and print server hardware costs and simplified file and print server administration. FPNW?which runs as part of the NWLink IPX/SPX-compatible service?enables Windows NT Server to emulate a NetWare file and print server and provide file and print resources using the same dialogs as NetWare servers. Slide Objective: FPNW5 helps organizations achieve multiple objectives while reducing costs. FPNW5 helps customers reduce the costs of migration to Windows 2000 Server so that customers can realize the benefits of consolidated file and print server hardware costs and simplified file and print server administration. FPNW?which runs as part of the NWLink IPX/SPX-compatible service?enables Windows NT Server to emulate a NetWare file and print server and provide file and print resources using the same dialogs as NetWare servers.

23. Reduces Migration Costs Transparent to Admins and Users Provides a NetWare user interface to a Windows 2000 file and print server Same NetWare log-in sequence for Users Same NetWare management tools for Administrators No client changes required Supports multiple client versions The first way the use of FPNW5 benefits Novell customers is through reduced training and re-training costs typically encountered during migration. FPNW makes a Windows 2000 Server look like a NetWare server to any of the Windows-based clients. FPNW5 reduces the impact of migrating to Windows 2000 Server by by providing a NetWare user interface to a Windows 2000 Server so that administrators and users see the same NetWare UI they?re familiar with. This means that to both admins and users, the replacement of a NetWare file and print server with a Windows 2000 file and print server is completely transparent ? they still think they?re using NetWare. Users can log on to a machine running Windows 2000 Server and have their interface look the same as if they had logged on to a NetWare 3.x Server. Admins can manage Windows 2000 Server file and print services with NetWare tools, eliminating the need for retraining. In addition, Using FPNW also does not require changes to NetWare clients. For example, a client program that uses NetWare protocols and naming conventions needs no redirection or translation. The first way the use of FPNW5 benefits Novell customers is through reduced training and re-training costs typically encountered during migration. FPNW makes a Windows 2000 Server look like a NetWare server to any of the Windows-based clients. FPNW5 reduces the impact of migrating to Windows 2000 Server by by providing a NetWare user interface to a Windows 2000 Server so that administrators and users see the same NetWare UI they?re familiar with. This means that to both admins and users, the replacement of a NetWare file and print server with a Windows 2000 file and print server is completely transparent ? they still think they?re using NetWare. Users can log on to a machine running Windows 2000 Server and have their interface look the same as if they had logged on to a NetWare 3.x Server. Admins can manage Windows 2000 Server file and print services with NetWare tools, eliminating the need for retraining. In addition, Using FPNW also does not require changes to NetWare clients. For example, a client program that uses NetWare protocols and naming conventions needs no redirection or translation.

24. Consolidates Hardware Support Costs Take advantage of symmetric multi-processing support in Windows 2000 Requires fewer file and print servers to handle the same load Increases server hardware utilization By migrating to Windows 2000 Server and using FPNW5 to minimize the impact on network users, customers can reduce their support costs by consolidating and reducing the amount of server hardware they must maintain In addition to having 30+% faster performance than NetWare, customers can also benefits by the superior SMP support present in Windows 2000 Server. This means that multiple single processor NetWare file and print servers can be reduced to fewer, or even one multi-processor Windows 2000 Servers allowing those servers to be used more productively. As this graphic illustrates a typical NetWare 4.x hardware configuration 2-3 years ago contained 10GB of storage and 1 Pentium II processor per server. To store 60GB of information would require 12 servers at a 50% utilization rate. Since NetWare lacks SMP support, it would not be feasible to consolidate to a multi-processor server on NetWare. However, all 12 older NetWare servers could be consolidated to a single high performance 2p Windows 2000 Server with a 100GB of storage, while increasing utilization from 50-60% with plenty of room to grow. An upgrade to NetWare 5 on similar hardware would also reduce the number of servers, but not to one, since no version of NetWare has SMP support of any kind. The impact of this is that of administering 12 NetWare 1p file and print servers, only a single 2p server needs to be administered in Windows 2000 Server to perform the same task. By migrating to Windows 2000 Server and using FPNW5 to minimize the impact on network users, customers can reduce their support costs by consolidating and reducing the amount of server hardware they must maintain In addition to having 30+% faster performance than NetWare, customers can also benefits by the superior SMP support present in Windows 2000 Server. This means that multiple single processor NetWare file and print servers can be reduced to fewer, or even one multi-processor Windows 2000 Servers allowing those servers to be used more productively. As this graphic illustrates a typical NetWare 4.x hardware configuration 2-3 years ago contained 10GB of storage and 1 Pentium II processor per server. To store 60GB of information would require 12 servers at a 50% utilization rate. Since NetWare lacks SMP support, it would not be feasible to consolidate to a multi-processor server on NetWare. However, all 12 older NetWare servers could be consolidated to a single high performance 2p Windows 2000 Server with a 100GB of storage, while increasing utilization from 50-60% with plenty of room to grow. An upgrade to NetWare 5 on similar hardware would also reduce the number of servers, but not to one, since no version of NetWare has SMP support of any kind. The impact of this is that of administering 12 NetWare 1p file and print servers, only a single 2p server needs to be administered in Windows 2000 Server to perform the same task.

25. Simplifies F/P Server Admin Leverage existing NetWare skill sets Avoid retraining costs Defer Windows 2000 training costs Centralize file and print server administration Support 1 file and print platform Simplifies File and Print Server Administration: By letting a Windows 2000 Server look like a NetWare file and print server the existing skill sets present with your NetWare administrator can be preserved and leveraged without costly re-training. Moreover file and print server administration can now be centralized reducing administration and support costs. In addition, if Windows NT Server already exists with NetWare in a mixed environment, an upgrade to Windows 2000 Server reduces the number of platforms to be supported to only one. FPNW5 provides a NetWare user interface to a Windows 2000 while taking advantage of the faster performance and SMP support of Windows 2000 Server. Moreover FPNW5 can be deployed without any client side changes so that users see their files organized in Windows 2000 as if they were still being stored and managed in a NetWare file and print server. Simplifies File and Print Server Administration: By letting a Windows 2000 Server look like a NetWare file and print server the existing skill sets present with your NetWare administrator can be preserved and leveraged without costly re-training. Moreover file and print server administration can now be centralized reducing administration and support costs. In addition, if Windows NT Server already exists with NetWare in a mixed environment, an upgrade to Windows 2000 Server reduces the number of platforms to be supported to only one. FPNW5 provides a NetWare user interface to a Windows 2000 while taking advantage of the faster performance and SMP support of Windows 2000 Server. Moreover FPNW5 can be deployed without any client side changes so that users see their files organized in Windows 2000 as if they were still being stored and managed in a NetWare file and print server.

26. Agenda Overview Microsoft Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary In addition to the interoperability utilities already presented in Services for NetWare, there are also other services that are included in Windows 2000 products as well as interoperability services for Windows NT Server 4.0 available.In addition to the interoperability utilities already presented in Services for NetWare, there are also other services that are included in Windows 2000 products as well as interoperability services for Windows NT Server 4.0 available.

27. Other Interoperability Utilities Services for NetWare 5.0 also contains utilities that were available previously in Services for NetWare 4.0: Directory Service Manager for NetWare allows a Windows NT 4.0 Domain to centrally administer multiple NetWare 2.x/3.x binderies File and Print Services for NetWare 4 enables administrators to manage a Windows NT Server 4.0 as if it were a NetWare file and print server Slide Objective: In order to provide a one-stop location for all of Microsoft?s interoperability and migration utilities for NetWare, Services for NetWare also includes two tools that provide better NetWare interoperability with Windows NT Server 4.0. Directory Service Manager for NetWare allows a Windows NT 4.0 Domain Controller to centrally administer multiple NetWare 2.x/3.x binderies. This is useful for customers who are not immediately planning to upgrade to Windows 2000 Server from Windows NT Server 4.0, OR have NetWare 3.x deployments and are looking for a better way to manage NetWare binderies. However, if a customer is planning to migrate to Windows 2000 Server, MSDSS provides an even better way to manage NetWare binderies. The choice depends on a customer?s need for NetWare 3.x bindery management. File and Print Services for NetWare v.4 performs an identical function as FPNW5 but instead allows a Windows NT Server 4.0 to look like like a NetWare 3.x server rather than allow a Windows 2000 Server to look like a NetWare 3.x server.Slide Objective: In order to provide a one-stop location for all of Microsoft?s interoperability and migration utilities for NetWare, Services for NetWare also includes two tools that provide better NetWare interoperability with Windows NT Server 4.0. Directory Service Manager for NetWare allows a Windows NT 4.0 Domain Controller to centrally administer multiple NetWare 2.x/3.x binderies. This is useful for customers who are not immediately planning to upgrade to Windows 2000 Server from Windows NT Server 4.0, OR have NetWare 3.x deployments and are looking for a better way to manage NetWare binderies. However, if a customer is planning to migrate to Windows 2000 Server, MSDSS provides an even better way to manage NetWare binderies. The choice depends on a customer?s need for NetWare 3.x bindery management. File and Print Services for NetWare v.4 performs an identical function as FPNW5 but instead allows a Windows NT Server 4.0 to look like like a NetWare 3.x server rather than allow a Windows 2000 Server to look like a NetWare 3.x server.

28. Relationship to Windows 2000 SFNW5 ships separately from the NetWare connectivity services included in Windows 2000 Services for NetWare 5 is a separate product not bundled with Windows 2000 Server or Professional. Windows 2000, however, does have other connectivity services that customers should be aware of which are useful in achieving NetWare interoperability and migration. These bundled services both complement and help enable the components included in Services for NetWare Services for NetWare has already been covered and provides the interoperability services that actually synchronize or migrate information, files , and functionality between NetWare and Windows 2000 The interoperability services bundled with Windows 2000, in contrast, include what are more accurately described as connectivity services that enable and facilitate communication between NetWare and Windows 2000 but do not synchronize or migrate that information There are 3 key connectivity services bundled with Windows 2000 Server that facilitate cross-platform communication: NWLInk is an IPX/SPX Transport protocol that connects Windows 2000 computer systems with those NetWare versions (NetWare 4.x and earlier) that use the proprietary legacy IPX/SPX protocol. IPX support preserves investments in legacy NetWare networks by making it easy to integrate them with Windows 2000 Server. (shipped with all versions of Windows 2000) Gateway Services for NetWare enables a computer running Windows 2000 Server to connect to computers running NetWare 3.x or 4.x server software. Logon script support is also included. In addition, administrators can use GSNW to create gateways to NetWare resources, allowing computers running only Microsoft client software to gain access to NetWare resources. (shipped only Windows 2000 Server, Windows 2000 Advanced Server and Windows 2000 DataCenter) Client Services for NetWare enables a computer running Windows 2000 Professional to connect to computers running NetWare 3.x or 4.x server software. CSNW allows clients to access NetWare resources on the IPX/SPX protocol stack without requiring a separate Novell client. (shipped only with Windows 2000 Professional) [Presenter?s Note: The main point here is that Windows 2000 includes NetWare connectivity services; Services for NetWare includes interoperability and migration services. Combined Microsoft provides a comprehensive way for Novell customers to connect to, interoperate with and migrate to Windows 2000.] Possible Questions: Q1: Is Microsoft shipping Novell?s client on Windows 2000 Professional? Yes and No. Microsoft is only shipping the bits to upgrade an existing Novell client on Windows NT Workstation 4.0. Microsoft did this to allow a seamless upgrade from Windows NT Workstation 4.0 to Windows 2000 Professional for NTW4 clients with existing installed Novell clients. Fresh installs of Windows 2000 Professional or NTW4 upgrades that do not have an existing Novell client will not be accompanied and will not install a Novell client Q2: Why doesn?t Microsoft just include the utilities in Services for NetWare with Windows 2000? Mostly because many customers who purchase Windows 2000 simply do not have much investments in Novell operating systems or directories. Moreover having all of the interoperability services in one product helps customers implement overall NetWare/Windows 2000 interoperability and migration initiatives.Services for NetWare 5 is a separate product not bundled with Windows 2000 Server or Professional. Windows 2000, however, does have other connectivity services that customers should be aware of which are useful in achieving NetWare interoperability and migration. These bundled services both complement and help enable the components included in Services for NetWare Services for NetWare has already been covered and provides the interoperability services that actually synchronize or migrate information, files , and functionality between NetWare and Windows 2000 The interoperability services bundled with Windows 2000, in contrast, include what are more accurately described as connectivity services that enable and facilitate communication between NetWare and Windows 2000 but do not synchronize or migrate that information There are 3 key connectivity services bundled with Windows 2000 Server that facilitate cross-platform communication: NWLInk is an IPX/SPX Transport protocol that connects Windows 2000 computer systems with those NetWare versions (NetWare 4.x and earlier) that use the proprietary legacy IPX/SPX protocol. IPX support preserves investments in legacy NetWare networks by making it easy to integrate them with Windows 2000 Server. (shipped with all versions of Windows 2000) Gateway Services for NetWare enables a computer running Windows 2000 Server to connect to computers running NetWare 3.x or 4.x server software. Logon script support is also included. In addition, administrators can use GSNW to create gateways to NetWare resources, allowing computers running only Microsoft client software to gain access to NetWare resources. (shipped only Windows 2000 Server, Windows 2000 Advanced Server and Windows 2000 DataCenter) Client Services for NetWare enables a computer running Windows 2000 Professional to connect to computers running NetWare 3.x or 4.x server software. CSNW allows clients to access NetWare resources on the IPX/SPX protocol stack without requiring a separate Novell client. (shipped only with Windows 2000 Professional) [Presenter?s Note: The main point here is that Windows 2000 includes NetWare connectivity services; Services for NetWare includes interoperability and migration services. Combined Microsoft provides a comprehensive way for Novell customers to connect to, interoperate with and migrate to Windows 2000.] Possible Questions: Q1: Is Microsoft shipping Novell?s client on Windows 2000 Professional? Yes and No. Microsoft is only shipping the bits to upgrade an existing Novell client on Windows NT Workstation 4.0. Microsoft did this to allow a seamless upgrade from Windows NT Workstation 4.0 to Windows 2000 Professional for NTW4 clients with existing installed Novell clients. Fresh installs of Windows 2000 Professional or NTW4 upgrades that do not have an existing Novell client will not be accompanied and will not install a Novell client Q2: Why doesn?t Microsoft just include the utilities in Services for NetWare with Windows 2000? Mostly because many customers who purchase Windows 2000 simply do not have much investments in Novell operating systems or directories. Moreover having all of the interoperability services in one product helps customers implement overall NetWare/Windows 2000 interoperability and migration initiatives.

29. Agenda Overview Microsoft Directory Synchronization Services Microsoft File Migration Utility File and Print Services for NetWare Other Interoperability Services Summary In summary . . . . In summary . . . .

30. Services for NetWare 5.0 Summary Services for NetWare helps Novell customers: Simplify the adoption of Windows 2000 Rapidly build and populate Active Directory Easily synchronize with existing NDS environment Minimize retraining costs Reduce network administration Centralize multi-directory management Consolidate file and print server administration Facilitate migration process Move NDS/bindery information to Active Directory Move NetWare file and print servers to Windows 2000 Server Move NetWare files to Windows 2000 Server Slide Objective: Summarize the high-level benefits of Services for NetWare in a mixed NetWare/Windows Server environment. Services for NetWare 5.0 is a comprehensive set of interoperability utilities that help Novell customers more easily adopt, administer and migrate to a network environment that includes a growing presence of Windows 2000 Server. SFNW5 helps customers: Simplify Adoption of Windows 2000. Services for NetWare helps customers more easily incorporate a Windows 2000 Server into their mixed Novell environment. By using MSDSS customers can: rapidly build an AD directory structure than can reflect an existing NDS structure, synchronize with NDS to centralize directory management through AD or flexibly administer a multi-master directory environment that consists of AD and NDS. In addition retraining costs are reduced with FPNW5 which reduces the impact of gaining the performance and consolidation benefits of Windows 2000 Server as a file server by allowing a Windows 2000 Server to look like a NetWare 3.x server, minimizing re-training costs for administrators skilled in administer NetWare. Reduces Network Administration. Service for NetWare also helps customers actually reduce the support and administration costs typically associated with a multiple directory and platform environment. For example, MSDSS lets customer centralize the administration of AD and NDS on a single AD platform through 1-way synchronization. Instead of updating both directories manually, only AD needs to be updated and those changes are automatically synchronized with NDS preserving data integrity across both directories. In addition, FPNW5 also helps reduce administration by more easily allowing customers to centralize file and print service functions on a single platform while preserving their investment in NetWare administration skill sets. Facilitate Migration Process. Services for NetWare 5 also provides the capability to allow customers to comprehensively, quickly, and easily migrate from a NetWare environment to Windows 2000. MSDSS provides the tools needed to migrate NDS information to Active Directory. FPNW5 helps assist customers migrate their NetWare file and printservers over to Windows 2000. FileMigrate provides a centrally administered file migration capability that moves files and their permissions to one or more Windows 2000 Servers In conclusion, Services for NetWare 5 is a flexible multi-purpose collection of interoperability utilities that help customers deploy Windows 2000 based services and solutions into a mixed NetWare environment, reduce network administration time and costs and completely and quickly migrate their Novell-based directories, NOS, and files to Windows 2000 Server to enjoy the greater reliability, manageability, and platform integration benefits of Windows 2000 Presenter?s Note: The main point here is that Services for NetWare is a requirement for companies requiring any degree of interoperability between NetWare and Windows 2000 and can help them more painlessly migrate to Windows 2000 from NetWare than ever before.Slide Objective: Summarize the high-level benefits of Services for NetWare in a mixed NetWare/Windows Server environment. Services for NetWare 5.0 is a comprehensive set of interoperability utilities that help Novell customers more easily adopt, administer and migrate to a network environment that includes a growing presence of Windows 2000 Server. SFNW5 helps customers: Simplify Adoption of Windows 2000. Services for NetWare helps customers more easily incorporate a Windows 2000 Server into their mixed Novell environment. By using MSDSS customers can: rapidly build an AD directory structure than can reflect an existing NDS structure, synchronize with NDS to centralize directory management through AD or flexibly administer a multi-master directory environment that consists of AD and NDS. In addition retraining costs are reduced with FPNW5 which reduces the impact of gaining the performance and consolidation benefits of Windows 2000 Server as a file server by allowing a Windows 2000 Server to look like a NetWare 3.x server, minimizing re-training costs for administrators skilled in administer NetWare. Reduces Network Administration. Service for NetWare also helps customers actually reduce the support and administration costs typically associated with a multiple directory and platform environment. For example, MSDSS lets customer centralize the administration of AD and NDS on a single AD platform through 1-way synchronization. Instead of updating both directories manually, only AD needs to be updated and those changes are automatically synchronized with NDS preserving data integrity across both directories. In addition, FPNW5 also helps reduce administration by more easily allowing customers to centralize file and print service functions on a single platform while preserving their investment in NetWare administration skill sets. Facilitate Migration Process. Services for NetWare 5 also provides the capability to allow customers to comprehensively, quickly, and easily migrate from a NetWare environment to Windows 2000. MSDSS provides the tools needed to migrate NDS information to Active Directory. FPNW5 helps assist customers migrate their NetWare file and printservers over to Windows 2000. FileMigrate provides a centrally administered file migration capability that moves files and their permissions to one or more Windows 2000 Servers In conclusion, Services for NetWare 5 is a flexible multi-purpose collection of interoperability utilities that help customers deploy Windows 2000 based services and solutions into a mixed NetWare environment, reduce network administration time and costs and completely and quickly migrate their Novell-based directories, NOS, and files to Windows 2000 Server to enjoy the greater reliability, manageability, and platform integration benefits of Windows 2000 Presenter?s Note: The main point here is that Services for NetWare is a requirement for companies requiring any degree of interoperability between NetWare and Windows 2000 and can help them more painlessly migrate to Windows 2000 from NetWare than ever before.

31. Closing In today?s marketplace, organizations need to carefully manage their costs in order to stay competitive. Windows 2000 Server has been designed to provide powerful management through its integrated Active Directory service. Active Directory enables customers to increase the value of their existing investments and lower their overall costs of computing by making the Windows network operating system more manageable, secure and interoperable. For more information on the Windows 2000 Active Directory see: http://www.Microsoft.com/windows/server/Closing In today?s marketplace, organizations need to carefully manage their costs in order to stay competitive. Windows 2000 Server has been designed to provide powerful management through its integrated Active Directory service. Active Directory enables customers to increase the value of their existing investments and lower their overall costs of computing by making the Windows network operating system more manageable, secure and interoperable. For more information on the Windows 2000 Active Directory see: http://www.Microsoft.com/windows/server/


Other Related Presentations

Copyright © 2014 SlideServe. All rights reserved | Powered By DigitalOfficePro