Show orphan account profiles

Do you want users to be able to select orphan account profiles to be migrated?

If true, all user profiles are included in the list of users able to be migrated, even if the user account is not resolved.

1 = True

0 = False

Defaults to True

None.

Orphan account profile handling

How should unresolved account profiles be processed during a migration?

Determines how CA DMM processes account profiles for which the user cannot be verified on the network.

1 = Temporarily unavailable

0 = Assume deleted

Defaults to Assume deleted (0)

None.

Use Microsoft profile naming conventions

Do you want to name the profiles according to Microsoft profile naming conventions for each platform?

When migrating user profiles, the ability to rename the user profile using Microsoft naming conventions or to use a consistent naming convention across operating systems is supported. If you do not use Microsoft naming conventions, the migrated profiles is named %username%.%domain%

1 = True

0 = False

Defaults to True

None.

Create roaming user profiles

Do you want to create user profiles as roaming user profiles when migrating to Active Directory?

If true, user profiles are created as roaming user profiles.

1 = True

0 = False

Defaults to false

None.

Roaming profile path

Do you want to identify a path to store roaming user profiles?

Defines the base folder path that is used to set the Profile Path user property when creating a roaming user profile in Active Directory. The actual roaming profile path depends on the user name.

Defaults to existing shared paths.

An empty path specifies that any create profiles will not set the Profile Path user property.

Must set Create roaming user on.

Use existing profiles to resolve user destinations

Do you want to use the account profile information present on disk to resolve user tree destination paths?

Determines whether user destination will use network information and attempt to create missing accounts or restrict itself to using existing profile information only. Redirecting accounts to existing profiles can be used during crossover cable migrations or whenever network resolution is impossible. Destination paths will match against all available existing profiles and will match the first profile with the same user path. Allows for wildcard matching of domain or user name, but not Active Directory organizational units unless the network is accessible. Domain name is not normally resolvable for account profiles without network access, so a wildcard domain match may be required. If only a user name is provided, then only local user account profiles will be used to resolve the destination path.

True or False.

Defaults to False

None.