Why is Exchange 2016 working so different with Active Directory?

Hi there,

after some time working with Ex16 I am confused why Microsoft is doing some stuff so different than before:

1. When creating new modern public folders, the objects are created in the root domain and not the subdomain. This freaks out our AD guys

2. When we rename a (security/distr.)Group the change is replicated back to ad except for the canonical name.  This is also freaking out the AD guys

3. The most annoying Thing is, that Exchange is adding a randomnumber-suffix to Group-Names. This makes scripting very hard.

Any advice on how to handle that?

Who is Participating?
Kevin StanushConnect With a Mentor Application DeveloperCommented:
I should fire up E2016 before replying, but...

1. AD objects should generally never be created in the root of the domain, so any object creation should be prompted or geared toward creating the object in an existing OU/container.

2. Canonical name is a constructed AD attribute, so I assume you mean the 'cn' attribute, also just called the 'name'.  The technical term is 'common name'.  The name/cn is used in the directory path, either LDAP or the shortened distinguished name (DN), ie CN=SBrooks,CN=Users,DC=mydomain,DC=com.  'SBrooks' is the common name/cn/name of the directory object.  When you rename something in AD, this is the most important part, but the rename operation should also include, at the user's option, to rename the 'Display Name', User Principal Name, and the 'Sam Account Name' (Pre-Windows 2000 name).  So when renaming the object in the Exchange console, I can't tell from your post which attributes are actually renamed or not renamed.

3.  The numbers at the end of the 'name' look to me like an auto-generated SamAccountName (Pre-Windows 2000 name).  AD requires that users, groups, and computers have one, but if you don't specify one, then it will create one for you with a unique number on the end.  Again, you should be prompted for what you want the SamAccountName to be when creating an object as a lot of AD users will call this the 'account name'.  Let us know where in ADUC you are seeing this 'name', as there are at least three different things in AD that go by name.

IMO Microsoft should never have de-coupled AD and Exchange administration, but thats water under the bridge now...
1 where you installed exchange 2016 server, in root or subdomain?

2 right click renamed group and click rename, at that point it will allow you to rename both field

3 can you give any example?
Marcel_DAuthor Commented:
1. Ex16 is installed in subdomain
2. We want to use just the EAC for daily workloads but it seems that we also have to use ADUC to rename correctly.
3. In EAC I have created Group "Testgroup". In ADUC the Name is "Testgroup-2389072072"
MaheshConnect With a Mentor ArchitectCommented:
public folder or database are getting created in root domain only in configuration container
from sub domain u can connect to configuration container thru adsiedit and should see public folder. it will not get created in domain partition
configuration container is getting replicated to all domains

yes you do need to use aduc because name attribute would not get changed from eac

check if there is duplicate groups exists in ad
as far as I know , no changes have been done in ad and exchange integra
PberSolutions ArchitectCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- Kevin Stanush (https:#a42429939)
-- Mahesh (https:#a42430028)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.