BigFix MCM Enrollment issue

Usage and Config MDM
1

All, I’ve updated my MCM Environment to version 3.3 and since them I’m not able to enroll any device anymore. This is PoC so no real production impact but like to have this resolved.
I was able to enroll devices when using 3.2 or earlier.
The error I’m getting

image
image896×537 86.1 KB

Before anyone asks about the WNS Push credentials, does not have anything to do with that with regards to the enrollment. I was able to enroll devices while the credentials did not work either. It has nothing to do with the LDAP credentials they work fine also and the lookup of my name agains the directory is done correctly.

I’ve also opened case with HCL Support on this, but they are also looking in direction of Credentials, but did found below article talking about configuring MCM in a Pull environment where the client checks every xx minute for any push actions, and that is working just fine.
Any advise suggestion are welcome

Thx!

2

Can you verify that the Id Service still reflects the correct domain pg.com ?

/var/opt/BESUEM/.env

Lines similar to

LDAP_AUTH=true

CONNECT_TO=activeDir

LDAP_URL=ldaps://mypdc.mydomain.com:3269

BASE_DN=dc=mydomain,dc=com

3

you might also verify the LDAP connection is good. This might have been suggested by support already.

docker exec -it idservice sh

cd bin

./BESmdmldaputil -a your_user:your_password

Then review the /var/opt/BESUEM/idserivce/logs/mdmldap.log

Then again, this issue might already be resolved

4

Thx for the info but already checked this and also run the commandline (Suggested by HCL Support). I’m still convinced this has nothing to do with LDAP Authentication, but will wait on support got troubleshooting session today hopefully will find some answers on why this is happening.