How do I determine the distinguished name or naming context on an already built adlds instance?

-

how determine distinguished name or naming context on built adlds instance?  i'm trying find connection string instance.  i'm not seeing in server manager stands out.  don't know instance name because didn't build instance.

thanks,

hi,

you can use ldp.exe administration tool. use ldp.exe administer active directory lightweight directory services (ad lds) instance, must connect , bind instance , display hierarchy (tree) of distinguished name of instance. can browse object in tree , right-click object administer it.

read this, practice using ad lds administration tools
http://technet.microsoft.com/en-us/library/cc732675(v=ws.10).aspx#bkmk_3

also check following, windows 2008 r2: managing ad lds using ad powershell module
http://blogs.technet.com/b/askds/archive/2009/09/14/windows-2008-r2-managing-ad-lds-using-the-ad-powershell-module.aspx

best regards,

abhijit waikar.
mcsa 2003 | mcsa:messaging | mcts | mcitp:server administrator | microsoft community contributor | my blog

disclaimer: posting provided "as is" no warranties or guarantees , , confers no rights.




Windows Server  >  Directory Services



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more