Microsoft KB Archive/298462

= Resources for Migrating from Novell NetWare to Windows NT 4.0 =

Article ID: 298462

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Server 4.0 Enterprise Edition
 * Microsoft BackOffice Server 4.0
 * Microsoft BackOffice Small Business Server 4.0
 * Microsoft BackOffice Small Business Server 4.5

-



This article was previously published under Q298462



SUMMARY
This article contains helpful information about how to use the Migration Tool for NetWare (Nwconv.exe), including a deployment guide, walk-through documents, and case studies.



Using the Migration Tool for NetWare (Nwconv.exe)
Download the Microsoft Windows NT Server NetWare Integration Deployment Guide

This self-executing file contains the Microsoft Windows NT Server NetWare Integration Deployment Guide (in Microsoft Word format). This document is a detailed guide for planning and implementing a deployment of Microsoft Windows NT Server in an enterprise environment comprised of both Windows NT and Novell NetWare servers.

An Overview of NetWare Compatibility Features

This document provides a brief description of the various features and services that enable Windows NT computers to coexist with Novell NetWare networks and servers. Some of these services and tools are included with Windows NT Server and Windows NT Workstation, while others are available as separate products.

Case Study: NetWare-to-Windows NT Migration

This case study examines how Boardwalk Equities, Inc., a fast-growing property management company, improved the stability of their custom programs by migrating from the limited capabilities of their DOS/Novell NetWare servers. This article describes how they first integrated Microsoft BackOffice technology with their NetWare servers and eventually migrated entirely to Windows NT.

Case Study: Improving NetWare-to-Windows NT Migration

This case study discusses how a large network integration company with clients across the United States made the decision to migrate from their Novell NetWare network to Microsoft Windows NT. The article explains the decision to use Windows NT Server and the lessons learned during the migration process. The procedures and tips described here should be useful to systems professionals in many medium-sized to large-sized companies with older networking operating systems.

Before the Migration
Where can I find a general overview of the Novell NetWare-to-Windows NT migration process?

When do I use the Migration Tool for NetWare (Nwconv.exe)?

Can I consolidate multiple NetWare servers into one Windows NT server?

What steps should I take before I begin the actual migration process?

What protocols and services do I need to install on my Windows NT domain controller so that the Migration Tool for NetWare can communicate with my NetWare servers?

When I install NWLink on my computer running Windows NT, how can I determine what frame type is being used by the NetWare server and how do I find the IPX network number?

What is the difference between an Internetwork Packet Exchange (IPX) network number and an internal IPX network number?

How can I tell which frame type and network number my Windows NT-based computer is using?

Does Windows NT Server automatically assign an IPX frame type or do I need to specify one manually?

Where can I find simple, step-by-step instructions about how to perform a basic NetWare server to Windows NT Server migration using the Migration Tool for NetWare?

Do I need to run the Migration Tool for NetWare on a domain controller or can I use a standalone computer running Windows NT Server?

How do I migrate my NetWare users' personal login scripts?

During the Migration
How do I transfer NetWare accounts to a trusted domain instead of moving them to the local domain server?

[http://support.microsoft.com/kb/157606/en-us NetWare groups are not being migrated to the Windows NT server. What could be the problem?]

How do I add the NetWare Supervisors group to the Administrators group on a Windows NT computer?

[http://support.microsoft.com/kb/187789/en-us Existing user passwords are not being migrated to the Windows NT server. Why is this happening?]

How can I migrate only selected files from a NetWare volume to a Windows NT server?

How do I specify the destination folder for migrated files?

Where can I find information containing the results of a completed migration?

[http://support.microsoft.com/kb/173669/en-us I cannot migrate users from a NetWare 4.x server. How do I resolve this?]

Why does the Migration Tool for NetWare (Nwconv.exe) appear to restart the migration process when I attempt to migrate more than 4 gigabytes (GB) of data?

[http://support.microsoft.com/kb/135723/en-us When I use the Migration Tool for NetWare to migrate a NetWare Macintosh volume to a Windows NT Macintosh volume, files are damaged. How can I prevent this from happening?]

Group file and folder permissions are not being migrated correctly, and the error log contains errors similar to &quot;[Transferring Files - Access Rights for: Volume:DirError 0: Adding Access Rights.&quot; What could be causing this problem?]

Why do I receive the error message &quot;NWCONV.EXE - Unable to locate DLL&quot; when I attempt to run the Migration Tool for NetWare?

[http://support.microsoft.com/kb/177611/en-us When I attempt to transfer data to a partition on a computer running Windows NT Server that contains more free space than needed to complete migration, I receive an error message stating that there is not enough free space to transfer the files. How do I resolve this?]

When I attempt to run the Migration Tool for NetWare on a computer running Windows NT, I receive the error message &quot;Cannot connect to server: servername The network name cannot be found.&quot; How do I resolve this?

Why does the Migration Tool for NetWare stop responding (hang) with exception error 0xc0000005 in Nwconv.exe and generate a Drwtsn32.log file when I attempt to migrate user accounts and data from Novell NetWare 3.1x servers to a Windows NT server?

Why are the Source Files and Destination boxes blank in the File Options dialog box in the Migration Tool for NetWare?

Why is the Transfer Users To Trusted Domain check box unavailable when I use the Migration Tool for NetWare to migrate users, groups, and files from a NetWare server to a Windows NT server?

[http://support.microsoft.com/kb/186874/en-us When I use the Migration Tool for NetWare to migrate users, changes to group memberships are being merged instead of replaced. Why is this happening?]

Is it true that when groups on a NetWare server are transferred to a Windows NT master domain they are created as global groups in the master domain, and again as local groups on the server specified in the Servers For Migration list?

[http://support.microsoft.com/kb/157608/en-us Only the default Everyone group exists on the NetWare server. When I attempt to transfer user and group accounts to Windows NT, user accounts are not transferred, and the &quot;Error: getting groups on server: server-name&quot; error appears in the error log. How do I resolve this?]

When I use the Migration Tool for NetWare to migrate users and groups, some groups are not migrated and the &quot;[Adding Users to Groups - Could not enumerate users for Group: GROUP_NAME&quot; error appears in the Error.log file. How do I resolve this?]

Why does &quot;Error Saving User [user_name&quot; appear in the error log for each user account even though the associated files are migrated?]

[http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fsupport%2fntserver%2fmigration%2fdefault.asp I have a question that is not covered in this FAQ. Where can I find additional online information about the migration process?]

After the Migration
How can I convert the environment variables in my NetWare login script so they are processed when migrated users log on to the Windows NT server?

[http://support.microsoft.com/kb/187541/en-us After I migrated user accounts using the Migration Tool for NetWare (Nwconv.exe), the Domain Account Policies I set on the Windows NT server changed. Why did this happen?]

[http://support.microsoft.com/kb/157606/en-us When I migrate using the Add Prefix option in the User And Group Options dialog box, NetWare groups with duplicate names on the Windows NT server are not migrated with the prefix I specify. How do I resolve this?]

How can I prevent a user from viewing another user's home directory?

How can I simulate the functionality of a NetWare MAP ROOT command in Windows NT Server?

Additional Migration Resources
NetWare Add-On Services for Windows NT

Microsoft Services for NetWare is a bundle of add-on utilities for Microsoft Windows NT Server 4.0 designed to enable you to enhance your Novell NetWare environment with Windows NT Server. Services for Netware, comprised of File and Print Services for NetWare (FPNW) and Directory Service Manager for NetWare (DSMN), is part of an overall Microsoft strategy to ease integration and interoperability between Windows NT Server and Novell NetWare. For this release, FPNW and DSMN are offered as a bundled solution called Services for NetWare.

Microsoft Services for NetWare Guide Reviewers Guide

Services for NetWare, comprised of File and Print Services for NetWare (FPNW) and Directory Service Manager for NetWare (DSMN), is a set of add-on utilities designed to ease integration of Windows NT Server 4.0 into existing Novell NetWare 2.x, 3.x, and 4.x (in bindery emulation mode only) environments. This downloadable Reviewer's Guide is designed to assist you in understanding and installing the two products.

File and Print Services for NetWare Reviewer's Guide

This downloadable guide explains how File and Print Services for NetWare (FPNW) enables you to enhance your NetWare 2.x, 3.x, or 4.x (in bindery emulation mode only)-based network with a multipurpose server operating system by enabling the integration of Windows NT Server into your network. In addition, because FPNW emulates a NetWare server, integrating Windows NT Server running FPNW requires no changes to NetWare clients, and you will be able to benefit from a multipurpose server operating system that offers excellent file and print, application, communication, and Internet/intranet services in one integrated solution.

Directory Service Manager for NetWare Reviewer's Guide

If you are using NetWare bindery to manage your NetWare 2.x, 3.x or 4.x network, download this guide to see how Directory Service Manager for NetWare (DSMN) can benefit you. Because it offers global directory services, Windows NT Server can help you manage multiple environments by providing a single-network logon to all services (including applications), and providing network administrators a central point of administration. With Windows NT Server and DSMN, you can centrally manage your mixed Windows NT and NetWare environment.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kbenv kbinfo KB298462

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.