Follow the install guide and you should be OK. Just remember you need to make sure you have an emergency account just in case AD is not available.
Good suggestion Robert. One thing that tricked me for a minute is that I believed this "emergency" account needed to only be local to Control-M/EM. What I mean is that I started off making the emergency account emuser; however, I found out I could also make ME an emergency account also. Control-M/EM will use AD when available and then the Control-M/EM password if AD is not.
I follow all steps that the manual guide me. I tried to create emergency user and results was not sucessfully.
After that the GUI Server, GAS , GCS and CMS server desappear from EM configuration and it was not be able to create those components. I re installed the EM and I need the aditional steps to configure AD integration.
Did you run the prep step as outlined in the manual? You cannot just turn on AD there is an intermediatary step to do the prep first.
1 of 1 people found this helpful
There is a bug in ctm 7 and support is working on it.!!!
Somebody know anything else about this error?
GUI Server CTL Request Failed. Machine: hipnos01, Type: GUI_Server, Name: ; Code: 34
GAS CTL Request Failed. Machine: hipnos01, Type: GAS, Name: ; Code: 34
BIM CTL Request Failed. Machine: hipnos01, Type: BIM, Name: ; Code: 34
It was show after Activate changes on EM System Configuration.
HI Camilo ,
Have you complted this activiy?
i am getting same error, and what have you done for this?
Hi Mohamed, you must complete all parameters in format "FQDN" Control-M does not search over referals info.
My LDAP authentication is working.
By the way you must active debug level and check those logs.
I have sucessfully integrated with LDAP , infact my mapped the group with Control-M.
Is it possible to Write a Code that will Access LDAP Server from within Control-M?
I am currently trying to achieve this Control-M/EM LDAP Integration and was wondering if you have some docs that can guide me on how to do it.
I have followed the technical white paper from BMC support site but unfortunately I am still getting issues with communications between my EM and that of the AD via port 636.
Should also mention that that when this connection is using SSL (instead of plain TCP) then 2048 bit certificates are not yet supported (support will be added in the future, poss Q1 2015).