My Support employee has changed settings for a customer with Exchange ECP. after he has saved the changes the UPN of the customer is lost and changed to the default internal (AD) domain name.
Is their a way to fix this behavior of exchange without adding the domain to AD’s Domain and Trust?
i personally don’t mind because i use powershell, but from the support / service desk site looking i can see some issues in this.
additional: with this problem also the user cant login to RDS, Reason: the specified user account does not exist.
Do you have your OWA virtual directory set to authencitation –> UPN ? (instead of the default)
That should normally fix this problem.
Thanks for your quick answer, i’ve changed from default to UPN after this iisreset, but problem remain the same form the ECP side.
you can set the login name of the user in the SolidCP mailbox page to the previous UPN and then save this mailbox in SolidCP. This will set the default UPN for this User back.
I don’t think it’s possible to Safe the mailbox in ECP without adding this domain to AD. ECP shows only these domains and if it won’t find it, it will set it to the local domain, which will break the UPN.
The UPN Login change should of worked (please check my screenshot)
Aslong as it lists the @domain.com correct it should not overwrite or change the UPN.
When i open this screen i see that it quickly change from customerdomain.nl to internaldomainname.nl.
now comes the weird part, my test account displays correctly but after removing this account and recreate it, it gets the same weird problem (changed when opening by ECP)
Exchange 2016 CU 10 (DAG)
[10/22/2018 10:09:02 PM] WARNING: Exchange Invoke error: Cannot open mailbox /o=COMPANY/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Server Nane/cn=Microsoft System Attendant.
[10/22/2018 10:09:06 PM] WARNING: Exchange Invoke error: The Archive Mailbox is not enabled for Test User.
[10/22/2018 10:09:27 PM] WARNING: Exchange Invoke error: The operation couldn’t be performed because object ‘email@example.com_members’ couldn’t be found on ‘Domain Controller Server Name’.
[10/22/2018 10:09:27 PM] WARNING: Exchange Invoke error: The operation couldn’t be performed because object ‘firstname.lastname@example.org’ couldn’t be found on ‘Domain Controller Server Name’.
hmm, for me it stays (on all accounts)
Though to be honest i tried alot of different solutions since exchange 2010, i did think just changing the OWA to upn solved it for me.. but maybe it has been a combination.
I know for sure if you add the domain to Domain suffix in AD it stays (i didn’t do that for solidcp.com but that was one of my findings back in 2010 or something).
I will double check my dev lab on this (as it doesn’t got any modifications like my live).
The errors/ warnings you got is correct, it basically checks all perm settings and compares them with mailbox (which the default groups ofcourse don’t have) it’s a bit sloppy but it’s nothing to worry about.
It seems to be AD related, exchange and rds can’t find the domain name (UPN).
if you run Get-UserPrincipalNamesSuffix do you see other domains except solidcp.com?
I do but it co-relates to the Alternative UPN Suffixes i think.
Maybe we can look into automating those (add/remove) for SolidCP
but i am not sure if it then requires the AD DNS settings for that domain aswell.
- Views2053 times
- Answers12 answers