Setup: Exchange 2007 with a separate PDC for it. We host 5 companies from this Exchange setup. These issue only exists for one (our largest though!) The other companies' email continue to work perfectly. Issue is with Lake Doctors, system's domain is called CFT-Hosted. All users have this issue, using Tim.Howard as a test Now onto the problem and the steps I have taken so far: _____________ Tim's account gives error in Outlook "the name cannot be resolved. The name cannot be matched to a name in the address list" This happens for all users, even ones previously working. People already setup can continue to work fine. Cannot setup Outlook for any user though. Researching this issue led me to ADSIEdit where I found each LD user was missing a line on the ShowinAdddressList entry that all other Hosted accounts have. I modified another company's entry to use for LD, entered under Tim's account to test. CN=Lake Doctors AL,CN=All Address Lists,CN=Address Lists Container,CN=CFT-Hosted,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=cft-hosted,DC=local Still could not setup Outlook as Tim. More research put me in the error logs where I found many (dozen plus) errors per second (filling the log as far back as I can see) from LDArchive failing to be authorized. I cannot log in as LDArhive (the account that receives copies of all in and outbound email)

You need to setup the Security Group and add that users in to that Security Group. I am sure you are havin this issue on the MAPI (Outlook) but user must be able to logon to the OWA.

Can you elaborate on what to setup for the security group? All users can use OWA properly.

how did you these domains? Did you create separate OUs for each of these domains? Can you check that if other users are part of any Security Groups?

Yes, each group has there own OU. All members are are part of Domain Users and Lake Doctors Default Security Group. To compare, the group that works properly are part of the Domain Users and (theirowncompanyname) Default Security Group. Everything matches between the working properly and non-working properly email domains.

Yes, each group has there own OU. All members are are part of Domain Users and Lake Doctors Default Security Group. To compare, the group that works properly are part of the Domain Users and (theirowncompanyname) Default Security Group. Everything matches between the working properly and non-working properly email domains. So - did you make these non working users to the part of Default Security Group?

They already were. I can see how its hard to decipher that from how I typed it but Lake Doctors userse are already part of Lake Doctors Default Security Group, just like the other company that works it part of that company's Default Security Group. Nothing has changed, this used to work, just quit recently with no known changes.

Now make sure these Lake Doctors are part of the Address List and you can see them in there. Update the GAL and Addresslist using PowerShell. Address List is a Must Do. they all should be able to see/access the AL.

I feel dumb asking this but; I looked around while researching this earlier, how do I check the address List? I think I found the Shell command to update (not positive) but I could not find the way to check to verify they are in the AL or GAL.

Someone please help, I am trying to figure out how to list all members of the AL and also the GAL. I believe all Lake Doctors users are in it but I cannot find a way to verify

run this powershell Get-Addresslist it will show all the address list then to update the AL and GAL run this Update-AddressList hit enter then type the name of the AL same for GAL Update-GlobalAddressList hit enter and type the name whoch should be Default Global Address List

I ran both of these and still get "The name cannot be resolved. The name cannot be matched to a name in the address list" I knew how to update them. Is there any way to view what is listed in each to verify they were added?

do you mind adding one of the user to the working users' security group?

I got it! Your previous suggestion worked afterall. Turns out the user I was testing with somehow lost his "Lake Doctor Default Security Group" membership (others didnt though). I fixed that then all users were able to verify. Thank you so much. If you're ever in Orlando, drinks are on me, just Google this name to find me :)

great to hear that it worked for you. good google results :) well I am sure if must be aware of user groups and I have tons to share on that. you can email me at adnan@techiesonly.com - stay in touch.