This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(172.8, 23%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EOE%3C/text%3E%3C/svg%3E)
Hybrid setup. User has Archive State "HostedPending" in Exchange 2013 on prem.
I can change the msExchArchiveStatus in local AD with ADSI Edit, but AD Connect will delete the attribute value
PS> Get-Mailbox user@keyman .com |fl Name, Archive*
Name : Username
ArchiveDatabase : EURPR08DG125-db124
ArchiveDatabaseGuid : bb2430a9-7493-4a5d-ad11-6369eec09041
ArchiveGuid : 347b063f-e279-48cb-a648-86351c5bbb75
ArchiveName : {Online Archive - Username}
ArchiveQuota : 100 GB (107,374,182,400 bytes)
ArchiveWarningQuota : 90 GB (96,636,764,160 bytes)
ArchiveDomain :
ArchiveStatus : None
ArchiveState : Local
ArchiveRelease : E15
A newly migrated cloud user got their Archive State set to "HostedProvisioned" after enabling the archive. This problem seems to be isolated to a number of previously migrated users.
Not sure I understand. Why are you setting that via adsiedit?
I have some users in Exchange Online with archive enabled. On the on-prem Exchange these users have Archive State: HostedPending.
Their msExchArchiveStatus in local AD should be 1. By manually changing it to 1 and then running AD Sync I can see that AD Connect is deleting that value, which it shouldn't.
Does the archiveguid in ExO match the one one prem for the remote mailbox?
If you disable the archive, resync to Azure , does the archive in Exo get disabled as well?
I've checked and it's a different GUID in ExO compared to on-prem. If im looking at the correct attribute: msExchArchiveGUID
Will disabling and enabling the archive wipe it? In that case i need to backup first as the accounts are live.
![](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(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi @Ole Erik Skare , is there any update about your issue?
![](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(195.2, 0%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
@Ole Erik Skare
I wanted to follow up and know if the below response helped in answering your query. If it did, please accept the appropriate response as answer for the benefit of community. If it did not, please let us know so that we can help you further.
Hi @Ole Erik Skare , do suggestions below help?
Hi @Ole Erik Skare , changing the value in ADSIEdit only will not update the real status of the mailbox archive status.
Please make sure you have followed all steps right list in this official document: Create a cloud-based archive for an on-premises primary mailbox in an Exchange hybrid deployment
Or you could use the command below to create a remote archive for the existing on-premises user
Enable-Mailbox "" -RemoteArchive -ArchiveDomain "domain.mail.contoso.com"
Detailed information and usage about the cmd Enable-Mailbox
After you finish the steps above successfully, (Optional) run directory synchronization
Start-ADSyncSyncCycle -PolicyType Delta
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I don't see how this would be relevant.
If they don't match, then you need set the on-prem to match the cloud one ( Which I assume the user can access yes?)
Follow the steps here:
https://support.microsoft.com/en-us/help/4053483/failed-to-sync-the-archiveguid-or-enable-the-new-cloud-archive
Set-RemoteMailbox John -ArchiveGUID CloudArchiveGuid
the let AADConnect do its thing and sync
I will try this and revert.
That link is broken, but I tried the following with this result:
Set-RemoteMailbox username@keyman .com -ArchiveGUID 347b063fe27948cba64886351c5bbb75
WARNING: The command completed successfully but no settings of 'domain/Azure AD
users/username' have been modified.
Exchange online: ArchiveGuid: 347b063f-e279-48cb-a648-86351c5bbb75
Can you post the following:
From On-Prem:
get-remotemailbox <user> |FL *archive*
From Exchange Online:
get-mailbox <user> |FL *archive*
On Prem:
get-remotemailbox user@domain.com |FL *archive*
ArchiveState : HostedPending
ArchiveGuid : 347b063f-e279-48cb-a648-86351c5bbb75
ArchiveName : {Online Archive - Username}
ArchiveQuota : 200 GB (214,748,364,800 bytes)
ArchiveWarningQuota : 185 GB (198,642,237,440 bytes)
ArchiveDatabase :
ArchiveStatus : None
DisabledArchiveDatabase :
DisabledArchiveGuid : 00000000-0000-0000-0000-000000000000
JournalArchiveAddress :
ArchiveRelease :
Exchange Online:
get-mailbox user@domain.com |FL *archive*
ArchiveDatabase : EURPR08DG125-db124
ArchiveDatabaseGuid : bb2430a9-7493-4a5d-ad11-6369eec09041
ArchiveGuid : 347b063f-e279-48cb-a648-86351c5bbb75
ArchiveName : {Online Archive - Username}
JournalArchiveAddress :
ArchiveQuota : 100 GB (107,374,182,400 bytes)
ArchiveWarningQuota : 90 GB (96,636,764,160 bytes)
ArchiveDomain :
ArchiveStatus : None
ArchiveState : Local
AutoExpandingArchiveEnabled : False
DisabledArchiveDatabase :
DisabledArchiveGuid : 00000000-0000-0000-0000-000000000000
ArchiveRelease : E15
![](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(243.2, 24%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
Hi,
can you also verify that the your Directory Sync Client version is upto-date as well on your directory sync server?
Cheers.
Yes, recently reinstalled on new server so this should not be a problem.
Ok, so it matches, but then it gets deleted?
Can you run a full AADConnect sync? ( Note that this may take a few hours)
One thought is that something isnt getting picked up correctly in the delta syncs
Start-ADSyncSyncCycle -PolicyType Initial
ArchiveGUID seems to be the same and stays the same after full AD Sync.
When looking at the user in ADSI the "msExchArchiveStatus" is empty. I can change it to "1", but AD Sync will delete the value of this attribute. You can refer to my original post for screenshots of this occuring.
When looking at msExchArchiveGUID it has a different value than ArchiveGUID from online and on-prem. I don't know if that matters.
What is the value of msExchRemoteRecipientType for this user?
or
get-remotemailbox <user> |FL *rec*
get-remotemailbox user |FL *rec*
RemoteRecipientType : Migrated
RecipientLimits : Unlimited
SingleItemRecoveryEnabled : False
RecoverableItemsQuota : Unlimited
RecoverableItemsWarningQuota : Unlimited
ExternalDirectoryObjectId :
MaxReceiveSize : Unlimited
RecipientType : MailUser
RecipientTypeDetails : RemoteUserMailbox
What you see with msExchRemoteRecipientType is in Hex, so thats expected.
Have you tried disabling the remote mailbox on-prem . re-syncing to 365, then re-enabling the remote mailbox and then re-enabling the archive and re-sycning? Not sure with all the comments in this thread :)
This and the other mailboxes with this issue was synced half a year ago or so. There is nothing to be re-synced.
I guess something similar would be to disable the archive (i think this will delete it in ExO), then re-enable and restore all items in the archive from a backup.
Right, but I can't tell you how many times I have fixed similar issues like this but either disabling the remote mailbox and re-enabling or simply touching the remote mailbox on-prem and resyncing. Changing the Display Name and doing a sync has actually fixed stuff.
just as aside, is there any similarity with the mailboxes having this issue?