Inplace Archive - Shared mailbox Onprem

Question

Inplace Archive - Shared mailbox Onprem

cruiser082 1

Hi, I'm trying to setup archiving for a shared mailbox that is onprem exchange 2016. I've set the inplace archive via EMC and can see the online archive in outlook for the shared mailbox, the appropriate retention policy has also been applied that works for other mailboxes. When I attempt to check the status of the mailbox using "get-mailbox redacted -archive|fl archive" it says the following "archive status - none". I've also attempted to use the following but it reports it as offline as well "Start-ManagedFolderAssistant -Identity redacted.

Any help or suggestions would be greatly appreciated.

1 answer

Your answer

Answer 1

Yuki Sun-MSFT 41,451 Moderator

Hi @cruiser082 ,

When I attempt to check the status of the mailbox using "get-mailbox redacted -archive|fl archive" it says the following "archive status - none".

This is the expected behavior. As according to the explaniation in the following document, the ArchiveStatus property value is only used in a cross-premises scenario, for all other scenarios, we should use both the ArchiveDatabase and ArchiveGuid properties to confirm the status of the archive:
ArchiveStatus shows None

I tried running the command "get-mailbox <user> -archive|fl archive*" for a normal user mailbox in my onprem Exchange environment, and is displayed in the screenshot below, it also shows "archive status - none", but both the ArchiveDatabase and ArchiveGuid properties have valid values:

I've also attempted to use the following but it reports it as offline as well "Start-ManagedFolderAssistant -Identity redacted.

Have you tried running the Start-ManagedFolderAssistant cmdlet on another mailbox and see how it goes? If the offline warning only occur to this particular shared mailbox, please run the command below and check the result:

Test-ArchiveConnectivity <******@domain.com>

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.

cruiser082 1 Reputation point

2021-07-22T05:02:05.023+00:00

Hi @Yuki Sun-MSFT
I ran Start-ManagedFolderAssistant on another mailbox that is archiving and got the same message about it being offline. I did also run the "Test-ArchiveConnectivity" and can confirm that the result was the same as your screenshot advising it could successfully login to the Archive mailbox and that the IsValid is Truen and in a New state.
Yuki Sun-MSFT 41,451 Reputation points Moderator

2021-07-22T05:50:23.71+00:00

Hi @cruiser082 ,

I ran Start-ManagedFolderAssistant on another mailbox that is archiving and got the same message about it being offline.

Then it seems that the issue is not with a particular mailbox. May I know if it's a recently occurred issue or it's the first time that you tried to run the Start-ManagedFolderAssistant cmdlet on this server?

Besides, please have a look at the Event Viewer on the Exchange server where the archive mailboxes are located and see if we can find any clues there.

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.
cruiser082 1 Reputation point

2021-07-22T06:11:48.163+00:00

Hi @Yuki Sun-MSFT
I've tried the start-managedfolderassistant a few times now over the weeks with this particular mailbox.

Are you able to advise where these log files would be in event viewer, I'm still learning with exchange.
Yuki Sun-MSFT 41,451 Reputation points Moderator

2021-07-22T09:26:46.263+00:00

Hi @cruiser082 ,

Normally we would open Event Viewer, then go to Windows logs > Application, you can right click on "Application"and choose "Filter Current Log...", select "Error" so to see all error events:

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.
cruiser082 1 Reputation point

2021-07-26T05:11:20.107+00:00

Hi @Yuki Sun-MSFT

I have checked the event viewer logs and can confirm I can't see any errors relating to the DB.
Yuki Sun-MSFT 41,451 Reputation points Moderator

2021-07-28T12:55:30.737+00:00

Hi @cruiser082 ,

Found the following thread which discussed a similar issue:
On-Prem In-Place Archiving and Retention
According to the solution shared there, the issue was finally fixed by configuring .NET Framework to support strong cryptography. So I'd recommend having a go and checking if it works for your scenario as well.

To do this, you can refer to the article mentioned in that thread or following this document to add the registry keys after backing up. Or you may simply download the .txt file attached(118693-strongcryptography.txt), change the extension to .reg, then double click the .reg file to run it on your exchange server 2016 so that the registry keys can be imported.
Yuki Sun-MSFT 41,451 Reputation points Moderator

2021-08-04T04:36:07.987+00:00

Hi @cruiser082 ,

Just checking to see if there are any updates. If you have any questions or need further help on this issue, please feel free to post back.

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.
cruiser082 1 Reputation point

2021-08-10T03:11:33.677+00:00

Hi @Yuki Sun-MSFT
No, I've not tried that option as we have other mailboxes with the archiving option enabled and are working. I don't believe that making the suggested change will resolve the issue.
Yuki Sun-MSFT 41,451 Reputation points Moderator

2021-08-11T07:08:52.943+00:00

Hi @cruiser082 ,

we have other mailboxes with the archiving option enabled and are working.

In this case, agree with you that the suggestion provided earlier may not help and apologize for that I thought the issue was affecting all archiving mailboxes in my previous posts.

Given current situation, have you noticed if there are anything in common on the problematic archiving mailboxes, like if thet all belong to a particular mailbox database?
How about moving one of the affected archiving mailbox to another mailbox database and see if it can be fixed?

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.

Share via

Inplace Archive - Shared mailbox Onprem

1 answer

Your answer