v3.6.0 does not find all Outlook mailboxes

[GruberMarkus]

Discussed in #74

^{Originally posted by KoenBouten April 28, 2023}
Hello Markus,

Here you have the text file with the output of the 3.6.0 script which you asked for last time.

But there was one thing I found in the meantime:

3.3.0 = line 748
3.6.0 = line 744
The script displays things in a different order/way at this part.
(domainD.local is a one-way-domain-trust & domainH.nl is a forrest-trust)

I hope this will be enough information.

Script output V3.6.txt
Script OutputV3.3.txt

[GruberMarkus]

Hi @KoenBouten,

the log files tell me the following:

ISSUE A: 3.6.0 DOES NOT FIND ALL OUTLOOK MAILBOXES
The problem that v3.6.0 does not find all mailboxes configured in Outlook but v3.3.0 does, is already fixed in the code for the upcoming version 4.0.0. The fix will not be backported. I currently can not communicate a release date or timeframe for v4.0.0, as not all new features have been completed by now.

ISSUE B: TRUST NOT WORKING
The client and/or user running Set-OutlookSignatures can not connect to 'domainD.local':

Check trusts for open LDAP port and connectivity @2023-04-28T09:32:39+02:00@
  domainA.local
    LDAP query successful
  domainH.nl
    LDAP query successful
  domainD.local
    LDAP query failed, remove domain from list.
    If this error is permanent, check firewalls, DNS and AD trust. Consider parameter TrustsToCheckForGroups.

If 'domainD.local' contains information relevant for Set-OutlookSignatures, your need to make sure that the client and user running Set-OutlookSignatures can use the trust.

If 'domainD.local' doest not contain information relevant for Set-OutlookSignatures, ignore the error or follow the recommendatation given in the error message.

ISSUE C: Current user has no mail attribute set
The user running Set-OutlookSignatures, 'CN=Koen Bouten,OU=Users,OU=domainA,DC=domainA,DC=local' does not have the 'mail' attribute set in Active Directory:

Get AD properties of currently logged in user and assigned manager @2023-04-28T09:32:44+02:00@
  Currently logged in user
    User's mailbox not found in Outlook profiles, but Outlook Web signature and/or OOF message should be set. Add dummy mailbox entry.
      User does not have mail attribute configured
    CN=Koen Bouten,OU=Users,OU=domainA,DC=domainA,DC=local

If 'CN=Koen Bouten,OU=Users,OU=domainA,DC=domainA,DC=local' does not have a mailbox, this is ok.
If 'CN=Koen Bouten,OU=Users,OU=domainA,DC=domainA,DC=local' does have a mailbox:

• If the mailbox is on-prem, your Exchange/AD configuration for at least this mailbox is wrong. There may be more error than just a missing 'mail' attribute.
• If the mailbox is in the cloud:
  • If you run in hybrid mode, make sure you sync all the attributes between Exchange Online and Exchange on-prem which are required for a Microsoft supported environment.
  • If you run in Exchange Online only, consider using the 'GraphOnly' parameter of Set-OutlookSignatures.

I think you are running your Exchange environment either fully on-prem or in hybrid mode:

Get AD properties of each mailbox @2023-04-28T09:32:44+02:00@
  Mailbox 'k.bouten@domainA.com'
    Search for mailbox user object in domain/forest 'domainA.local': Not found
    Search for mailbox user object in domain/forest 'domainH.nl': Found
      CN=Koen Bouten | SAM Office BV,OU=Users,OU=H31(domainA),OU=Klanten,DC=domainH,DC=nl

The script seems to run fine, of course with the constraints resulting from issues A, B and C.
I do not not see anything else in the log file, that would concern me. Am I missing something?

[KoenBouten]

Hi @GruberMarkus

Thank you for your anwser.

For Issue A: Then I will use version 3.3.0 until 4.0.0 comes out.
For Issue B: domainD is a management domain with no mailbox related information.
For Issue C: user object is located in domainA and has a linked mailbox in domainH.

I am a trainee at the moment, so my account doesn't have all rights available. So most things 'work' as intended at my organization.

[GruberMarkus]

So we can just ignore issues A and B.

Let's focus on issue C now.

Your maibox is running in a resource forest scenario: You have a user in AD forest A, Exchange is running in AD forest D. The user from forest A is configured as linked account (a.k.a. external master account) on a mailbox in AD forest D.

This configuration is nothing uncommon, and it is supported by Set-OutlookSignatures (other products do not have this feature).

Microsoft does not required to set the mail attribute on the user in AD forest A, and you have not done this. Set-OutlookSignatures logs this with this text:

Get AD properties of currently logged in user and assigned manager @2023-04-28T09:32:44+02:00@
  Currently logged in user
    User's mailbox not found in Outlook profiles, but Outlook Web signature and/or OOF message should be set. Add dummy mailbox entry.
      User does not have mail attribute configured
    CN=Koen Bouten,OU=Users,OU=domainA,DC=domainA,DC=local

The mail attribute of the currently logged in user is important for Set-OutlookSignatures, as the mailbox of the currently logged in user has highter priority than other mailboxes. As the mail attribute is not set, Set-OutlookSignatures tries to find the mail address by searching for a mailbox in AD, where the user from AD forest A is set as linked account. The search is successful:

Sort mailbox list: User's primary mailbox, mailboxes in default Outlook profile, others @2023-04-28T09:32:44+02:00@
  AD mail attribute of currently logged in user is empty, searching msExchMasterAccountSid
    One matching primary mailbox found: k.bouten@domainA.com
  Mailbox priority (highest to lowest)

The lines following are a symptom of the bug in v3.6.0 which is already fixed in the yet unreleased version v4.0.0.:

VERBOSE:   Outlook mailbox display sort order is not yet defined or does not yet contain all found mail addresses. Falling back to sorting by time mailboxes
 have been added.
    k.bouten@domainA.com
VERBOSE:       Outlook profile 'Outlook'
VERBOSE:         HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Outlook\9375CFF0413111d3B88A00104B2A6676\00000002
VERBOSE:         /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=cdb645573cba43a8a87b3ccf02b499bc-Koen

All in all, I would say issue C is not a problem, but a configuration that is

• supported by Microsoft
• supportet by Set-OutlookSignatures
• has no impact on how Set-OutlookSignatures works
  and is therefore not a bug.

I think, we can close this issue. Do you agree?

[KoenBouten]

Hi Markus,

I agree.
Thank you for your help.

[GruberMarkus]

My pleasure!