I'm trying to create an Auto-Discovery group and filter this by the option:

Use computers from the active directory (maximum 1000 computers).

When entering the following string into the Organizational Unit box:

OU=Name of OrgUnit,OU=LowerName,OU=LowerName,DC=DOMAIN,DC=SUFFIX

I receive the following error message:

Error (Bad Request) The validation of at least one of the new objects failed because of the following: Active Directory cannot be accessed for "IP Selection" (Auto discovery setting)

I have tried to amend the Organizational Unit string with the following alternatives but still this does not work.

   Name of OrgUnit,OU=LowerName,OU=LowerName,DC=DOMAIN,DC=SUFFIX
  "Name of OrgUnit",OU=LowerName,OU=LowerName,DC=DOMAIN,DC=SUFFIX
  "Name of OrgUnit,OU=LowerName,OU=LowerName,DC=DOMAIN,DC=SUFFIX"
  "OU=Name of OrgUnit,OU=LowerName,OU=LowerName,DC=DOMAIN,DC=SUFFIX"

None of the above have worked.

Article Comments

You need to go over to Setup -> System Administration -> Core and Probes, and then put in the AD Domain, and tell PRTG how to authenticate to it. This doesn't do a join to the domain, just gives PRTG credentials to authenticate to the domain for things like adding computers from an OU, and added a user group that is tied to an AD group.

Benjamin Day
Paessler Support


Aug, 2018 - Permalink

I'm afraid I still have the same issue, even after changing the Core Probes service account (to an specific PRTG account that is a domain Admin) and then after this didn't work, manually setting these settings you describe with the active directory account I am using to connect to the AD.


Aug, 2018 - Permalink

Try just entering the name of the OU without the nomenclature you are using.

I don't think PRTG needs all that information.

Benjamin Day
Paessler Support


Aug, 2018 - Permalink

I have tested numerous variations but none work. Even testing with an OU that has no spaces does not work.

I have tried the following and each time I receive the same error message.

ou=name,OU=name,OU=name,DC=domain,DC=suffix

- or -

name,OU=name,OU=name,DC=domain,DC=suffix

- or -

name,OU=name,OU=name,DC=domain.suffix

Is there not a definitive guide to using this feature that tells you exactly what you need to enter?


Sep, 2018 - Permalink

Sorry but:

Name,OU=Name,OU=Name,DC=Domain,DC=Suffix

Still results in the same error.


Sep, 2018 - Permalink

Hi,

No, I meant just type in the name of the OU.

As in "Computers" or "Servers". We will poll AD for the name. Just make sure the OU contains a host.

Benjamin Day
Paessler Support


Sep, 2018 - Permalink

Benjamin,

Im sorry but you're not being clear.

Whoich of the following is correct?

OU=name,OU=name,OU=name,DC=domain,DC=suffix - or - name,OU=name,OU=name,DC=domain,DC=suffix - or - name,OU=name,OU=name,DC=domain.suffix


Sep, 2018 - Permalink

Hi there,

Could you try the following:

name,OU=name

As PRTG is already connected to the domain, it is not necessary to add the "DC="-suffix.

Best regards


Sep, 2018 - Permalink

Hi,

The following did not work:

OU=Name,OU=Name,OU=Name

However, this did work:

Name,OU=Name,OU=Name

Thank you for the help. May I suggest paessler updates its documentation so that future users know the exact requirements for this function.


Sep, 2018 - Permalink

Hi there,

The documentation actually mentions this, more or less:
Make sure that the OU contains a host. If the OU is empty, you will receive an error message.

If you have sub-OUs, consider the correct syntax in the format Y,OU=X: OUs that are part of another OU have to be listed together with their parent(s). Enter the sub-OU followed by ,OU= and the name of the parent OU.

Examples:

  • Assuming that the organizational unit 'Y' is part of the OU named 'X'. Then the syntax would be Y,OU=X
  • For three OUs 'X', 'Y' part of 'X', and 'Z' part of 'Y', the syntax would be Z,OU=Y,OU=X The order is important, sub-OUs have to be listed left of their particular parents!

    Best regards.

Sep, 2018 - Permalink

The guidance on creating an Autodiscover group does not mention anything of the above.

What you have to guide you is the following:

Optionally enter a string to define an organizational unit (OU) if you want to restrict the active directory search to computers that are part of this OU. You can leave this field empty if you do not want to restrict the search. 

Note: Ensure that you set the correct domain name for your active directory. Check this in the System Administration settings, section Active Directory Integration in Server & Probes. Also ensure that the OU contains a host. If the OU does not contain a host, you will receive an error message.

Further Help (Manual)

The Further Help (Manual) link takes you to:

Use computers from the active directory (maximum 1000 computers): Search in the active directory for computers to perform auto-discovery.

Define your active directory domain in advance in the system administration. 
See System Administration—Core & Probes.

Following the System Administration-Core & Probes link takes you to the Active Directory Integration section which also has none of the information you have provided.

This is why I suggest you update your guidance.


Sep, 2018 - Permalink

Hi there,

Unfortunately, the "Further Help" does not have many anchors, which is why you start the sensor settings. When you scroll down, you will see the information about the "Organizational Unit"-setting.

Best regards.


Sep, 2018 - Permalink