Hi Eric Logsdon
Based on the checks you’ve already performed (connectivity, time sync, WMI, and confirmation that the object exists and the mailbox is functional), this does not appear to be an infrastructure or communication issue.
To help narrow this down, could you try resolving the mailbox using different identity formats to see how Exchange is interpreting the object? For example:
Get-Mailbox "Sample User"
Get-Mailbox ******@domain.com
This can help determine how the identity is being resolved in the current session. If the display name does not return any results while the SMTP address does, it may indicate that the object is not being resolved consistently in the current context.
Also, since the Exchange server is only started occasionally, the current session may be limited in scope. You can expand it to include the entire forest with:
Set-ADServerSettings -ViewEntireForest $true
After that, run Get-Mailbox again to confirm whether the object is visible.
If the issue still persists, it would be helpful to check whether Exchange can see the object through Get-Recipient, and optionally test against a specific domain controller to rule out any directory replication inconsistencies.
Please let us know how it goes once you’ve had a chance to try this.
We assume that “Doe, John” is a placeholder name and does not reflect the actual user.
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.