Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 The Upgrade Manager Dialog Boxes

How To...

 Restore a Server

Tools and Utilities

 Upgrade Tools

 Upgrade Utilities


Contents-All Windows NT Server Upgrade Manager Help Topics
Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 What Is Windows NT Server Upgrade Manager?

 Express or Custom Upgrade?

 The Upgrade Manager Dialog Boxes

 The Windows NT Server Upgrade Manager Dialog Box

 The Express Upgrade Dialog Box

 The Custom Upgrade Dialog Box

 The Configure Tools Dialog Box

 The Save As Dialog Box

How To...

 Restore a Server

 Starting Upgrade Manager

 Viewing the ADVISORY.TXT file

 Performing an Express Upgrade

 Performing a Custom Upgrade

 Configuring the Upgrade Tools

 Saving a Configuration File

Tools

 Upgrade Tools

 Convert Partition

 Restore Environment

 Restore User Accounts

 Map to Trusted Domain Accounts

 Restore Permissions

 Restore Scheduled Commands

 Convert Macintosh Volumes

 Verify Permissions

 Upgrade Utilities

 Aclcomp

 Aclconv

 Convert

 Portuas

 Restenv

 Sfmconv

 Userconv


Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 What Is Windows NT Server Upgrade Manager?

 Express or Custom Upgrade?

 The Upgrade Manager Dialog Boxes

How To...

 Restore a Server

Tools and Utilities

 Upgrade Tools

 Upgrade Utilities


What Is Windows NT Server Upgrade Manager?

Windows NT Server Upgrade Manager allows you to take server files and configuration information from a LAN Manager server, and restore them to a computer running Windows NT Server.  Both clone and in place upgrades are supported.

Windows NT Server Upgrade Manager automates a large part of the upgrade process.  It runs the Windows NT Server upgrade utilities in a specific order, eliminating the need to memorize steps or commands.  It is configurable, allowing you to customize your upgrade as needed for your particular server configuration.

Windows NT Server Upgrade for LAN Manager:

Converts partitions.  It can convert FAT, HPFS, or HPFS386 volumes to NTFS volumes, without losing data.

Restores the server environment.  It reads a data file created by the LAN Manager backenv utility and uses it to restore server configuration information under Windows NT Server.

Restores user accounts.  It can merge a LAN Manager user account database into an existing Windows NT Workstation or Windows NT Server security database by reading information directly from the NETACC.BKP file created by the LAN Manager backacc utility. It can also restore global group and user account information (for example, passwords, minimum password age and length, and logon script names).

Maps user accounts.  It enables mapping of LAN Manager user accounts to existing Windows NT Server accounts in a local or a trusted domain.  Where one user has more than one user account in an enterprise, it allows the merging of user accounts. This allows you to more easily implement a trusted domain structure that allows each user network-wide access from a single user account.

Restores permissions.  It uses an ACL information file created by the LAN Manager backacc utility to apply equivalent permissions to the files and directories on newly created or converted NTFS volumes.

Restores scheduled commands.  It restores at commands by executing RESTAT.CMD, a command file created by the LAN Manager backat utility.

Converts Macintosh volumes.  It restores Macintosh volumes to a Windows NT Server computer. To convert Services for Macintosh, you must establish the volume structure on the Windows NT Server computer exactly as it was under LAN Manager. All volumes must be NTFS.

Verifies permissions.  It compares the text output of the acllist utility with file settings on the Windows NT Server computer, and documents all discrepancies.

See Also

Starting Upgrade Manager


clone upgrade

An upgrade where server files and configuration information are transferred from a LAN Manager server to another computer (the clone) that runs Windows NT Server.  The clone can be an x86- or RISC-based computer. This is the recommended method of upgrading.


in place upgrade

An upgrade performed in place on a LAN Manager server, converting it to run Windows NT Server.  Note that the computer used for an in place upgrade must meet the hardware requirements for a Windows NT Server installation.


What Is Windows NT Server Upgrade Manager?
Express or Custom Upgrade?

With Windows NT Server Upgrade Manager, you have the option of performing an Express upgrade or a Custom upgrade.

The Express option lets Upgrade Manager determine and configure the appropriate upgrade steps.  Using the Express option is strongly recommended.

When performing an Express upgrade, Upgrade Manager analyzes the results returned by LAN Manager Upgrade Manager, determines the upgrade steps that should be performed, and then displays the appropriate tools, configured and arranged in the appropriate sequence.  (You still have the option to modify the displayed settings.)  In most cases, the Express upgrade is the recommended method of upgrading.

The Custom option expects that you will determine and configure the appropriate upgrade steps.

When performing a Custom upgrade, you can choose and configure upgrade steps at the time of the upgrade, or you can run an upgrade that has been predefined in a configuration file.  (This could be the default WNTUPMGR.INI file, or another configuration file that you specify.)

Note  We strongly recommend that you choose the Express upgrade option, as Custom assumes that you will do many tasks manually that would have been automatic under Express. Use Custom only if advised to do so by Microsoft Product Support or if you have special requirements. You should read and have a thorough understanding of everything in the Upgrade Guide.

See Also

Starting Upgrade Manager


Express upgrade

The Express option lets Upgrade Manager determine and configure the appropriate upgrade steps.  In most cases, Express upgrade is the recommended method of upgrading.

When performing an Express upgrade, Upgrade Manager analyzes the results returned by LAN Manager Upgrade Manager, determines the upgrade steps that should be performed, and then displays the appropriate tools, configured and arranged in the appropriate sequence.  (You still have the option to modify the displayed settings.)


Custom upgrade

The Custom option expects that you will determine and configure the appropriate upgrade steps.

When performing a Custom upgrade, you can choose and configure upgrade steps at the time of the upgrade, or you can run an upgrade that has been predefined in a configuration file.  (This could be the default WNTUPMGR.INI file or another configuration file that you specify.)


Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 The Upgrade Manager Dialog Boxes

 The Windows NT Server Upgrade Manager Dialog Box

 The Express Upgrade Dialog Box

 The Custom Upgrade Dialog Box

 The Configure Tools Dialog Box

 The Save As Dialog Box

How To...

 Restore a Server

Tools and Utilities

 Upgrade Tools

 Upgrade Utilities


The Windows NT Server Upgrade Manager Dialog Box

In the Windows NT Server Upgrade Manager dialog box, you can choose either an Express upgrade or a Custom upgrade.  You can also display the ADVISORY.TXT file, which was created by LAN Manager Upgrade Manager.

For more information about this dialog box, choose one of the following buttons.

 Express Upgrade Button

 Custom Upgrade Button

 ADVISORY.TXT Button

 Help Button

 Exit Button


Express Upgrade Button

Choose the Express Upgrade button when you want Upgrade Manager to determine and configure the appropriate upgrade steps.  In most cases, Express Upgrade is the recommended method of upgrading.

The Express Upgrade button displays the Express Upgrade dialog box, from which you can run an upgrade based on Windows NT Server Upgrade Manager's analysis of the results returned by LAN Manager Upgrade Manager.

Windows NT Server Upgrade Manager determines the upgrade steps that should be performed, and then in the Express Upgrade dialog box displays the appropriate tools, configured and arranged in the appropriate sequence.  (You still have the option to modify the displayed settings.)


Custom Upgrade Button

Choose the Custom Upgrade button when you want to perform an upgrade as defined by the WNTUPMGR.INI configuration file, or when you want to select and configure the appropriate upgrade steps yourself.

The Custom Upgrade button displays the Custom Upgrade dialog box, with the upgrade tools configured and arranged in the sequence that is defined in the WNTUPMGR.INI file. In the Custom Upgrade dialog box you can either run the upgrade as predefined by the WNTUPMGR.INI file, or you can select and configure the upgrade tools yourself, and then run the upgrade as you have defined it.


ADVISORY.TXT Button

The ADVISORY.TXT button starts the Notepad accessory and opens the ADVISORY.TXT file.

The ADVISORY.TXT is a text file created by LAN Manager Upgrade Manager when it runs the backenv utility.  ADVISORY.TXT contains recommendations for the Windows NT Server installation process, such as network card settings, required memory, and so on.


Help Button

The Help button provides access to online Help.  It displays the table of contents for Windows NT Server Upgrade Manager Help.


Exit Button

The Exit button cancels the upgrade, and then quits Windows NT Server Upgrade Manager.


The Express Upgrade Dialog Box

Use the Express Upgrade dialog box when you want Upgrade Manager to determine and configure the appropriate upgrade steps.  In most cases, the express upgrade is the recommended method of upgrading.

Windows NT Server Upgrade Manager analyzes the results returned by LAN Manager Upgrade Manager, determines the upgrade steps that should be performed, and then in the Express Upgrade dialog box displays the appropriate tools, configured and arranged in the appropriate sequence.  (You still have the option to modify the displayed settings.)

For more information about the Express Upgrade dialog box, choose one of the following buttons.

 Upgrade Tool Schedule

 Upgrade Status

 Start Button

 Restart Button

 Pause Button

 Continue Button

 Exit Button

 Help Button

 Configure Button

 About Button

See Also

Performing an Express Upgrade


Upgrade Tool Schedule

The Upgrade Tool Schedule displays, in sequence, the upgrade tools that will be run.  Colors indicate the status of the each tool.

Gray text indicates a tool that has already run.

Blue text indicates either a tool that is running, or a tool that, when the Start or Continue buttons are chosen, will be run next.

Black text indicates a tool that has not yet run.

When a question mark (?) appears as part of the text for a listed tool, that tool requires configuration before it is run.  Usually, a drive letter must be specified in place of the variable (?).


Upgrade Status

The Upgrade Status box displays status information, including error messages and start and stop times for each execution sequence.

Note:	This information is also saved in a log file, WNTUPMGR.LOG.  The restenv, userconv, and aclcomp utilities also generate their own log files.


Start Button

Choosing the Start button begins the upgrade as defined in the Upgrade Tool Schedule.  The tools run in sequence, beginning with the first tool in the list.

Note:	When an upgrade has not yet been started, the Start button is displayed.  Once the Start button has been chosen, it is replaced by the Restart button.


Restart Button

When an upgrade has already been started, choosing the Restart button returns to the first tool in the Upgrade Tool Schedule list.  The upgrade starts again from the beginning.

Note:	When an upgrade has not yet been started, the Start button is displayed.  Once the Start button has been chosen, it is replaced by the Restart button.


Pause Button

Choosing the Pause button pauses an upgrade.  The tool currently running completes execution, and then the upgrade is paused.

Note:	The Pause button is displayed when an upgrade is running.  When an upgrade has been paused, the Continue button is displayed in its place.


Continue Button

Choosing the Continue button resumes execution of a paused upgrade utility.

By default, Upgrade Manager automatically pauses after each utility runs.  To change this, choose the Configure button to open the Configure Tools dialog box, select a tool from the Upgrade Schedule, and then select or clear the Pause After Execution option.

Upgrades can also be paused by the user, by choosing the Pause button while the upgrade is running.

Note:	The Continue button is displayed when an upgrade is paused.  When an upgrade is running, the Pause button is displayed in its place.


Configure Button

The Configure button displays the Configure Tools dialog box, which you use to modify the Upgrade Tool Schedule.

This configuration can then be run immediately and/or saved for future use.


About Button

The About button provides version, copyright, and trademark information for Microsoft Windows NT Server Upgrade Manager.


The Custom Upgrade Dialog Box

When you open the Custom Upgrade dialog box, it loads a configuration file and displays the upgrade tools as scheduled by that file.

When you start Upgrade Manager by typing wntupmgr from a command line and then choosing the Custom Upgrade button in the Windows NT Server Upgrade Manager dialog box, the WINTUPMGR.INI file is loaded and the Custom Upgrade dialog box is displayed.

When you start Upgrade Manager by typing wntupmgr filename.ext, from a command line, the specified configuration file is loaded and the Custom Upgrade dialog box is immediately displayed.  (In this case, the Windows NT Server Upgrade Manager dialog box does not appear.)

From the Custom Upgrade dialog box you can either run the upgrade as defined by the loaded configuration file, or you can configure the upgrade tools yourself, and then run the upgrade as you have defined it.  For most Custom upgrades, you will need at a minimum to customize the command lines for some of the scheduled tools before executing the upgrade.

For more information about the Custom Upgrade dialog box, choose one of the following buttons.

 Upgrade Tool Schedule

 Upgrade Status

 Start Button

 Restart Button

 Pause Button

 Continue Button

 Exit Button

 Help Button

 Configure Button

 About Button

See Also

Performing a Custom Upgrade


The Configure Tools Dialog Box

Use the Configure Tools dialog box to modify the Upgrade schedule or Upgrade utility options. This configuration can then be run immediately and/or saved for future use.

For more information about the Configure Tools dialog box, choose one of the following buttons.

 Available Utilities

 Upgrade Schedule

 Upgrade Schedule Details

 Pause After Execution

 Reboot After Execution

 Command Line

 Insert Button

 Remove Button

 OK Button

 Cancel Button

 Save As Button

 Help Button

See Also

Configuring the Upgrade Tools


Available Utilities

This box lists the available upgrade tools.


Upgrade Schedule

This box displays the current upgrade configuration.  It shows the upgrade tools, arranged in the sequence in which they will run.

One tool at a time can be selected from the Upgrade Schedule.  The selected tool can then be configured using the options in the Upgrade Schedule Details box.

When a question mark (?) appears as part of the text for a listed tool, that tool requires configuration before it is run.  Usually, in the Command Line box, a drive letter must be specified in place of the variable (?).


Upgrade Schedule Details

The options displayed in this box apply to the upgrade tool that is currently selected in the Upgrade Schedule.


Pause After Execution

This option applies to the upgrade tool that is currently selected in the Upgrade Schedule.

When an upgrade tool is set for Pause After Execution, it pauses Windows NT Server Upgrade Manager after executing.


Reboot After Execution

This option applies to the upgrade tool that is currently selected in the Upgrade Schedule list.

When an upgrade tool is set for Reboot After Execution, it reboots the system after executing.  After the reboot, Windows NT Server Upgrade Manager resumes.


Command Line

The Command Line applies to the upgrade utility that is currently selected in the Upgrade Schedule.  The Command Line box displays the command syntax that will be issued when Windows NT Server Upgrade Manager runs that upgrade tool.  To modify this command, edit the text in the Command Line box.

When a question mark (?) appears as part of the command for a selected upgrade tool, that tool requires configuration.  Usually, a drive letter must be specified in place of the variable (?).


Insert Button

The Insert button adds to the Upgrade Schedule the tool that corresponds to the utility that is currently selected in the Available Utilities box. The added tool is inserted immediately above the current selection in the Upgrade Schedule box.

Note:	To insert a tool at the end of the Upgrade Schedule list, select the first blank line below the last tool on the Upgrade Schedule.


Remove Button

The Remove button removes the selected upgrade tool from the Upgrade Schedule.


OK Button

The OK button exits the Configuration Tools dialog box and retains any changes that were made to the Upgrade Schedule.

As appropriate, the Express Upgrade or the Custom Upgrade dialog box returns, and the Upgrade Tool Schedule displays the new upgrade configuration.


Cancel Button

The Cancel button exits the Configuration Tools dialog box and discards any changes that were made to the Upgrade Schedule.

As appropriate, the Express Upgrade or the Custom Upgrade dialog box returns, and the Upgrade Tool Schedule is unchanged.


Save As Button

Choosing the Save As button opens the Save As dialog box, where you can save as a configuration file the upgrade configuration displayed in the Upgrade Schedule box.

Later you can load that upgrade configuration by specifying that file when starting Upgrade Manager (by typing wntupmgr filename.ext).


The Save As Dialog Box

Use the Save As dialog box to save the current upgrade configuration as a configuration file.  That upgrade configuration can then be used for future upgrades.

For information about the Save As dialog box, choose one of the following buttons.

 File Name

 Save File As Type

 Directories

 Drives

 OK Button

 Cancel Button

 Network Button

See Also

Saving a Configuration File


File Name

Type a filename, and optionally a filename extension, in the File Name box.  If you do not specify a filename extension, the .INI filename extension is used.

Note:	Usually, you should not enter the filenames WNTUPMGR.EXP or WNTUPMGR.INI, so that you avoid overwriting (respectively) the express upgrade configuration file and the default custom upgrade configuration file.


Save File As Type

Optionally, in the Save File As Type box, select a filename extension for the file you are saving.

Note:	This is usually not necessary.  If you do not specify a filename extension, the .INI filename extension is used.


Directories

If the displayed directory path is not the preferred storage location for the file you are saving, select a different path in the Directories box.


Drives

If the displayed disk drive is not the preferred storage location for the file you are saving, select a different drive from the list in the Drives box.


OK Button

The OK button saves the file under the specified name, in the specified location, and closes the Save As dialog box.  The Configure Tools dialog box returns.


Cancel Button

The Cancel button closes the Save As dialog box.  A file is not saved.  The Configure Tools dialog box returns.


Network Button

The Network button allows you to establish a connection to a shared network directory.  It displays the Connect Network Drive dialog box.


Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 The Upgrade Manager Dialog Boxes

How To...

 Restore a Server

 Starting Upgrade Manager

 Viewing the ADVISORY.TXT file

 Performing an Express Upgrade

 Performing a Custom Upgrade

 Configuring the Upgrade Tools

 Saving a Configuration File

Tools and Utilities

 Upgrade Tools

 Upgrade Utilities


Starting Upgrade Manager

To use Windows NT Server Upgrade Manager, you must be logged on to a user account that is a member of the Administrators local group or the Domain Admins global group.

To start Upgrade Manager

Change to the UPGRADE directory, and then from the command line type wntupmgr.

The Windows NT Server Upgrade Manager dialog box appears.  You can then choose between an express upgrade and a custom upgrade.

To start Upgrade Manager and load a predefined upgrade configuration

Change to the UPGRADE directory, and then from the command line type wntupmgr filename.ext.

Upgrade Manager skips the Windows NT Server Upgrade Manager dialog box and goes directly to The Custom Upgrade dialog box.  The Upgrade Tool Schedule box lists the upgrade configuration as defined by the specified file.

For example, you might type wntupmgr server1.ini.  The Custom Upgrade dialog box appears, and the Upgrade Tool Schedule defined in the SERVER1.INI file is displayed.

See Also

Performing an Express Upgrade

Performing a Custom Upgrade


Viewing the ADVISORY.TXT File

The ADVISORY.TXT file is created by LAN Manager Upgrade Manager when it runs the backenv utility.  ADVISORY.TXT is a text file that contains recommendations for the Windows NT Server installation process, such as network card settings, required memory, and so on. You should review this file before completing an upgrade with Windows NT Server Upgrade Manager.

To view the ADVISORY.TXT file

1.	To start Upgrade Manager, change to the UPGRADE directory, and then from the command line type wntupmgr.

The Windows NT Server Upgrade Manager dialog box appears.

2.	Choose the ADVISORY.TXT button.

Upgrade Manager starts the Notepad accessory, which then loads and displays the ADVISORY.TXT file.


Performing an Express Upgrade

Perform an Express upgrade when you want Upgrade Manager to determine and configure the appropriate upgrade steps.  (In most cases, the Express upgrade is the recommended method of upgrading.)

When you perform an Express upgrade, Windows NT Server Upgrade Manager analyzes the results returned by LAN Manager Upgrade Manager, determines the upgrade steps that should be performed, and then displays the appropriate tools, configured and arranged in the appropriate sequence. (You still have the option to modify the displayed settings.)

To perform an Express upgrade

1.	To start Upgrade Manager, change to the UPGRADE directory, and then from the command line type wntupmgr.

2.	In the Windows NT Server Upgrade Manager dialog box, choose the Express Upgrade button.

The Express Upgrade dialog box appears.  Windows NT Server Upgrade Manager has analyzed the results returned by LAN Manager Upgrade Manager, determined the upgrade steps that should be performed, and now lists the tools in the appropriate sequence in the Upgrade Tool Schedule box.

3.	Examine the Upgrade Tool Schedule to make sure the upgrade steps are appropriate.  In particular, check steps that specify drive letters. Variable drive letters are noted with a question mark (?). Also check steps that already specify drive letters to make sure the letters are correct.

If necessary, modify the Upgrade Tools Schedule by choosing the Configure button and completing the Configuration Tools dialog box that appears.  When the upgrade tools configuration is modified as necessary, choose the OK button to return to the Express Upgrade dialog box.

4.	From the Express Upgrade dialog box, begin the upgrade by choosing the Start button.

Throughout the rest of this upgrade, the Upgrade Status box displays status information, including error messages and start and stop times for each execution sequence.

5.	If the upgrade pauses after executing a tool (an option that you can select or clear in Step 2, in the Configuration Tools dialog box), choose the Continue button.  The upgrade will continue.

Repeat as necessary after each pause, until the upgrade completes.

See Also

The Express Upgrade Dialog Box

Starting Upgrade Manager

Configuring the Upgrade Tools


Performing a Custom Upgrade

Perform a Custom upgrade when you want to choose and configure upgrade steps at the time of the upgrade, or when you want to run an upgrade that has been predefined in a configuration file.

To perform a custom upgrade

1.	Start Upgrade Manager.

You can start Upgrade Manager and load WNTUPMGR.INI.  To do this, change to the UPGRADE directory, from the command line type wntupmgr, and then in the Windows NT Server Upgrade Manager Dialog box choose the Custom Upgrade button.

Or, you can start Upgrade Manager and load a selected configuration file.  To do this, change to the UPGRADE directory, and then from the command line type wntupmgr filename.ext.

In both cases, the Custom Upgrade dialog box appears.

2.	Examine the Upgrade Tools Schedule to make sure the upgrade steps are appropriate.  In particular, check steps that specify drive letters.

If necessary, modify the Upgrade Tools Schedule by choosing the Configure button and completing the Configuration Tools dialog box that appears.  When the upgrade tools configuration is modified as necessary, choose the OK button to return to the Custom Upgrade dialog box.

Note:	For most Custom upgrades, you will need at a minimum to customize the command lines for some of the scheduled tools before executing the upgrade.

3.	From the Custom Upgrade dialog box, begin the upgrade by choosing the Start button.

Throughout the rest of this upgrade, the Upgrade Status box displays status information, including error messages and start and stop times for each execution sequence.

4.	If the upgrade pauses after executing a tool (an option that you can select or clear in Step 2, in the Configuration Tools dialog box), choose the Continue button.  The upgrade will continue.

Repeat as necessary after each pause, until the upgrade completes.

See Also

The Custom Upgrade Dialog Box

Starting Upgrade Manager

Configuring the Upgrade Tools

Saving a Configuration File


Configuring the Upgrade Tools

Optionally, you can modify the configuration of the Upgrade Schedule and the Upgrade tools.  You can add or delete tools from the schedule, or change the options or syntax of individual utilities. This configuration can then be run immediately, saved for future use, or both.

To configure the upgrade tools

1.	Start Upgrade Manager, and then choose either the Express Upgrade button or the Custom Upgrade button.

2.	Choose the Configure button.

3.	To add an upgrade tool to the Upgrade Schedule, first determine where the tool will be inserted by selecting a tool from the list in the Upgrade Schedule, or by selecting the empty line below the lowest tool in the list.  The added tool will be inserted immediately above this selection.

Then select a tool from the list in the Available Utilities box, and choose the Insert button. The selected tool is added to the Upgrade Schedule.

4.	To remove an upgrade tool from the Upgrade Schedule, select a tool from the list in the Upgrade Schedule, and then choose the Remove button.

5.	To configure a scheduled upgrade tool, select a tool from the list in the Upgrade Schedule box, and then set the Upgrade Schedule Details options.  Edit the text in the Command Line box as necessary, and select or clear the Pause After Execution and Reboot After Execution options.

6.	Optionally, to save this configuration for future use, choose the Save As button and complete the Save As dialog box that appears.

7.	To complete the current upgrade using this configuration, choose the OK button, and then in the dialog box that reappears (as appropriate, the Express Upgrade or Custom Upgrade dialog box), choose the Start button.

Or, to cancel and exit the upgrade process, choose the Cancel button, and then in the dialog box that reappears (as appropriate, the Express Upgrade or Custom Upgrade dialog box), choose the Exit button.

See Also

The Configure Tools Dialog Box

Saving a Configuration File


Saving a Configuration File

Optionally, you can save an upgrade configuration as a configuration file.

To save an upgrade configuration

1.	Start Upgrade Manager, and then choose either the Express Upgrade button or the Custom Upgrade button.

2.	Choose the Configure button.

3.	In the Configure Tools dialog box, configure the Upgrade Schedule and each of the upgrade tools in that schedule.

4.	From the Configure Tools dialog box, choose the Save As button.

5.	If necessary, establish a new network connection to a shared network directory on another server by choosing the Network button, and then completing the Connect Network Drive dialog box that appears.

Do this only if you want to save the file to a shared network drive to which there is not already a connection.

6.	Optionally, change the path of the saved file by making selections in the Drives and Directories boxes.

7.	Enter a filename in the File Name box.

If you omit a filename extension from the filename, when the file is saved the system will automatically add the filename extension that is selected in the Save File As Type box.

Note:	Usually, you should not enter the filenames WNTUPMGR.EXP or WNTUPMGR.INI, so that you avoid overwriting (respectively) the express upgrade configuration file and the default custom upgrade configuration file.

8.	From the Save As dialog box, choose the OK button.

The configuration is saved as a file.  The Configure Tools dialog box returns.

9.	From the Configure Tools dialog box, either proceed with the current upgrade, or cancel and exit.

See Also

The Save As Dialog Box

Configuring the Upgrade Tools

Starting Upgrade Manager


Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 The Upgrade Manager Dialog Boxes

How To...

 Restore a Server

Tools and Utilities

 Upgrade Tools

 Convert Partition

 Restore Environment

 Restore User Accounts

 Map to Trusted Domain Accounts

 Restore Permissions

 Restore Scheduled Commands

 Convert Macintosh Volumes

 Verify Permissions

 Upgrade Utilities


Convert Partition

After installing Windows NT Server, at least one partition (the partition that contains Windows NT Server) is NTFS.  Each partition that is to contain secure files must be formatted as NTFS. You can convert the remaining partitions using the Convert Partition tool, which runs the Windows NT convert utility.

The convert utility changes FAT, HPFS, and HPFS386 partitions to NTFS, without losing data. Convert operates on any volume to which it can gain exclusive access. If the utility cannot gain exclusive access to a volume, it offers to convert the next time you start your system. When you select this option, convert adds appropriate entries to the Windows NT Registry to force conversion after rebooting.

When convert runs during system initialization, it uses a version of convert called autoconv. Autoconv automatically calls autochk (the system initialization version of chkdsk).

Convert has the following requirements:

Drives must be local.

Remote drives are not supported.

Volumes must be consistent.

Chkdsk must not report errors on a volume. If convert can gain exclusive access to the volume during system initialization, convert (autoconv) invokes autochk (without the /f parameter) and does not proceed if errors are found.

Free space must be adequate.

Some free space is necessary to run convert. The utility estimates the minimum amount of free disk space needed to complete a conversion and only proceeds if adequate free space is available. If a conversion fails because of a lack of free space, the conversion stops, leaving the volume in its original preconversion state.

If convert fails because of insufficient memory, it will leave the volume in a valid state. Chkdsk may be needed to restore the volume to a consistent state, but no data will be lost. Convert is able to perform without a swap file.

Convert preserves all user file data and extended attributes on the volume. Internal file-system data is not preserved. In particular, the FAT extended attributes file, EADATA.SF, is discarded; however, its contents are preserved as extended attributes attached to files on the NTFS volume. Convert also preserves volume labels.

Convert gives ownership of the root directory and of all converted files and directories to the Administrators group. It also creates an ACL for each file and directory that grants full access to Everyone. HPFS386 permissions are discarded and must be reassigned using the aclconv utility.

The conversion process consists of two stages: preparation and conversion. Each stage performs a specific transformation on a volume.

Preparation

This stage prepares the current file system. Usually this involves shuffling the file system structure around in order to create zones of free space at specific physical locations on the volume. This stage only creates free space in those sectors that are absolutely required by the target file system. Data structures that should be in certain locations for performance reasons are not taken into account.

Preparation consists of three steps:

1.	Estimating free space.

If 50% or more of the disk is free, convert assumes that free space is adequate. Otherwise it gathers information (the number of files, number of extended attributes, and so on) which it then uses to estimate the amount of free space required for conversion. Conversion proceeds only if enough free space is available.

2.	Remapping free space.

Convert creates free space at specific locations. This is done by moving the data at those locations to other places (currently free) on disk. If a failure occurs during this process, no harm is done because the existing file system data structures, such as links and directories, have not been modified.

3.	Overwriting the file systems data structures to reflect space changes.

If a failure occurs during this process, autochk can restore the volume to a consistent state without loss of data.

Conversion

This stage converts the volume to the specified file system. During this process, all target file system data structures are created in the free space created in the preparation stage, so that if a failure occurs the volume is still consistent and convert can start over.

At the end of the process, the NTFS boot sector is written to the proper places on the drive. If a failure occurs at this point, autochk restores the disk to the original file system with its data intact.

See Also

Convert


Restore Environment

After converting volumes to NTFS, you can restore environment parameters to the destination Windows NT Server computer. This is accomplished with the Restore Environment tool, which runs the restenv utility.

Restenv reads the LMBAKENV.DAT file created by the LAN Manager backenv utility, and restores applicable settings on the Windows NT Server computer. The utility ignores settings that dont apply under Windows NT.

Restenv generates a log file, RESTENV.LOG, that shows what settings were detected and what settings changed. Restenv also indicates what settings it did not change and why. If a service, protocol, or setting listed in LMBAKENV.DAT does not exist on the destination Windows NT Server computer, the log indicates this.

To retain LAN Manager file replication settings under Windows NT Server, you must create a special service account called REP on the Windows NT Server primary domain controller prior to running the Windows NT Server Upgrade Manager on the server you are upgrading. If the computer running Windows NT Server is aware of this service account (the Upgrade Manager transfers this account if previously present on the domain controller being upgraded), the restenv utility restores file replication. Otherwise, file replication configuration is not preserved.

In addition, restenv configures the Windows NT Schedule service to start automatically, so that you can reinstate at commands.

The following information shows how restenv handles various LMBAKENV.DAT parameters.

[workstation]

Writes applicable settings to Registry and attempts to start service.

[server]

Writes applicable settings to Registry and attempts to start service.

[ups]

Writes applicable settings to Registry and sets service to start automatically. If UPS command file is in the UPGRADE directory, copies it to \systemroot\SYSTEM32\DRIVERS\ETC.

[netlogon]

Writes applicable settings to Registry and attempts to start service.

[alerter]

Attempts to start service.  (No settings applicable.)

[replicator]

Writes applicable settings to Registry and sets service to start automatically. Assigns permissions to REPL$ and restores replication and logon script paths under Windows NT. If the logon script path and/or the replication paths are relative, restenv moves the appropriate directories and files and modifies ACLs appropriately. These changes are recorded in the file RESTENV.DAT, which is used by aclcomp to verify proper ACLs.

Also moves import server accounts from the LAN Manager group rep to the Windows NT Server group Replicator.

[remoteaccess]

Writes applicable settings to Registry if Remote Access Service is installed.

[SNMP]

Writes applicable settings to Registry if SNMP installed. Attempts to start service.

[timesource]

If timesource server, restenv adds the key TimeSource to the Registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters.

[protocol1, 2...n]

Checks for existing protocol. If NetBEUI is installed, restenv upgrades settings. For TCP/IP, AppleTalk, and DLC protocols, restenv compares Windows NT settings with the original LAN Manager values. If a discrepancy exists, restenv notes it in RESTENV.LOG. Note that the value of one TCP/IP parameter (ScopeID) is transferred.

[netcard1,2]

In RESTENV.LOG, lists adapter card driver name for LAN Manager and Windows NT configurations.

[shares]

Compares shares listed in LMBAKENV.DAT with existing shares on Windows NT Server. If there is a mismatch between an existing and a requested sharename and/or pathname, restenv writes an error message to RESTENV.LOG but does not make a change to the share. If no conflicts exist, restenv creates equivalent shares. Note that share permissions are not ported.

[uses]

Compares persistent connections listed in LMBAKENV.DAT with existing connections. If there is a drive letter conflict, writes an error message to RESTENV.LOG but does not make a change to the connection. If no conflicts exist, restenv creates the network connections under Windows NT.

[countryinfo]

Checks to see if country code in LMBAKENV.DAT matches locale specified during Windows NT installation. Writes country code, country name, and locale code to the log file and indicates if existing code is correct.

See Also

Restenv


Restore User Accounts

The restore User Accounts tool runs the portuas utility, which merges a LAN Manager user accounts system (UAS) database into an existing Windows NT Server security database. It does this by reading information from the LAN Manager NETACC.BKP file, generated by the LAN Manager backacc utility.  By default, portuas converts all users and groups.  However, you can also convert individual user accounts using portuas with the /u option.

Portuas conversion consists of the following steps:

Opening and validating the LAN Manager UAS database.

Reading each group in the UAS database.

Adding the group to the Windows NT security database using the NetGroupAdd API, if a group does not exist under Windows NT Server. If the group already exists (for example, the default ADMIN group), portuas updates the group comment using the NetGroupSetInfo API.

If the group name matches an existing user name or local group name, portuas prompts the user to decide whether to change the conflicting name, leave it as is, or skip it entirely.

Copying the group name into a group table entry so that portuas can refer to the group later to add members.

Reading each user in the UAS database and adding the user to the security database using the NetUserAdd API. If the same user exists in the security database, portuas updates the user attributes using the NetUserSetInfo API.

Adding users to appropriate groups using the NetGroupAddUser API.

Setting global account policies, such as minimum password length, in the UAS database.

Closing the UAS database.

User Account Information

Note that portuas overwrites with LAN Manager account information the Windows NT Guest and Administrator user accounts.

The following shows how LAN Manager user account information is mapped to Windows NT Server.

Account Name maps to Username

Password maps to Password

Full Name maps to Full Name

Comment maps to Description

Disable Account maps to Account Disabled

User Comment maps to User Comment (accessible only from the Net User command)

Country Code maps to Country Code (accessible only from the Net User command)

Privilege Level does not directly apply to Windows NT.  See "Groups," below.

Operator Privileges does not directly apply to Windows NT.  See "Groups," below.

Logon Hours maps to Logon Hours

Account Expires maps to Account Expires

Valid Workstations maps to Logon Workstations

Logon Server does not apply to Windows NT

Logon Script Path maps to Logon Script Name

Home directory path maps to Home directory path

User Storage Limit does not apply to Windows NT

Groups

The following shows how portuas maps default LAN Manager groups to Windows NT Server. Non-default groups become new domain groups in the domain user accounts database.

Admins maps to Domain Admins

Users maps to Domain Users

Guests maps to Domain Guests

Servers maps to Servers

Account Operators maps to Account Operators

Print Operators maps to Print Operators

Server Operators maps to Server Operators

Comm Operators does not apply to Windows NT

Local does not apply to Windows NT

If a LAN Manager account specifies a Macintosh Primary Group, portuas transfers this designation. A primary group is relevant for Windows NT Services for Macintosh and for POSIX applications.

Merging Multiple User Account Databases

Multiple LAN Manager user account databases (NETACC.BKP files) can be merged into a single Windows NT Server user account database. To do this, each NETACC.BKP (or NET.ACC) file from the LAN Manager domain that you want to merge must be copied to the Windows NT Server domain that it is to be merged with. (Note that you can give each file a different name.) When the NETACC.BKP files are in place, run the portuas utility separately on each file to merge it with the Windows NT Server user account database.

If a user account occurs in more than one of the NETACC.BKP files, the last accounts information will supersede information in previous accounts. Thus, if MILESL has an account in two LAN Manager domains that have been merged into a single Windows NT Server domain, MILESL will have a single account with the password that applies to the most recently converted user account database.

Use caution here because any groups from the LAN Manager domains that have the same names will be merged into a single group with that name in the Windows NT Server domain. If this is not what you want, you can merge a NETACC.BKP file, rename the group whose name matches that in another LAN Manager domain, and then merge the next NETACC.BKP file. You can continue this until all of the LAN Manager user account databases have been merged.

See Also

Portuas

Map to Trusted Domain Accounts


Map to Trusted Domain Accounts

The Map to Trusted Domain Accounts tool runs the userconv utility, which then displays the User Conversion dialog box.

Userconv enables you to map LAN Mananger user accounts to accounts in trusted domains. It is used in place of the portuas utility. Userconv execution consists of four stages: preparation, account and local group mapping, conversion, and output file creation.

Preparation

After you invoke the utility and select an appropriate NETACC.BKP file, userconv loads NETACC.BKP into memory and checks the network for trusted domains. If trusted domains exist, userconv displays them in the Trusted Domain box. Userconv then browses the local domain for groups and users and displays them in the LAN Manager Accounts dialog box.

When you select a local or trusted domain, userconv browses that domain for groups and accounts. This information is retained in memory should a user reselect the domain later in the session.

Account and Local Groups Mapping

When you choose the Auto Map button, userconv checks for matches between users and groups in the selected domain. It also records associations created when you choose Manual Map or add a local group. Userconv does not implement these changes until you choose the Convert button.

Conversion

Userconvs first step in this stage is to create local groups under Windows NT Server. Before creating groups, it checks that they dont already exist.

Userconv then checks to see if each user in each group is mapped to an existing Windows NT account. If so, it retains the user in the group, using his or her Windows NT user account name. If not, the name is dropped.

For each user name specified in that file, it checks to see if mapping was specified. If so, it replaces the LAN Manager name with the mapped Windows NT username and writes the changes to a file named ACLWORK.DAT.

File Creation

Userconv creates the files ACLWORK.DAT, USERWORK.DAT and USERCONV.LOG. ACLWORK.DAT is used by the aclconv utility to determine correct permission mapping.  USERWORK.DAT is used by the aclcomp utility. USERCONV.LOG contains a list of mapped and unmapped user accounts and local groups.

See Also

Userconv

Restore User Accounts


Restore Permissions

Restore Permissions runs the aclconv utility, which converts file and directory permissions stored in the ACLBAKdrive.ACL file to Windows NT Server.  ACLBAKdrive.ACL is created by the LAN Manager backacc utility.

Under Windows NT, each file and directory has a discretionary access control list (ACL), which identifies users and groups that are granted or denied access. ACLs are controlled by the owner of the resource. An ACL consists of a set of access control entries (ACEs); an ACE in turn consists of a user or group name and a set of associated access privileges. For each LAN Manager access permission, aclconv creates an equivalent ACE and adds it to the file or directory's discretionary ACL. Because there are no owners under LAN Manager, aclconv gives resource ownership to the Administrator account.

The Windows NT directory is excluded from processing by aclconv, to avoid overwriting the default security created by Windows NT Setup.

File and Directory Conversion

The following table shows how file and directory permissions (ACEs) map.

Read (R) becomes Read and Execute (RX)

Write (W) becomes Write (W)

Create (C) becomes Write and Execute (WX)

Delete (D) becomes Delete (D)

Execute (X) becomes Execute (X)

Change Attributes does not apply to Windows NT

Change Permissions becomes Change Permissions/Take Ownership (PO)

Yes (RWCDA) becomes Full Control (RWXDPO)

No becomes No Access

If no permissions exist for the root directory, aclconv does not change this.

Interpretation of ACLs under Windows NT is order-dependent. All Access-Denied ACEs are placed before Access-Allowed ACEs. Aclconv is consistent with this convention; it inserts new Access-Denied ACEs before the first Access-Allowed ACE in the existing ACL, and new Access-Allowed ACEs at the end.

Permission Inheritance

Under LAN Manager, if a file or directory does not have a set of permissions, it uses the parent directory's permissions. If the parent directory does not have permissions, those of the drive are used (if it is a FAT drive).

Because aclconv does not determine drive permissions, it cannot preserve this behavior. Instead, when the security information for a directory is converted, it is propagated to all the files and subdirectories in that directory that do not have explicit LAN Manager security information of their own. The subdirectories in turn propagate security information to any of their subdirectories that do not have LAN Manager permissions.

If no permissions are specified in a directory tree, aclconv does not apply permissions. Newly created files and subdirectories inherit the converted security, regardless of existing NTFS ACLs.

User and Group Conflicts

Under LAN Manager, if an ACL includes an ACE that grants some set of privileges to a group and another that grants a set of privileges to a user who is a member of that group, the user receives only those privileges explicitly granted in the user ACE. In other words, if an ACE for a particular user exists on the file, that user does not benefit from membership in any groups that have access to the file.

This means that a LAN Manager permission setting that grants a user partial access should correspond to two Windows NT ACEs: an Access-Allowed ACE that grants the privileges granted under LAN Manager, and an Access-Denied ACE that denies all access except that granted by LAN Manager. However, the Windows NT file permissions editor does not accept ACEs that deny specific access; the only Access-Denied ACE it accepts is that which denies all access.

Aclconv does not generate partial Access-Denied ACEs. Instead, in the case described above, aclconv produces an ACL that grants the user the union of privileges granted directly to the user and indirectly by membership in the group.

User ID Conversion

Aclconv uses the LookupAccountName API to determine the security identifier (SID) for an ACL. The following accounts are automatically mapped to their equivalents prior to the lookup operation.

Admin is mapped to Administrator

Admins is mapped to Administrators

Users is mapped to Users

Guests is mapped to Guests

Note that if a trusted domain is specified as a command line option, aclconv polls the specified domain for user and group information. However, the administrator and administrators accounts are always on the local system.

Changing File Location

Aclconv supports changing files from one drive to another, provided you specify a new drive. For example, if you copy files from LAN Manager drive C to Windows NT Server drive D, you must specify D as the new destination drive using the /NEWDRIVE:drive: option.

Merging LAN Manager Directory Trees

Aclconv supports moving files from two drives onto one. However, because aclconv disregards existing Windows NT ACLs, you must be careful when you merge directory trees from two LAN Manager servers under a single Windows NT Server tree.

For example, assume you have copied directories from a LAN Manager server to a clone running Windows NT Server. Then, after running aclconv, you copy directories from another LAN Manager server to the same partition on the clone and run aclconv again. If the merger combines two LAN Manager subdirectories under a common root, and there is an ACL on the root, a set of subdirectory permissions is overwritten the second time you run aclconv.

To avoid this situation, remove ACLs from the LAN Manager root directory prior to running the backacc utility. For example, if you intend to combine LAN Manager C and D drives onto a C drive under Windows NT, remove LAN Manager permissions for C:\ and D:\. This preserves all subdirectory permissions, provided these are not directories with common names. Or, copy files and directories from various LAN Manager servers onto different Windows NT Server partitions and merge directory trees after running aclconv on each partition.

See Also

Aclconv


Restore Scheduled Commands

Under LAN Manager, scheduled (at) commands are stored in the servers \LANMAN\LOGS\SCHED.LOG file, so scheduled tools are not lost if you have to restart the server. When the LAN Manager backat utility is run, it reads SCHED.LOG, interprets the commands there, and writes the commands to RESTAT.CMD (or to another user-specified filename).  If there are no entries in SCHED.LOG, no file is generated.

You restore scheduled commands on a Windows NT Server computer using the Restore Schedule tool, which runs RESTAT.CMD.  This starts the Windows NT Schedule service and then reinstates command and program schedules by writing information into the Registry.

If a filename other than RESTAT.CMD was specified when running the LAN Manager backat utility, then in the Configure Tools dialog box you must modify the command line for the Restore Scheduled Commands tool.  Replace the RESTAT.CMD entry with the appropriate filename.


Convert Macintosh Volumes

Convert Macintosh Volumes runs the sfmconv utility, which restores Macintosh volumes to a Windows NT Server computer. To convert Services for Macintosh, you must preserve Macintosh volume structure exactly as it is under LAN Manager. All partitions must be NTFS and Services for Macintosh must be installed.

Sfmconv upgrades Macintosh volumes to Windows NT as follows:

Equivalent volumes are created automatically and volume passwords are preserved.

Extended attributes are read, and the values are used, but they are not erased.

Wherever file and directory access permissions are found for the group Guests, they are duplicated for the group Everyone.

Note:	If the Services for Macintosh Guest account is not enabled under LAN Manager, sfmconv does not transfer permissions for the group Everyone.

If See Files permission is allowed for a user, group, or Everyone, but See Folders is not, then sfmconv adds the RX (read and execute) permissions.  This is necessary so that the same finder permissions will be available under Windows NT Services for Macintosh. The same is done if See Folders is allowed but See Files is not. RX is not necessary if both See Files and See Folders are allowed.

Comments attached to files and folders are preserved, as are comments attached to non-root directory volumes. Comments attached to root directory volumes (evol=e:\) are not preserved.

Note:	If the Admins group is specified in the Macintosh permission matrix and the privileges are restricted to read-only, write-only, or no access, sfmconv revokes certain administrator permissions. This is because by default, aclconv gives the Administrators group all permissions on all files and directories. Sfmconv revokes some of the permissions so that access matches the access specified by Macintosh permissions.

The Conversion Process

During conversion to Windows NT Services for Macintosh, sfmconv attempts to convert each file and directory of each volume's directory tree. Each directory is processed completely before attempting another directory. Subdirectories are processed prior to peer (sibling) directories. After file and directory information is converted, files and directories are renamed from their host names (which are MS-DOS 8.3 filenames) to Macintosh names, which can be considerably longer.

LAN Manager for Macintosh stores information about files and directories in a hidden directory (\~AFP). The ~AFP directory contains file resource forks, which contain Macintosh operating system resources, such as code, menu, font, and icon definitions. The ~AFP directory also contains FILEINFO.AFP, and the ~I directory. If AFPINFOINEAS=NO in the [macfile] section of LANMAN.INI, sfmconv uses information in the ~I directory. Otherwise, it uses information stored in the extended attributes attached to the files and directories. After sfmconv successfully converts volumes, it deletes the ~AFP and ~I directories and any other LAN Manager for Macintosh Services configuration files.

Sfmconv converts the information stored in ~AFP and ~I files, extended attributes, and various configuration files into NTFS streams. Streams are very similar to extended attributes under LAN Manager. They represent information associated with a file or a directory, but not contained within the file or directory.

Sfmconv generates the following streams:

:AFP_Resource, the resource fork for each Macintosh file that exists

:AFP_AfpInfo, information for each file and directory, such as its location and privileges

:AFP_DeskTop, application and icon information

:AFP_IdIndex, directory structure information

:Comments, comments from extended attributes, attached to each file or directory

Sfmconv also generates the file SFMCONV.DAT in UNICODE format. SFMCONV.DAT is used by aclcomp to verify file permissions on Macintosh volumes.

Required Files

SFMCONV uses the following files: SFMCONV.EXE, LANMAN.INI, SRVAUTO.PRO, CONFIG.AFP, CONFIGSV.AFP, USERINFO.AFP, USERBACK.AFP, DESKTOP.AFP, DIRID.AFP, VOLINFO.AFP, FILEINFO.AFP. If they are not available, it checks *.BAK files. Some files such as DESKTOP.AFP are optional; if they are missing, sfmconv still attempts to convert the volume.

If volume conversion is successful, sfmconv attempts to delete these files, including the *.BAK versions.

See Also

Sfmconv


Verify Permissions

Verify Permissions runs the aclcomp utility, which reads the output of the LAN Manager acllist utility and flags any file information discrepancies.

The Windows NT Server utilities convert and aclconv are used to convert partitions to the NTFS file system and to port file access permissions from the LAN Manager access control lists (ACLs) to Windows NT security IDs (SIDs) and access control entries (ACEs). Aclcomp verifies that settings are mapped according to convert and aclconv specifications.

The LAN Manager acllist utility creates an inventory file (ACLLISTdrive.DAT) that lists all resources on the specified LAN Manager drive along with their security settings. Aclcomp compares the contents of ACLLISTdrive.DAT with converted data to ensure that all settings are retained or translated appropriately to Windows NT Server. The utilities must be run once for each drive you are upgrading.

Note:	When run from the command line, the LAN Manager acllist utility generates the file ACLLIST.DAT unless another filename is specified.

If you have copied files to a drive other than that specified by ACLLISTdrive.DAT, you must direct aclcomp to check the new drive by using the /newdrive:drive option.

Aclcomp creates a report file (ACLCOMP.LOG) that lists any discrepancies in the file conversion process. File and directory information is compared against data stored in ACLLISTdrive.DAT. New files and directories, such as the \WINNT directory, are ignored.

Aclcomp checks for mismatches in the creation date and time, the last write date and time, the data checksum, file size, and file attributes. If permissions (ACLs) are present, aclcomp reports on missing users and groups and mismatches in their permissions to files or directories.

See Also

Aclcomp


Help Contents for Windows NT Server Upgrade Manager

Overview

 About Upgrade Manager

 The Upgrade Manager Dialog Boxes

How To...

 Restore a Server

Tools and Utilities

 Upgrade Tools

 Upgrade Utilities

 Aclcomp

 Aclconv

 Convert

 Portuas

 Restenv

 Sfmconv

 Userconv


Aclcomp

Aclcomp is a Windows NT utility that reads the file ACLLISTdrive.DAT created when the LAN Manager acllist utility is run on an OS/2 volume, and verifies that files and directories have accurately transferred to NTFS.

Syntax

aclcomp [/dat:filename] [/a] [/newdrive:drive:] [/log:logfilename] [/s] [/q] [/codepage:codepagenumber] [/?]

Options

/dat:filename

Specifies the inventory filename, defaulting to ACLLIST.DAT in the current directory.

/a

Tells aclcomp to append the inventory information to an existing file.

/newdrive:drive

Tells aclcomp to check a drive other than the one specified by the ACLLISTdrive.DAT file.

/log: logfilename

Specifies the conversion report filename. If not specified, output defaults to ACLCOMP.LOG in the current directory.

/s

Sets silent mode. No status information is echoed to the screen during execution.

/q

Sets quiet mode. Minimal status information is echoed to the screen during execution.

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the server running LAN Manager for OS/2.

/?

Displays command usage.

Comments

Aclcomp checks for mismatches in the creation date and time, the last access date and time, the last write date and time, the data checksum, file size and file attributes, and permissions. Aclcomp (and acllist) do not report on settings associated with drives, named pipes, or print or communication queues.

ACLCOMP.LOG reports successful and unsuccessful transfers.

Examples

To use aclcomp to check information stored in ACLCOMP.DAT in the current directory and write it to ACLCOMP.LOG in the current directory, type:

aclcomp

To write ACLCOMP.LOG to another drive, type:

aclcomp /log:b:\aclcomp.log

To direct aclcomp to check a particular filename, type:

aclcomp /dat:acllistd.dat

To direct aclcomp to check a drive different from the one specified by ACLLISTdrive.DAT, such as the D drive, type:

aclcomp /dat:acllistc.dat /newdrive:d:

See Also

Verify Permissions


code page

Upgrade Manager supports upgrading from English to another language. Code pages determine the character correspondence tables used to set up specific language versions of software.

To detect a language change, Upgrade Manager compares OS/2 code page information with the OEM code page under Windows NT.  If code pages differ, Upgrade Manager modifies the express Upgrade Schedule so that the command lines of aclconv, aclcomp, portuas, restenv, sfmconv, and userconv include the /codepage switch, with the appropriate codepagenumber value.

A Custom Upgrade Schedule always includes a /codepage:### entry for those utilities. If you are performing a Custom upgrade (or running one of those utilities from the command line) and are also changing languages, first check the ADVISORY.TXT for OS/2 code page information, and then specify the appropriate codepagenumber value (replacing ###) for those utilities.


Aclconv

Aclconv is a Windows NT utility that reads the file and directory permissions stored in the file ACLBAKdrive.ACL created when the LAN Manager backacc utility runs on an OS/2 volume. Aclconv then applies equivalent permissions to the files and directories on that volume once it has been converted to NTFS.

Syntax

aclconv /data:datafile /log:logfile [/newdrive:n:] [/domain:domain] [/codepage:codepagenumber] [/?]

aclconv /log:logfile /list

Options

/data:datafile

Specifies the backup file produced by backacc (the default filename is ACLBAKdrive.ACL).

/log:logfile

Specifies a log file in which to write ACLs that aclconv could not restore.

/newdrive:n:

Is the drive to which permissions are to be restored. This parameter is only necessary if the files are stored on a different drive from that used on the source server. For example, if files are transferred from the E partition of the source OS/2 computer to the D partition of the destination Windows NT computer, n is D.

/domain:domain

Searches only the specified domain for account names.

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the server running LAN Manager for OS/2.

/list

Lists the contents of the specified log file.

/?

Lists the command usage.

Comments

Since only NTFS supports the security features of Windows NT, aclconv can only be run on volumes that have been converted to NTFS. Before you convert a volume to NTFS or run aclconv, you must first run the backacc utility on the LAN Manager volume you intend to convert to NTFS.

Aclconv supports moving files from drive C on the source LAN Manager volume to drive D on the destination Windows NT computer. It also allows you to merge files from two LAN Manager volumes into one Windows NT volume.

Access control lists (ACLs) that could not be restored by aclconv have to be restored manually.

Aclconv is often the most time-consuming portion of the upgrade; for large numbers of accounts, the process can take several hours.

Examples

To restore permissions for files transferred from the C drive on the LAN Manager server to the C drive on the destination server, where the log file name is ACLLOG, type:

aclconv /data:aclbakc.acl /log:acllog

To view the log file created by aclconv, type:

aclconv /list /log:acllog

To restore permissions for files transferred from the C drive on the source server to the D drive on the destination server, type:

aclconv /data:aclbakc.acl /log:logfile /newdrive:d:

To merge files from two LAN Manager volumes (C and D) into a single Windows NT volume (C), type:

aclconv /data:aclbakc.acl /log:acllog

and then type:

aclconv /data:aclbakd.acl /log:acllog /newdrive:c

See Also

Restore Permissions


Convert

The Windows NT convert utility converts FAT, HPFS, or HPFS386 volumes into NTFS volumes, without losing data.

Syntax

convert drive: /fs:targetfilesystem [/?]

Options

drive:

Is the path of the drive to convert.

targetfilesystem

Is the file system to convert to. The default is NTFS.

/?

Lists command usage.

Comments

Convert operates on any volume as long as it located on a local drive. This includes the system (boot) volume and any volume containing a paging file. Convert does not operate on the current drive.

Convert preserves all user file data and extended attributes (EAs) on a volume. It also preserves volume labels and serial numbers.

Convert requires a certain amount of memory and free space to run. The utility estimates the memory required before attempting a conversion in order to avoid running out of memory in the middle of the conversion process. (Note that if convert fails because of insufficient memory, it leaves the volume in a valid state.) Convert also estimates the minimum amount of free space required on a volume and only proceeds if adequate free space is available. If, during conversion, that estimate turns out to be insufficient, convert quits, leaving the volume in its original state. Free space should be equal to approximately 10% of occupied space on a drive.

The volume to be converted must be consistent (the LAN Manager utility chkdsk must not report errors). For drives that have open files, chkdsk is invoked automatically to fix errors before converting. If convert is unable to lock a drive for conversion, it offers to convert it the next time the computer starts.

Examples

To convert the C partition to NTFS, type:

convert c: /fs:NTFS

or:

convert c:

See Also

Convert Partition


Portuas

Portuas restores the user and group accounts of a LAN Manager server onto a Windows NT Server computer.

Syntax

portuas /f:filename [/u username] [/v] [log:filename] [/codepage:codepagenumber] [/?]

Options

/f:filename

Specifies the path and filename of the LAN Manager 2.x NETACC.BKP file, which contains user account information. NETACC.BKP is created by running the LAN Manager backacc utility.

/u username

Specifies a single user or group to restore. The default is for all accounts to be converted.

/v

Specifies verbose mode.

/log:filename

Creates a log file in the current directory.

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the LAN Manager for OS/2 server.

/?

Lists command usage.

Comments

The portuas utility merges a LAN Manager user accounts database, including remote access accounts, with an existing Windows NT Workstation or Server security database by reading information from the NETACC.BKP file (created by the backacc utility).

To use portuas, you must be a member of the Administrators group and the Server and Net Logon services must be running on the Windows NT computer.

If the file PORTUAS.LOG already exists, portuas will not run. Rename or delete the file.

When a user or a group name in a LAN Manager domain matches a group on the destination Windows NT Server computer or the domain name of the destination system, portuas prompts you to decide whether to change the conflicting name, leave it as is, or skip it entirely. After you decide, the merge continues with the remaining users or groups.

Note that when you use the /u option to add a single user, in addition to porting the specified user, portuas transfers all LAN Manager group names to Windows NT Server. For example, portuas /f netacc.bkp /u pamsw results in the following:

All groups listed in NETACC.BKP are added to the Windows NT security database.

The user pamsw is added with her group membership preserved.

If the groups or the user pamsw already exist, portuas overwrites previous information, which in the case of groups is a remark entry.

Examples

To merge a LAN Manager user account database into a Windows NT user account database, type:

portuas /f:a:\lanman\accounts\netacc.bkp /v

To add the user account JEFFH from a LAN Manager user account database to a Windows NT computer, type:

portuas /f:a:\netacc.bkp /u jeffh

See Also

Restore User Accounts


Restenv

The restenv utility uses the file created by the backenv utility to restore configuration information into the Windows NT Server Registry.

Syntax

restenv source file [/noalerter] [/nocountry] [/nonetlogon] [/nonetworks] [/noprotocol] [/noras] [/noreplicator] [/noshare] [/nouses] [/noworkstation] [/noserver] [/nosnmp] [/noups] [/test] [/noverbose] [/codepage:codepagenumber] [/?]

Options

source file

Is the name of the file created by backenv. If not specified, restenv attempts to read LMBAKENV.DAT in the current directory.

/noalerter

Does not restore Alert service settings.

/nocountry

Does not restore country code setting.

/nonetlogon

Does not restore Netlogon service parameters.

/nonetworks

Does not restore network parameters.

/noprotocol

Does not restore protocol settings.

/noras

Does not restore Remote Access Service parameters.

/noreplicator

Does not restore Replicator service parameters.

/noshare

Does not restore sharenames.

/nouses

Does not restore network connections.

/noworkstation

Does not restore Workstation service parameters.

/noserver

Does not restore Server service parameters.

/nosnmp

Does not restore SNMP service parameters.

/noups

Does not restore UPS service parameters.

/test

Runs diagnostics only; does not change system settings.

/noverbose

Does not echo complete information to the screen.

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the server running LAN Manager for OS/2.

/?

Lists command usage.

Comments

Restenv uses the file created by backenv (LMBAKENV.DAT) to restore whatever parameters were not set during Windows NT Setup.

Example

To restore LMBAKENV.DAT parameters from a floppy disk in your B drive, type:

restenv b:\lmbakenv.dat

See Also

Restore Environment


Sfmconv

Sfmconv is a Windows NT utility that restores functionality for Services for Macintosh on a Windows NT Server computer.

Syntax

sfmconv [ntfs drive:] [/script:filename] [/v] [/log:logfile] [lanroot] [/codepage:codepagenumber] [/?]

Options

ntfs drive:

Causes only Services for Macintosh volumes located on that drive to be converted. If this option is not specified, all Macintosh volumes on all drives are converted.

/script:filename

Specifies the location of a file that contains the LAN Manager root directory. If not specified, the default filename is SFMCONV.RUN. This file is created by the backenv utility if Services for Macintosh is present on a LAN Manager volume.

/v

Gives verbose output. Messages are displayed for all file and directory conversions. If /v is not specified, only a summary of the total number of files and directories is printed.

/log:logfile

Specifies a log file for status and error messages and warnings.

lanroot

Specifies location of LAN Manager root directory (C:\LANMAN by default).

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the LAN Manager for OS/2 server.

/?

Lists command usage.

Comments

To convert Services for Macintosh, you must preserve Macintosh volume structure exactly as it is under LAN Manager. The volume to be converted must have the same structure as the source LAN Manager for Macintosh volume. All partitions must be NTFS and Services for Macintosh must be installed. Sfmconv operates only on NTFS volumes.

Example

To convert only volumes C and D to Windows NT Services for Macintosh, where LAN Manager files are located in the C:\LANMAN directory, type:

sfmconv c

and then:

sfmconv d

See Also

Convert Macintosh Volumes


Userconv

The userconv command starts the User Conversion utility (USERCONV.EXE), which displays the User Conversion dialog box.

Syntax

userconv [/codepage:codepagenumber]

Options

/codepage:codepagenumber

Specifies the code page to be used by the upgrade utility.  Required when changing languages as part of the upgrade.  The codepagenumber is a 3-digit decimal number indicating the code page that was used by the server running LAN Manager for OS/2.

Comments

You can run User Conversion on its own, or from within Windows NT Server Upgrade Manager.  In Upgrade Manager, User Conversion corresponds to the Map To Trusted Domain Accounts tool.

User Conversion offers its own online Help.

Userconv allows you to implement a trusted domain model.  The User Conversion maps LAN Manager user accounts and groups into Windows NT Server domains. User Conversion provides:

Automatic mapping between LAN Manager and Windows NT Server user accounts (and groups) that have identical names.

This allows User Conversion to automatically identify and merge user accounts and groups when the old LAN Manager name is identical to the new Windows NT Server name.

Manual mapping between LAN Manager and Windows NT user accounts (and groups) that do not have identical names.

This allows you to select and merge user accounts and groups that are not identically named.  This is particularly useful when a user has several LAN Manager user accounts, under various user names, which should be combined into a new, single user account on the Windows NT Server computer.

Manual mapping of LAN Manager groups to new Windows NT Server local groups.

Each new local group will consist of the same users that were in the old LAN Manager group, except that the member user accounts will have been mapped to a Windows NT Server domain.

See Also

Map to Trusted Domain Accounts