Azure AD

[rorymcinerney]

Hi,

Tool is great thanks!

Feature suggestion, when moving from a local profile to azure AD linked accounts, the tool picks up the new domain as just DOMAIN which causes the following error when importing the profile;

Windows error 1332 description: No mapping between account names and security IDs was done.

However if you take the scanstate.exe command displayed in the right pane of the window and amend the command from DOMAIN\user to AZUREAD\user, the command then maps the accounts and imports the profile correctly.

Adding an option to take account of this behaviour may be useful for the future.

In any case, thanks again, saved me loads of work.

[rkopoku]

I second this. It would be a great feature to add!

[nickrod518]

Does the domain need to be overridden during both the scanstate and loadstate executions? Please try updating line 846 from:

$UsersToInclude += $Script:SelectedProfile | ForEach-Object { "`"/ui:$($_.Domain)\$($_.UserName)`"" }

To:

$UsersToInclude += $Script:SelectedProfile | ForEach-Object {
    if ($_.Domain -eq "DOMAIN") {
        Update-Log "$($_.UserName) appears to be an Azure AD user and will be saved as such."
        "`"/ui:AZUREAD\$($_.UserName)`""
    } else {
        "`"/ui:$($_.Domain)\$($_.UserName)`""
    }
}

and let me know if that works for you. If it works, I'll update the script.