1 Reply Latest reply on Jul 13, 2016 3:57 AM by acocimano

    LDMS 2016 issues after in-place upgrade with LDAP scopes

    hp14 Rookie



      I was forced to upgrade my LDMS 9.6SP2 and made an in-place upgrade in the past days. So I'm running now. After beginning the roll-out  of new agents (upgrade) I encountered an issue with the LDAP scopes I use. In the past with 9.6 this worked quite well and now it seems that I get only distinguished names if the client has a new agent installed and not that "fake" LDAP tree. Any idea how to get rid of these DNs? Will this behaviour change if the last client is upgraded?



      Any help would be appreciated.