@@ -1939,146 +1954,217 @@ The lab campaign
Configuration: unknown setting X |
typing mistake or setting of another version |
compare with chapter 6 |
+ |
Batch <id> not found under ... |
the batch folder is not in Storage.BackupFolder |
copy the whole Batch-... / Finalize-... folder there, or give the path of the JSON file |
+ |
The Convert batch used by this Recover is not in ... |
cloud phase of a Recover without the original Convert batch |
copy the Batch-<convert id> folder too |
+ |
Batch ... is a Convert batch: the cloud phase of a Recover needs the batch printed by its AD phase |
wrong ID |
use the ID printed by Recover -Phase AD |
+ |
EntraConnect.Sync = $true but the ADSync module is not on this server |
AD part not on the Entra Connect server |
set EntraConnect.Server, or run on the Entra Connect server, or Sync = $false |
+ |
Entra Connect sync will not be possible: this account has no right on X ... |
the check made before the first AD write was refused: the account cannot open a remote session on X, or cannot use ADSync there |
give the account Remote Management Users (or Administrators) and ADSyncOperators on X, or set EntraConnect.Sync = $false and synchronise by hand. Nothing was changed |
+ |
Entra Connect sync will not be possible: X does not answer to PowerShell remoting |
wrong name in EntraConnect.Server, WinRM (TCP 5985) closed, firewall |
fix the name or the access (Test-WSMan X shows the network part only). Nothing was changed |
+ |
-AD is changed and verified. The Entra Connect sync could not start: ... (Pending, exit code 2) |
-the check passed, then the cycle failed (right removed, server down, timeout) |
+AD is changed and verified. The Entra Connect sync did not run: ... (Pending, exit code 2) |
+the check passed, then the cycle failed (right removed, server down, timeout, scheduler suspended); the Next steps give the first line of the message, the full technical message is in the log. For a suspended scheduler: run Set-ADSyncScheduler -SchedulerSuspended $false on the Entra Connect server, then the delta sync |
+ |
+ |
+
+
+The RSAT ActiveDirectory module is not installed on this server: ... |
+the AD part was started on a server without the RSAT feature Active Directory module |
+install the RSAT feature, or run the AD part on a server that has it |
do not convert again: run a delta sync on the Entra Connect server, then carry the package (or -Phase Cloud -Batch <id>) as the Next steps say |
<account> is already converted by batch <id> (it is a remote mailbox now) |
a Convert was started again for an object that the batch <id> already converted |
-nothing is converted. To finish that batch (sync + package) run the command in the message: -Action Convert -Phase AD -Mode Apply -Batch <id> |
+nothing is converted. To finish that batch (sync + package) run the command given in the Next steps: -Action Convert -Phase AD -Mode Apply -Batch <id> |
+ |
This batch has no AD proof (State file) ... cannot be finished from here |
-Phase AD -Batch on a batch whose AD changes were not verified |
use the cloud phase only for a batch with a proof; otherwise run a Preview of a new Convert |
+ |
An Exchange Online session already exists in this console |
the console was used for EXO before |
open a new PowerShell 7 window |
+ |
Microsoft Graph: found Microsoft.Graph.Authentication 2.40.0; Microsoft.Graph.Users 2.35.1. The tool needs both in one same version 2.41.1 or later |
the Graph modules installed are too old, or not in one same version (two versions of Graph in one session fail with Assembly with same name is already loaded) |
-run the command of the message: Install-Module Microsoft.Graph.Authentication,Microsoft.Graph.Users -MinimumVersion 2.41.1 -Scope AllUsers. Nothing was changed. The tool imports both modules in that same version. The same text is on the Microsoft.Graph light of the Setup page |
+run the commands of the message, one per module and both for the same version (Install-Module Microsoft.Graph.Authentication -MinimumVersion 2.41.1 -Scope CurrentUser, then Install-Module Microsoft.Graph.Users -MinimumVersion 2.41.1 -Scope CurrentUser; -Scope AllUsers needs a window opened as administrator). Install-Module refuses -MinimumVersion with several names. Nothing was changed. The tool imports both modules in that same version. The same text is on the Microsoft.Graph light of the Setup page |
+ |
ExchangeOnlineManagement: found 3.9.0; the tool needs 3.10.1 or later |
the module is too old |
-Install-Module ExchangeOnlineManagement -MinimumVersion 3.10.1 -Scope AllUsers. Nothing was changed |
+Install-Module ExchangeOnlineManagement -MinimumVersion 3.10.1 -Scope CurrentUser (-Scope AllUsers in a window opened as administrator). Nothing was changed |
+ |
Microsoft Graph 2.40.0 is already loaded in this PowerShell session |
an older Graph was loaded earlier in this window |
close the window, start the tool in a new PowerShell 7 window |
+ |
Nothing was changed in AD. This account cannot write to <DC>: run the tool on that domain controller, or with an account that has the rights |
the domain controller refused the first write (for instance the account is SYSTEM of another server and DomainController names a remote domain controller) |
-run the tool on that domain controller, or with an account that has the rights (chapter 4). The backup folder written before the refusal holds NOT-APPLIED.txt: it is not a batch to continue or to roll back, and is kept as a record |
+run the tool on that domain controller, or with an account that has the rights (chapter 4). The Next steps give the command to run there: the Preview first (with the batch ID, and without the configuration path of this server: the other server has its own), then the same command with -Mode Apply. The backup folder written before the refusal holds NOT-APPLIED.txt: it is not a batch to continue or to roll back, and is kept as a record |
+ |
Configuration: Scope.Mode = OU requires Scope.SearchBase: no OU is set |
a conversion (not a Check, not a cloud phase) without any source of mailboxes |
-fill Scope.SearchBase (or GroupDN, CsvPath) in the configuration file, or give -Identity, -CsvPath or -SearchBase, or set Scope.Mode = Auto. Nothing was changed |
+fill Scope.SearchBase (or GroupDN, CsvPath) in the configuration file, or give -Identity, -CsvPath, -SearchBase or -Group, or set Scope.Mode = Auto. Nothing was changed |
+ |
Next steps of a Preview started with a package (-Batch <package.zip>) |
the Preview extracts nothing into the backup folder |
the commands name the package itself (-Batch '<package.zip>'): run the same command with -Mode Apply |
+ |
-Action is missing: nothing was done |
the command has no -Action |
always give -Action Convert, Recover, Finalize or Check (the tool no longer waits for an answer at a prompt) |
+ |
-Microsoft Graph cannot load in this console (assembly conflict ...) |
-Exchange Online was used earlier in the same window (for example Recover, then Check): its assemblies stay loaded and Microsoft Graph cannot load next to them |
-open a new PowerShell 7 window for each run that needs Microsoft Graph (Check, Convert of users) |
+Microsoft Graph could not load an assembly in this console |
+a module of this window already loaded an assembly that Microsoft Graph needs in another version |
+open a new PowerShell 7 window |
+ |
+
+
+Transfer package: the .sha256 file next to the package is missing. Copy <name>.zip.sha256 from the Outbox folder of the AD server ... |
+only the .zip was copied |
+copy <name>.zip.sha256 from the Backups\Outbox folder of the server that wrote the package, into the same folder as the .zip, then run again |
+ |
+
+
+The Apply would be refused as things stand. First ... (Next step of a Preview) |
+the Preview already knows that the Apply will stop (the account has no right on the Entra Connect server, or the cloud modules are missing) |
+do what the line says, then run the Apply proposed after it |
+ |
+
+
+<account>: not in the expected state: no mailbox in Exchange Online yet ... (Check) |
+the object is still an on-premises mailbox, or the sync has not run: a Check only reads |
+run the Convert, or the sync, then Check again. Check finished: N object(s) not in the expected state. Nothing was changed. ends the run (the result card says Check finished - N object(s) not in the expected state); the technical states are in the log |
+ |
+
+
+<account>: Microsoft 365 did not answer (network): <host>. Run again. |
+Microsoft Graph or Exchange Online did not answer from this machine (network, proxy, firewall, a moment of unavailability). The technical text of the error is in the log only. A run error is counted as an error (1 error(s)), never as not as expected, which is only for objects that were read and compared |
+nothing was changed by a Preview or a Check: run it again (the Next steps give the command). After an Apply of a cloud phase (-Phase Cloud), run the same command again: what is done is kept and checked again. After an Apply of phase Both, the AD part is already made and verified and the same command would be refused: go on with -Phase Cloud -Mode Apply -Batch <id> (the Next steps give the command, for a Recover too) |
+ |
+
+
+The domain controller <DC> does not answer from this machine (Active Directory Web Services, TCP 9389): ... |
+the domain controller cannot be reached from this machine (a Check given an account name needs to read AD) |
+run the tool on a machine that reaches the domain controller, or give the UPN of the mailbox as -Identity (no AD read is needed). The raw error text is in the log. Nothing was changed |
+ |
+
+
+N object(s) are not yet in the expected state in Exchange Online. If the Entra Connect sync has not run ... (Next step of a cloud Preview) |
+the Preview looked once and the objects are not there yet, usually because the Entra Connect sync has not run since the AD changes |
+run the sync first, run the Preview again, then the Apply |
+ |
Exchange Online session: wrong tenant (...) |
signed in to another tenant, or Cloud.Organization wrong |
fix Cloud.TenantId / Cloud.Organization |
+ |
uSNChanged changed: the object was modified since it was planned |
someone (or a sync) changed the object between plan and write |
run the command again (a new plan is made) |
+ |
Finalize: use the domain controller of the proof |
DomainController differs from the DC of the Recover AD phase |
set the same DomainController |
+ |
Expected state not reached (timeout or -Once) |
Exchange Online is slow (provisioning up to 60 min after a sync) |
run the cloud phase again later (-Phase Cloud -Batch <id>); nothing is granted twice |
+ |
Permission ... trustees missing in Exchange Online |
a permission holder is not known in Exchange Online (not synchronised) |
check that Entra Connect synchronises the holder, or exclude it (ExcludeTrusteeSamAccountNames) |
+ |
Trustee not found in Exchange Online at the pre-check: <upn> |
same, found before any AD write (phase Both) |
same; nothing was written |
+ |
▲ <mailbox>: N permission entries ignored, account unknown in AD (deleted, or from another domain): FullAccess S-1-5-21-... (warning) |
a permission entry of the shared mailbox points to an account that no longer exists ("Account Unknown") |
nothing to do: the other holders are granted. To clean the source: SendAs entries in Active Directory Users and Computers → account of the shared mailbox → Security; FullAccess entries are removed when Exchange is back (Remove-MailboxPermission). If the account belongs to another domain and must keep its access, grant it by hand in Exchange Online |
+ |
▲ <mailbox>: X500 missing in Exchange Online: X500:/o=... (warning) |
the cloud mailbox does not carry an older X500 address that the on-premises object had (the legacyExchangeDN of the mailbox itself is counted as present). The text says it is not serious: the mailbox works, and a reply to a very old message could bounce (IMCEAEX) until the address appears. The conversion itself is done |
check that Entra Connect synchronises proxyAddresses and legacyExchangeDN for the object (a customised or filtered rule, an object not yet synchronised, an empty legacyExchangeDN), run a synchronisation, then -Action Check -Batch <id>. Nothing is written by the tool |
+ |
Trustee without UPN / Unsupported trustee type |
a holder is an account without UPN, or a contact / computer |
give it a UPN, or exclude it (ExcludeTrusteeSamAccountNames) |
+ |
Apply needs a confirmation and this console cannot ask for one |
-Mode Apply in a non-interactive run |
add -Force |
+ |