Video Screencast Help

Moving DLO Media Server to new domain

Created: 25 Jun 2013 | 1 comment

Hello,

We have a DLO (2010 R2) installation with 300 users.

Network Share is located on the DLO server itself.

We are in process of merging our regional domains into a single root domain worldwide.

Hence the server on which DLO installed is going to join the root domain as well. (Example: 'old.test.com' to 'test.com')

We have moved the user workstations to the root domain already and the backups in existing DLO instance appears to be running fine. (Though there are new folders created in network share with new domain name).

What steps or precautions do we need to take before moving the 'DLO Media Server' into new domain?

Also are there any post movement steps required as well? .

One thing to add is when I checked on few of the clients, found the 'DefaultMediaServerName' is the FQDN of DLO server.

Any help is appreciated since I am kind of playing a blind game otherwise.

Operating Systems:

Comments 1 CommentJump to latest comment

tech_user's picture
Taken From DLO 7.5 Admin Guide
 
 
Prerequisites for Migrating Users across Administration Servers
 
The following prerequisites must be met before you can migrate users across
Administration Servers:
Domain The source and the destination administration servers must be on
the same domain or on trusted domains.
Administrative
Rights
The Administrator of the source Administration server must have
administrative rights on the destination Administration server.
DLO Versions The source and the destination administration servers must have
the same DLO versions and same patch levels.
Shared Clients The user that is migrated must not share the client computer
with any other user.
Storage Locations On the destination administration server, configure the same
storage location that is present on the source administration
server.
The name of the storage location on the destination
administration server must be exactly the same as the storage
location on the source administration server.
Profile On the destination Administration server, create the same profile
that is present on the source Administration server. This profile is
used by the user that is to be migrated. The profiles can be
migrated to the destination Administration server by using the
-IOProfile command. For more information, see “-IOProfile
command” on page 225.
Dedupe Server The source and destination Dedupe Servers must be on the same
domain or on a trusted domain.
Dedupe Storage Pools On the destination administration server, configure the same
Dedupe Storage Pool that is present on the source administration
server.
The name of the Dedupe Storage Pools on the destination
administration server must be exactly the same as the Dedupe
Storage Pools on the source administration server.
Dedupe Storage
Locations
On the destination administration server, configure the same
Dedupe Storage Location that is present on the source
administration server.
The name of the Dedupe Storage Location on the destination
administration server must be exactly the same as the Dedupe
Storage Location on the source administration server.
 
Migrating Users across Administration Servers
Before you start the migration process, review the section “Prerequisites for
Migrating Users across Administration Servers” on page 232.
To migrate users across Administration Servers
1 On the destination administration server, configure the same storage location
that is present on the source administration server. The name of this storage
location must be exactly the same as the storage location on source
administration servers. For example, the storage location name on the source
administration server is storage1. The destination server must also contain a
storage location with the name storage1.
2 On the destination administration server, create the same profile for the user.
The profile can be migrated to the destination server with the -IOProfile
command. The profile name must be exactly the same on both the source and the
destination servers. For more information, see “-IOProfile command” on
page 225.
3 On the source administration server, enter the following command:
DLOCommandu -MigrateUser -M <media server>[-A|-F <file
server>|-P <profile name>|-PI <profile id>|-S <SL name>|-SI
<SL id>|-U <user>|-UF <text file path>]
Note: Wildcard '*' match is permitted in profile, Storage Location, and user
names.
Quotations around name are required if name contains a space or colon.
To get a list of all storage locations, use the -ListSL command.
 
dlo_migrat_options.JPG
 
 
Note: For the -DBInstance option, specify “” in case of a blank instance.
The following are examples of using this command:
DLOCommandu -MigrateUser -M MARY.CAF.dlo.com -P Profile1
DLOCommandu -MigrateUser -M MARY.CAF.dlo.com -U CAF\ummouse
On the source administration server, the user’s status changes to User Migrated once
the migration is successful. Delete this user from the Administration Console
 
-MigrateDomain command
This command is used to migrate a user from an old domain to a new domain in
trust.
Syntax:
DLOCommandu -MigrateDomain -OD <OldDomainName> -ND <NewDomainName> -U
<UserName>
 
 
more details on page no 224and on wards  of DLO 7.5 Admin Guide