AD Discovery Schedules are not working properly when containing a space (4324474)

Active Directory (AD) Discovery Schedules may not work anymore as expected. After the upgrade you may find some of the schedules missing the missing green check-mark as shown in the below screenshot:

When attempting to run the task, nothing seemingy happens and no results for this discovery will appear.

The issue has been filed internally under the defect #K1-17185 and will be fixed in a future release.

Spaces inside the distinguishedName specified inside the discovery schedule causes the problem.

The following distinguishedName has a space in the "All Computers" OU:

OU=All Computers,DC=rootdom,DC=local (example)

Configure the distinguishedName inside the discovery schedule as follows:

OU=All%20Computers,DC=rootdom,DC=local (example)

NOTE: "%20" or "/20" can be used to escape the space inside the string.