The server on which the Engine in Active Directory is installed must have the Client for OES installed while the migration is being performed. After the migration is complete, the client can be removed. Additionally, the Engine can delegate migration operations to Agents for improved migration performance. If Agents are deployed as a part of a Storage Manager installation, these Agents are individually used for migration if the Client for OES is installed on them. In order for an Agent to participate in a migration, the server that has the Agent installed must also have the Client for OES installed. This determination is made automatically within Storage Manager as a part of Agent/Engine communications and no additional configuration is required in order to use this feature.
The Client for OES installed on the Engine in Active Directory should be properly configured to use SLP (Service Location Protocol) for the eDirectory tree source of a data migration. For information on SLP configuration, see “Setting Client Properties” in the Novell Client 2 SP3 for Windows Administration Guide.
Before you proceed with an eDirectory to Active Directory Cross-Empire Data Migration, perform the following tasks:
Log in with Administrative access to the Domain.
Install the Storage Manager Engine on the target Windows server.
See Installing the Engine
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
Install the Client for OES with the NMAS installation default option on the Engine server.
The Client for OES can be removed after you have completed your migrations.
Extend the Active Directory schema.
This is required only if you are migrating to a target share managed by a collaborative storage policy.
See Active Directory Schema
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
Install SMAdmin.
See Installing SMAdmin
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
(Optional) Install and authorize the Event Monitor.
The Event Monitor is not needed for a Cross-Empire Data Migration, but is needed for managing storage once your data has been migrated to the Microsoft network.
See Installing and Configuring the Event Monitor
and Authorizing the Event Monitor
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
Assign SMProxyRights group Full Control permission to the shares to which you will be migrating data.
See Setting Rights and Privileges on Managed Storage
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
Install and authorize Agents and configure Proxy Agents for all servers that will be target servers for Cross-Empire Data Migrations.
See Installing and Configuring the Agents
and Authorizing the Agents
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
(Conditional) If you plan to migrate data to a NAS device, make the SMProxyRights group a member of the Local Administrators group on each NAS device.
See Setting Rights and Privileges on Managed Storage
in the Micro Focus Storage Manager 5.2 for Active Directory Installation Guide.
Install the Client for OES and configure SLP on any Agent servers that will be involved in a Cross-Empire Data Migration.
The Client for OES can be removed after you have completed your migrations.
Create Storage Manager policies for the migration of storage.
These policies are needed if the Cross-Empire Data Migrations will be driven by Storage Manager policies, which we recommend for migrating user data.
For all objects in eDirectory that have rights assigned to the file system, create matching objects in Active Directory.
To migrate rights assigned to containers, you must create an equivalent Group object in Active Directory for each container object in eDirectory,.