Questions[adsi](server)

In my test windows AD server I was checking out ADSI (adsiedit.msc). From this doc, I can make config changes to ADSI that allows me to monitor changes from Domains, OU deletions, etc.

I decided to take a look ADSI. When I got to the Auditing Entry for (my domain) below, I saw Permissions and Properties:

Does anyone know what permissions and properties do? For example, if Principal is set to Everyone and Full control was checked, does this change everyone's permissions to full overriding AD settings?

I did some reading and found some info on what it is but I couldn't find any other details on what changing these auditing settings (Permissions and Properties) do aside from what the doc provides.

I need to modify access rights in Azure Active Directory Domain Services (AD DS) for a specific container in ADSI.

Usually in an on-prem Active Directory this is possible with having the correct access rights on an object and changing the Control Access Right (ACE) in the Access Control Lists (ACL) of the object. This usually means I need Enterprise / Domain Admin Rights in the first palace to modify the object rights.

In Azure Active Directory Domain Services (AD DS) Microsoft limits the environment by the following: Domain Administrator and Enterprise Administrator privileges aren't available. The only way to administer the domain is the usage of users in the Group "AAD DC Administrators" which does not have access to the Container Rights: Screenshot of the Container ACL

Is there a way to modify the permission on the ADSI Object somehow without the Enterprise / Domain Admin Rights? Or is there a way of setting additional permissions directly through Azure?

We have an old server that has suffered numerous hardware and software problems over the years. We want to simply get rid of the old Exchange 2013 server and start fresh with a new Windows 2019 + Exchange 2019 installation.

As a precaution I tried to uninstall Exchange 2013 from the old server but the box is too messed up. Uninstall fails.

What's the best approach? Do I need to go into ADSI edit and start cleaning up AD for the old server? Or just remove the old server from the domain and create a new Exchange 2019 server? I've read mixed advice about the need to remove the software, risk of cleaning up AD which may prevent new server from installing, etc. See this detailed walk through

(I have exported mail at the client level - so there is nothing I need to save).

An admin in the organization ran /PrepareSchema from an Exchange 2019 ISO and it succeeded. The following day their application vendor said Exchange 2019 is not supported for mail integration. So the admin decided to continue Exchange migration by running /PrepareAD from an Exchange 2016 ISO and it succeeded. Now I have a source Exchange 2013 server with the following AD attributes:

1. Schema rangeUpper: 17001

2. Exchange Organization Object Version 16217

3. Exchange System Object Version: 13237

The goal is to Migrate from Exchange 2013->2016.

Since there is not going to be an Exchange 2019 server, can I still proceed with installing Exchange 2016 even though the Schema has already been extended for Exchange 2019?

I'm using the same userID, LDAP connection string to bind to an LDAP server and fetch information.

• Tool #1 exposes the msExchMailboxGuid consistently and reliably.

• Tool #2 (.NET) doesn't expose the msExchMailboxGuid. There are occasions where it's null, and other instances where it isn't.

(Note: I'm not looking for code /developer support)

       DirectoryEntry de = new DirectoryEntry();

        de.Path = "LDAP://ldap.exchange.serverdata.net:636/DC=exchange,DC=serverpod,DC=net";
        de.Password = "PASSWORD";
        de.Username = "[email protected]";
        de.AuthenticationType = AuthenticationTypes.Secure;

        DirectorySearcher ds = new DirectorySearcher();
        ds.PropertiesToLoad.Add("cn");
        ds.PropertiesToLoad.Add("mail");
        ds.PropertiesToLoad.Add("samAccountName");
        ds.PropertiesToLoad.Add("msExchMailboxGuid");
        ds.PropertiesToLoad.Add("proxyAddresses");
        ds.PropertiesToLoad.Add("targetAddress");

        ds.PageSize = 800;
        ds.Filter = "(&(objectCategory=person)([email protected]))"; 

        SearchResultCollection results = ds.FindAll();

This code is very simple, but when I substitute [email protected] with [email protected], the attribute is gone. (but is visible in other tools)

Is there any logical AD reason why an attribute would be missing under certain circumstances? What are those circumstances?

How can I debug this kind of LDAP query?