Agents and Migration Jobs Accessible To All Domain Admins (Limited Availability)

Agents and migration jobs created by admins and power users are accessible to all the other admins in the same domain. Shared agents refer to the migration agents which can be used by other users in the domain to create migration jobs. The Agent Creator (the one who installed the agent) can create migration jobs on their agents and take other actions, such as delete agent, deactivate agent, speed test, and scan source. Non-agent creators, on the other hand, can only create new migration jobs using the shared agents. 

This feature is useful for scenarios wherein a job created by a user needs to be monitored or managed by other users. For instance, an Admin in an organization can create a migration job and another admin can then either monitor, true-up or perform other actions on the migration job. 

Admins can easily filter the jobs to view the jobs created by themselves or by the other admins. 

1. Navigate to the Migration Dashboard and view the migration jobs listed. 
2. Click on the Created By filter which has two choices as Anyone (default) and Me. 
3. Select the desired filter to view the self-created migration jobs or the ones created by anyone.  

Non-agent creators can only create new migration jobs using the shared agents. All other actions are disabled for users who are not agent creators.

Considerations and Limitations

• The agent owner can delete any completed job associated with their agent, regardless of who created the job. Likewise, the agent owner can download the migration report for any job run using their agent, even if the job was created by another user.

• If a job was created by an admin using a power user’s agent, the migration report might be lost forever if the power user deletes their folders, or leaves the organization.

• Users cannot create a Migration Project using a shared agent. However, users can assign jobs in a project to a shared agent.
• If a migration job is created by User A and is being monitored, managed, or updated by User B, the File Audit Report in the WebUI will have the logs in the name of User A. 
  • To view the activities performed by other users (User B), refer to the Migration Job report for the details. 
• In the filter section of migration jobs, only those users will be displayed in auto-suggestion who have access to the Migration App.
• If a user who has created the migration leaves the organisation then the Admin will not be able to run any command on that user's migration, assuming that the agent created with the previous admin’s credentials has been deactivated.
  • The workaround for this limitation is to re-register the CMM agent with new admin user credentials.