RE: [ActiveDir] ADAM attribute value

[Harpreet_Kapoor]

Hi Carlos,   In case you cannot send the tool, will you have a look at my code again & suggest the changes that I need to incorporate…   Also, I tried setting RootDSE in accordance with your article. For this, when I tried connecting to from the “Distinguished Name or naming context” textbox by giving CN=NTDS Setting,CN=computerName$instanceName,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={GUID} after replacing the computername, instanceName & GUID , I got the message “Directory object not found”.   However, when I tried connecting from the “Well known naming context”  combo-box by choosing RootDSE , I could not locate the attribute defaultNamingContext. However, there was another attribute present called dsServiceName which contains the value : CN=NTDS Setting,CN=computerName$instanceName,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={GUID} (with computerName, instanceName & GUID specific to my scenario) .   In my existing connections, one from “Distinguished Name or naming context” textbox  by giving dc=abcd,dc=com And the second by selecting Configuration from “Well known naming context”  combo-box , I find that an attribute named msDS-DefaultNamingContextBL is present instead of msDS-DefaultNamingContext. Is this the same as msDS-DefaultNamingContext ?   How should I set the defaultNamingContext even when I am not able to connect to the NTDS Setting container as mentioned in the article?   Thanks, Harpreet