Error creating shar…
 
Notifications
Clear all

Error creating shared Mailbox wit username "service"

5 Posts
2 Users
0 Reactions
1,360 Views
0
Topic starter

Hi

I’m trying to create a shared mailbox with username Service and e-mail-address service@cutomerdomain.tld for a new customer, but I receive the follwing error, when I want to save it:

“Active Directory operation failed on exchange.domain.local. The Object ‘CN=Service,OU=Exchange,OU=WET,OU=WOR,OU=Tenants,DC=domain,DC=local’ allready exists.”

Which isn’t true, there’s no such user, group and/or OU in the whole Active Directory.

When I use service1@customerdomain.tld I can save, without a problem. I can then change the e-mail-address manually to service@customerdomain.tld.

Am I missing something here, or is this a bug?

CloudPanel Version is 3.2.0320.0

Regards,
Roger

1 Answer
0

Service is a reserved word in Active Directory: https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou#table-of-reserved-words

Is your SamAccountName format set to 1 on the advanced settings instead of 0?

WBCH Topic starter 2021-02-17 08:38

Hmm, strange, this is the first time, that I ran into this problem, but I can confirm, that it’s also happening on our on premise exchange 2019, when I try to create a mailbox with the name.Service. What puzzles me is, that I can change everything to service after creating the mailbox with a different name.

And yes, SamAccountName is set to 1 in our CloudPanel Configuration

KMI Support 2021-02-17 08:40

We default the SamAccountName to 0 because it creates a unique SamAccountName and I think would avoid this situation for you. To get around this issue right now change your SamAccountName back to 0, create the user and then change SamAccountName back to 1. This value is only used when creating new accounts. The reason it is failing is because it is trying to use the wording before the @ for the SamAccountName and with your value set to 1, it is using “service” instead of something like “service_companycode”

WBCH Topic starter 2021-02-17 08:54

Just tried it wit SamAccountName set to 0, but I get the same error message, anyway, creating it with service1 and then changing the e-mail-address manually to service seems to be working.

looks like we are never to old to learn something new 🙂

Thanks!

KMI Support 2021-02-17 08:55

Interesting. I will have to try to reproduce this with the SamAccountName set to 0 and see what it does. Glad you found a solution though!

Share: