Replacing NetWare Servers with Windows Servers

A common process in a migration or partial migration from Novell NetWare to a Windows network environment involves the replacement of servers. Sometimes the server replacement is performed in entirety; sometimes the server replacement process is performed over an extended period of time. Regardless of the strategy chosen , the Services for NetWare tools provide options for the integration and migration process. The options are as follows :

• Enable a Windows server to simulate a Novell NetWare server.

• Set up a gateway to bridge a Windows share to link to a Novell server share.

• Migrate files from a Novell server to a Windows server.

Enabling a Windows Server to Simulate a Novell NetWare Server

One method of replacing a Novell server with a Windows server is to physically replace the Novell server with a Microsoft Windows system. The problem is usually the situation where users who are mapped to the Novell server need to have their mappings changed to the new Windows server. This creates a chicken and egg scenario where the server cannot be replaced because each client system needs to be touched, but each client system cannot be reconfigured until the server data is migrated .

By using the File and Print Services for NetWare server replacement functionality, a Microsoft Windows server can take on the exact same server name , IP address, and drive and resource mapping as the old Novell server. Effectively, the Microsoft server responds not only as a Windows server, but also can respond to Novell MAP commands for sharing files, printers, and other network devices. One day, the server was running on Novell NetWare, and the next day a Windows server running Windows 2000 or Windows 2003 responds to the exact same Novell access commands.

Login scripts, drive mappings, configuration access files, file permissions, and all other information is migrated from the old to new server. The process in which this is done is as follows:

1. Install Windows 2000 or Windows 2003 on a new server. Give the server a new Windows server name.

2. Install File and Print Services for NetWare on the server as described in the "Installation of the File and Print Services for NetWare" section earlier in this chapter.

3. When choosing the Novell name, temporarily select a new NetWare server name for this system (this will be changed later to be the exact same name as the old Novell server, however it cannot be changed now because the names will conflict in the directory).

4. Use the file migration tool to migrate all volume information from the old Novell server to the new Windows server as described in the "Using the File Migration Wizard to Migrate Files" section later in this chapter.

5. After all files have been migrated, unplug the old Novell server from the network. Do not shut the server off, delete the server from the directory, or make any changes to the network. Simply unplug the network cable to remove the system (that way if you have any problems with the new Windows server, you can simply plug the old server back in without making any network changes).

6. Change the IP address of the new Windows server to be the same IP address as the old Novell server.

7. Change the File and Print Services for NetWare server name to be identical to the name of the old Novell server.

8. Reboot the Windows server to reconnect to the network that will then respond as if it were the old NetWare server.

Bridging a Migration Gap Between Novell and Microsoft Environments

Another method of gaining access to Novell information during a migration to Windows is to set up the Gateway Services for NetWare (GSNW), which is part of the File and Print Services for NetWare installation tool. What GSNW does is allow a workstation that no longer has the Novell client installed to access a Novell NetWare shared resource by connecting through a Windows server. Instead of connecting directly from the client to the Novell server for file and print access, all file and printer components are redirected through a Windows server.

The Windows Server Becomes a Bottleneck

Because all traffic to a Novell server has to first go through a Windows server, the Windows server becomes a bottleneck if an extensive amount of traffic must be routed through the server. GSNW works fine for organizations with less than 2550 connections, or for organizations that are using GSNW for a temporary cross-over server in a migration process. When more than 100 users have to access resources through a GSNW server for an extensive period of time, the performance might be degraded and should be tested before using GSNW for an extensive server reroute of information.

This minimizes the need for the client systems to have the Novell client installed, and a quick and easy way to share old legacy Novell file shares or printers without having to configure Novell workstation configurations. GSNW is installed on a Windows server and the Windows server has the Client for Novell installed and accesses the Novell resource, and then redistributes the shared access to Windows clients .

To install GSNW, perform the following steps:

1. After File and Print Services for NetWare has been installed on a Windows 2000 or Windows 2003 server, click on Start, Settings, Control Panel, and then double-click on GSNW.

2. Click on Settings, and then click on Enable Gateway.

3. Type in a username that will be the default access path from the Windows server to the Novell server. If the user account is in eDirectory or NDS, enter the username as .username.organizationalunit.organization format.

4. Enter in the password for the selected user account, again enter the same password into the Confirm Password box, and then click OK.

5. Type the Windows share name as you want this Novell network share to appear in Windows, click OK.

6. If you want to apply new permissions for Windows users to this share, click on Permissions and choose the Type of Access and the Access Through the Share information. Click OK to select the settings.

A Security Limitation for GSNW

Because all users route through the GSNW server using the same logon and password, usually a supervisor type password is used. However, this becomes a security limitation for GSNW because all users routing through GSNW will have the same access name and password to the Novell system, so permissions should be applied in step 6.

GSNW Will Not Work on the Same Server That Is Running MSDSS

GSNW will not work on the same server that is running MSDSS, so if directory synchronization will take place on a network, make sure it is also not going to be the GSNW server.

Using the File Migration Wizard to Migrate Files

A utility that is installed with the MSDSS tool is the File Migration Utility. The File Migration Utility migrates files from one server to another, particularly from Novell servers to Windows servers while preserving filenames, file paths, access control lists (ACLs), and user and directory permission information. The File Migration Wizard simplifies the process of moving information from one server to another in an ability to migrate information without having to manually track file permissions or to rebuild configuration settings.

Build a Brand New Microsoft Windows Server

A common practice for organizations replacing Novell servers with Microsoft Windows servers is to build a brand new Microsoft Windows server and then run the File Migration Wizard to extract information from a Novell server and replace the information onto a Windows server. Upon completion of the file migration, a drive mapping is changed in the network logon script remapping the user drive from a Novell volume to a Microsoft Windows share.

To run the File Migration Wizard, do the following:

1. Launch the File Migration Wizard by selecting Start, Programs, Administrative Tools, File Migration Utility.

2. For Step 1 Mappings, enter the name of a log file that will be used to record the server, drive, and configuration mappings. This is extremely helpful in creating a prototype test migration in a lab environment that can then be replicated in a production environment using the exact same settings. Choose Next to continue.

3. For Step 2 Security Accounts, if not already logged on to Novell, click on the Log On to Novell button and enter in a valid account (typically the supervisor account) that has full access to the Novell server information. Click Next.

4. For Step 3 Source and Target, choose the Novell server volume that is the source of information to be migrated, and select the Microsoft Windows share that is the target of the migrated information as shown in Figure 17.5. Choose Next to continue.

   Figure 17.5. Selecting source and destination servers.

   

5. For Step 4 Log Settings, choose to log the migration process. During a test migration during the prototype phase, select high log detail to view all migration change information. If after a test migration all processes are validated in the test, you can choose to log at a low or medium level to save disk space on the migration process. Click Next to continue.

6. Step 5 Scan performs a test to validate whether there will be any failures during the migration process. The scan tests for available disk space, read and write permissions, matching account information, and proper configuration settings between the source and target servers. Click Next to continue.

7. Step 6 Migrate performs the migration. If there were any errors in the test migration process, the errors will be reported and a warning will be displayed onscreen to prevent a migration process from occurring with undesired results. If the migration test phases are successful, the migration will proceed with a progress displayed similar to the one shown in Figure 17.6.

   Figure 17.6. File migration process proceeding as initiated.