• State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 20 subscribers
  • Views 4471 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Quest Migration Manager processing did not change servieaccount

tienlamnguyen
over 5 years ago

Hello,

I migrated a server and after the end of the processing activity , i did not get any error. The Lof files says that services account have no errors.

But, When I log in to the server, I see that it did not change to the target domain.

I am at a loss as how to investigate this. If someone can direct where to look, It is appreciated

Parents
  • 0 over 5 years ago

    Check the contents of the VMOVER.INI file on the server (it's in the agent's folder).  Verify that there is an entry for the account in question there.  If there isn't then there's your answer - there's no mapping for the agent to refer to.

  • 0 over 5 years ago in reply to JohnnyQuest

    Hello 

    I finally found the .ini file and between the header [] I do not see my sevice account source and target object mapping

    How can I investigate this error ?

  • 0 over 5 years ago in reply to tienlamnguyen

    The way I check for account mappings is to locate the migration session that I believe processed the object and initiate an "Undo" - but only to the point where it lists the objects in the session.  There you will see whether or not there is an entry for the account you are looking for.

  • 0 over 5 years ago in reply to JohnnyQuest

    I was unable to retrace the directory Migration Session as it was deleted by the previous DMM administrator.

    But I was able to retrieve the matching pair ExtensionAttributes. From the ExtensionAttributes I was able to valide the souce and target GUID

    Both GUID are the same. Why can QMM is unable to do the mapping ?

  • 0 over 5 years ago in reply to tienlamnguyen

    The quickest solution at this point would be to do a migration session for that one account to try and force the re-creation of the mapping.  Then create a resource processing job for your server and check if the account shows up in the VMOVER.INI this time.

  • 0 over 5 years ago in reply to JohnnyQuest

    Hello

    How can I do this ? Delete the extensionAttributes with powershell commands on the target domain and redo the mapping ?

  • +1 over 5 years ago in reply to JohnnyQuest

    Hello,

    So I deleted the extensionAttributes on target domain, recreated the migration session. Once this is complted, RUN was able to process the service account.

    I believe that RUM needs to have the migration session available in order to do the mapping. If you deleted the migration session, the mapping is btoken

    I Wonder if I migrrated a user a seconf time, Will I loose a licence ?

Reply
  • +1 over 5 years ago in reply to JohnnyQuest

    Hello,

    So I deleted the extensionAttributes on target domain, recreated the migration session. Once this is complted, RUN was able to process the service account.

    I believe that RUM needs to have the migration session available in order to do the mapping. If you deleted the migration session, the mapping is btoken

    I Wonder if I migrrated a user a seconf time, Will I loose a licence ?

Children
No Data