• State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 19 subscribers
  • Views 3468 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

Service Attributes question

tienlamnguyen
over 6 years ago

Hi I need to understand Matching Service Attributes.

According to the user guide. it is statedas follows:  Matching—When two objects are matched, the Global Unique Identifier (GUID) of the corresponding object is written to the service attribute selected to store information about matching

I migrated 2000 users recently and if I retrieved the GUID of the source domain and the Extenstion Attribute 15 of the same migrated user, I see that they are not identical:

GUID of source domain (domain A) of user X: 7a79022c-9e79-4e92-8ffb-bef0debcdeb3

ExtenstionAttribute15 of user X on target domain (Domain B): 2C02797A799E924E8FFBBEF0DEBCDEB3

 

I can see that part of the GUID  from User X gets written to attibute15 on the target but it is not identical. I this normal ? How can I be certain that this user is the same one when I start a new migration project? (ex: Domain C -> Domain B) ?

I do not want to merge a wrong user account.

  • 0 over 6 years ago

    QMM uses the octet string format.

    There's a handy Powershell function out on the web Convert-GuidToOctetString that you can Google for that will take the GUID from your initial format to that used by QMM.

    Alternatively, if you use the Quest PoSh cmdlets to enumerate your objects, if you select the ObjectGUID attribute it will return the GUID in the QMM format.

  • 0 over 6 years ago in reply to JohnnyQuest

    Thanks @JonnyQuest with Quest powershell command I get the value in Octet