This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
I have performed a swing migration of our old Azure AD Connect v1 to a new Azure AD Connect v2
I have imported the .json file from our V1 to the new server and enabled the stagging mode on the new server.
Regarding this upgrade I have 2 concerns, after a comparison of the Exported json and the new applied json, I discovered some changes in the immutableTag of 4 Items and additional item at the end of the V2 json file.
I just wanna know if I need to worry about or it's because we upgrade from 1.6.16.0 to 2.2.1.0 ?
thanks :-)
on json file of V1
"Name": "Out to AAD - User Join",
"uniqueIdentifier": "c9dd1b2d-cd34-44ef-8adc-4090dc514839",
"immutableTag": "Microsoft.OuttoAADUserJoin.007",
"precedence": 140
on json file of V2
"Name": "Out to AAD - User Join",
"uniqueIdentifier": "c9dd1b2d-cd34-44ef-8adc-4090dc514839",
"immutableTag": "Microsoft.OuttoAADUserJoin.013",
"precedence": 140
and the last concern it's about additional option in the V2 json
},
{
"Name": "In from AD - Device Common",
"uniqueIdentifier": "09113be1-4cc3-4755-b955-f6c0bfb113ab",
"immutableTag": "Microsoft.InfromADDeviceCommon.002",
"precedence": 207
},
{
"Name": "Out to AD - User NGCKey",
"uniqueIdentifier": "d55578a4-c7ec-4ad7-9e1a-e540cb6e5b07",
"immutableTag": "Microsoft.OuttoADUserNGCKey.001",
"precedence": 208
},
{
"Name": "Out to AD - Device STKKey",
"uniqueIdentifier": "f991ab2e-feee-4b60-9a69-74553cd21b92",
"immutableTag": "Microsoft.OuttoADDeviceSTKKey.001",
"precedence": 209
}
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 81%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
I'm looking into this but wanted to check - is it possible that your config may have changed from using objectGuid as sourceAnchor to using mS-DS-ConsistencyGuid as the sourceAnchor?
@Marilee Turscak-MSFT thanks for you answer and good point but I checked and the source Anchor has not changed.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 74%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
I did the similar swing migration, currently running AD connect v.1.6.16 and new server installed v2.2.1.0
the new applied configuration has the following changes and added 1 new setting:
"immutableTag": "Microsoft.OuttoAADUserJoin.007", => "immutableTag": "Microsoft.OuttoAADUserJoin.013",
"immutableTag": "Microsoft.OuttoAADGroupWriteupMemberLimit.002", => "immutableTag": "Microsoft.OuttoAADGroupWriteupMemberLimit.003",
"immutableTag": "Microsoft.InfromADUserJoin.005", => "immutableTag": "Microsoft.InfromADUserJoin.006",
"immutableTag": "Microsoft.InfromADUserCommon.009", => "immutableTag": "Microsoft.InfromADUserCommon.010",
"Name": "In from AD - Device Common",
"uniqueIdentifier": "502c4ced-739b-413f-9af9-c86b7600647a",
"immutableTag": "Microsoft.InfromADDeviceCommon.002",
"precedence": 164
Not sure if this is concrete, but I found this thread and one user said the different values don't matter because of the different Databases and to rely on metaverse search to confirm if everything is ready to switch:
"immutableTag": "Microsoft.OuttoAADUserJoin.013" "immutableTag": "Microsoft.OuttoAADUserJoin.007",
As you have a new version, existing rules in the database are different. This number is not important.
Now, to know if you can switch, you should use the "Metaverse search" for each kind of objects:
<Screenshot>
The number of person, group, devices should be nearly identical on the 2 servers, the old and the new.
An update that can help someone.
We put the new server in production and the old one in stagging mode without any issue.
ImmutableTag have no impact on the migration of the ADConnect.
I'm agree Katflp with the different database.
thanks