Export (0) Print
Expand All

Preface

Published: June 07, 2005
On This Page

Overview Overview
Intended Audiences Intended Audiences
Scope Scope
How to Use This Migration Guide How to Use This Migration Guide
Contributors Contributors

Overview

Regardless of the size of your environment, migrating your entire existing environment to a new operating system can be a daunting task. This guide demonstrates how to break the process into stages to simplify your migration. The first stage, migrating directory, file, and print services, is outlined in this guide. This stage builds the infrastructure on which you will migrate the directory and file and print services. After you have a solid Windows Active Directory infrastructure in place, you can define future stages such as moving mail and other applications or adding Windows Active Directory features.

In this guide, you will learn how to plan your project, develop the solution for the new environment, determine the best migration strategy for your environment, and migrate directory and file and print services to the new environment.

The following topics are covered in this guide:

  • Major migration planning decisions

  • Migration tools and services

  • Migration options

  • Migration procedures

  • Operations guidelines for the new environment

This guide presumes that you have either already decided to migrate from NetWare to Windows Server 2003 or you are currently considering migration and you need to evaluate the available migration strategies before making a final decision.

Intended Audiences

This guide is intended for IT professionals working in a network environment that includes Novell’s NetWare operating system with Novell Directory Service (NDS), eDirectory, or Bindery directory services. It is specifically targeted at information technology (IT) professionals responsible for designing and implementing directory and file services in an enterprise environment:

  • IT technical decision makers

  • IT architects

  • IT support personnel

  • Infrastructure/Systems managers

  • System integrators

  • Consultants

Knowledge Prerequisites

This guide assumes that the reader has an understanding of the Microsoft file server technologies for Windows Server 2003 and Microsoft Active Directory services. The reader is also expected to have a working knowledge of the following:

  • Novell File Services and trustee permissions

  • E-Directory/NDS concepts

  • Centralized storage and backup concepts

  • Storage technologies, such as network-attached storage (NAS) and storage area network (SAN)

  • Networking and connectivity

  • Service operations

For links to in-depth information about Windows Server 2003 Active Directory, Novell NDS and Bindery, Novell File and Print, and other related topics, see the "Bibliography/References" section in Appendix A.

Scope

The scope of this guide is to provide guidance on the process for migrating Novell versions 3.x to 6.5 to Windows Server 2003 and Active Directory. The process includes envisioning and planning the migration project and guidance on implementing the solution using Microsoft and other vendors' tools (if required). Additional areas that are in scope include:

  • Guidance on migrating Novell network directory and file and print services for the product versions mentioned

  • Guidance on migrating Novell client workstation to be serviced by Microsoft Windows 2003 Servers

Areas that are not included in the scope of this guide are:

  • Windows NT/2000 to Windows 2003 migration in the case of mixed environments

  • Non Windows Server 2003 or Windows Storage Server 2003 environments

  • Applications or services beyond “out of the box” directory, file and print services. This includes applications such as GroupWise and ZENworks

How to Use This Migration Guide

The organization of this guide is based on the industry-proven need to manage IT projects according to a disciplined process that improves the odds of project success. This Novell migration guide provides prescriptive guidance for successfully carrying out a migration from Novell NetWare to Windows Server 2003 from its inception through its completion. It is designed to be used with a companion guide, the UNIX Migration Project Guide (UMPG). While this Novell migration guide contains the technical and solution-specific information needed for the project, the UMPG provides the disciplined process steps for using this information in the context of a migration project and a team organization model ("people and process" guidance).

To facilitate their side-by-side use, both guides use project phases as an organizational device. Specifically, they follow the structure of the Microsoft Solutions Framework (MSF), which defines five distinct phases for IT projects:

  • Envisioning

  • Planning

  • Developing (or Migrating in the case of migration projects)

  • Stabilizing

  • Deploying

Each guide presents the information (process or technical) needed for a phase within chapters named for that phase. For example, in the solution guide, business and technical information needed for the initial decision-making is in the Envisioning chapter, detailed procedures and scripts are in the Migrating chapters, and so on).

The UMPG is essentially "MSF applied to migration projects." It begins with an overview of MSF and then describes the processes that belong to each phase and the team roles responsible for them; it is not, however, meant to serve as a comprehensive introduction to MSF. In-depth information about MSF is available to interested readers on the Microsoft Solutions Frameworks Web site at http://www.microsoft.com/msf.

The reason for separating the process guidance from technical and project-specific guidance is to keep this guide as lean as possible. Some readers will need to focus narrowly on project tasks, while persons with project management and team lead responsibilities need to digest the UMPG guidance and apply it to the project.

Because organizational personnel and project team members tend to have different levels of involvement during different phases, the division of content according to project phase also supports the capability to focus on the material that is most relevant to a particular responsibility. The following list identifies likely readers by phase:

Guide Section or Project Phase

Organizational Roles of Likely Audiences

Project Team Roles of Likely Audiences

Introduction

Business decision makers, technical decision makers, architects

All team leads

Envisioning

Business decision makers, technical decision makers, architects

Product Management, Program Management, all team leads

Planning

Business decision makers, technical decision makers, architects

Product Management, Program Management, all team leads

Developing/Migrating

Developers, Operations team

Test, Development, Release Management, all team leads

Stabilizing

Developers, Operations team

Test, Development, Release Management, all team leads

Deploying

Operations team

Release Management, all team leads

Operations

Operations team

Release Management

Note: Although the two guides are designed to be used together, it is not necessary to follow the MSF processes and team guidance described in the UMPG if the organization has an alternative project methodology in place. In that case, the UMPG would be used merely to map the MSF phases and team structure to the elements of the organization's methodology. We recommend you read at least the overview of MSF in the UMPG to become familiar with the MSF Process Model, the MSF Team Model, and MSF terminology.

Organization of Chapters

Following an introductory chapter, this guide is divided into four sections, Plan, Build, Deploy, and Operate, that cover the entire span of the IT solution life cycle. The five Microsoft Solutions Framework phases fall into the first three sections, and the Microsoft Operations Framework is the reference framework for the final section.

  • Introduction. The Introduction chapter defines the project, provides an overview of the technologies discussed in this guide, and introduces migration options and tools.

  • Plan. The Plan section is divided into two chapters, Envisioning and Planning. These chapters correspond with the first two MSF phases. In the Envisioning Phase the team and sponsor agree on the high-level requirements and goals of the project. The Planning Phase is where the team defines what to build and deploy along with how and when to build it.

  • Build. The Build section is divided into two chapters, Migrating and Stabilizing, which correspond to the MSF Developing and Stabilizing phases. The Migrating chapter outlines the Developing Phase where the team builds and tests the solution and the migration process in an isolated lab environment. In the Stabilizing Phase the new Windows environment is built in the production environment and a limited number of pilot users are migrated.

  • Deploy. The Deploy section consists of a single chapter that covers the final MSF project phase, Deploying. The Deploying Phase chapter outlines the steps required to fully migrate the existing NetWare environment to the new "live" production environment.

  • Operate. The Operate section consists of a single chapter with high level guidelines for operating and maintaining your new environment.

Terminology

This guide uses the term "migration" to refer to:

  • Specific activities that happen in the Developing (or Migrating) Phase

  • The entire solution process

Contributors

Writer

Kathi Honegger (Convergent Computing)

Editors

Trelawney Goodell (Volt)

Thomas Olsen (Volt)

Program Manager

Pablo Bárcenas Ibinarriaga (Microsoft Corporation)

Project Manager

Rich Dorfman (Convergent Computing)

Reviewers

Fred Antrobus (Excell Data Corporation)

Christopher Westpoint (Microsoft Corporation)

Download
Solution for Migrating File, Print, and Directory Services from Novell NetWare to Windows Server 2003

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft