After you have modeled your consolidation in the Project Window, you should verify that the proposed locations for these new objects do not conflict with existing names, rights, name spaces, etc., in the eDirectory tree.
Remember, you have simply created a model of how you want to copy the Windows data to the destination servers and volumes; no data has yet been migrated. Dragged-and-dropped items appearing in the eDirectory tree are merely assigned to be copied to that area in the eDirectory tree. Objects are not actually copied until you begin the consolidation process. When migrated, Windows User objects are converted to eDirectory objects and placed in the destination eDirectory tree.
Because a similar verification process is run when you begin the actual consolidation, running the precopy verification process prior to consolidation is not mandatory. However, catching any critical errors or warnings now will speed up the verification process during the consolidation.
From the Server Consolidation Utility menu, select> V or click the button on the toolbar, then click .
Read the Welcome page, then click.
If you want to apply a Template object to newly created eDirectory users, browse the tree, select the Template object from the tree view, and then click.
If you do not want to use a Template object, uncheck the box, then click.
To migrate home directories, you must use a Template object when migrating your Windows users to the destination eDirectory tree. Make sure a Home Directory property is defined for the Template object you are using.
HINT:If you have not created a Template object but you want to use one now, save the project, go to ConsoleOne, and create the Template object. Next, launch the Server Consolidation Utility again and click Open Last Project. Then restart this migration procedure again starting with Step 1.
Decide how you want to handle any duplicate filenames between the Windows domain and the destination eDirectory tree, select one of the following, then click:
Don’t Copy Over Existing Files: The file on the source server is not copied and the file on the destination server is not replaced.
Copy the Source File If It Is Newer: If the file on the source server is newer than the one on the destination server, the file on the destination server is replaced.
Always Copy the Source File: The file on the source server always replaces the file with the same name on the destination server.
Decide how you want to handle passwords for your Windows users, select one of the following, then click:
Assign the Same Password to All Users: The utility will assign the same password to all migrated users.
Assign a Randomly Generated Password to All Users: The utility will randomly generate passwords, assign them, and then store the passwords it assigns in a file that it creates, named project_name_out.txt. This file is saved in the same directory where your consolidation project is located.
Read Passwords from a File: The utility will migrate the current Windows passwords to the destination eDirectory tree by reading them from a text file. You must create the text file containing the Windows passwords before you begin the migration.
For more information on how to create this file, click thebutton.
Set Windows consolidation options by checking or unchecking the check boxes next to the following options and then click:
Copy File Permissions: Normally, the utility migrates file and directory permissions. If, for some reason, you want to reassign file and directory permissions, you can choose to not copy the file and directory permissions here and then assign them later with ConsoleOne.
Copy Everyone Permissions: The eDirectory container that you drop the Windows Domain Info object into will be assigned the permissions that were associated with group Everyone. If you are migrating the Everyone permissions, be sure to drop the Domain Info object high enough in the eDirectory tree so that all Windows users will inherit those permissions.
HINT:Every new folder that is created in the Windows domain automatically receives the Everyone permissions by default.
Restart Option: Normally, this information is not erased; however, if you have previously run a consolidation program and deleted the eDirectory objects from the destination tree, and you are planning to start over and migrate the same domain again, check this check box.
When you migrate users and groups from Windows, the Server Consolidation Utility stores a table of Windows names and associated eDirectory usernames in the registry of the Primary Domain Controller (PDC). The utility then uses this information when migrating the file system so that it can remember where each user and group has been migrated to in the destination eDirectory tree. By storing this information, the utility can assign the correct file permissions to the appropriate users.
To begin the verification, clickin the Verify NT to NetWare Project window.
(Conditional) If prompted, resolve any naming conflicts between different-type objects, then click.
You can choose to merge different-type objects or to keep them as they are.
(Conditional) If prompted, resolve any naming conflicts between same-type objects, then click.
You can choose to merge same-type objects or to keep them as they are.
(Conditional) If prompted, verify that you do not want to migrate the listed Windows users and groups, then click.
If you migrated all of your users and groups, you will not see this dialog box.
Otherwise, this step must be done three times—once each for your Windows local groups, global groups, and users that were not dragged and dropped into the destination eDirectory tree.
If you have made a mistake, click Cancel to return to the Project Window. Then drag-and-drop the objects, go to the toolbar, click Step 1.> , then restart this procedure with
Resolve any critical errors.
Warnings or noncritical errors can be resolved after the consolidation. To resolve a critical error or warning, read the description in the text field located beneath it. This description should give you a good idea of what could be the possible cause and a suggestion for fixing it.
If you are copying data from a Windows 2000/2003 server, you might see several “Group membership from another domain” errors stating that a particular group or user will not be migrated. These errors are informational; the specified group or user accounts have no purpose or function in Netware.