Archive for the ‘powershell’ Category
Read this post.
Watch this video at:
and the follow links on that page.
Videos of talks covering topics in:
Virtualization & Cloud
given at the Nordic Infrastructure Conference held in January are now available. There’s broad coverage by many well-known speakers, see the Agenda for links to the videos.
Written by adamsync
February 13, 2013 at 22:59
Posted in Active Directory, AD DS, Cloud, Data Center, Domain Controller, Dynamic Access Control, Enterprise Architecture, Exchange, Exchange 2013, Hyper-V, Identity Management, IdMAAS, Infrastructure, learning resources, Microsoft, Office 365, powershell, single sign-on, SSO, Storage, Technology Architecture, Windows Azure, Windows Azure Active Directory, Windows Server 2012, Windows2012
Suppose we have an AD LDS instance running on localhost port 389. What naming contexts does it hold?
PS C:\Users\Administrator> (Get-ADRootDSE -Server localhost:389).namingContexts
C:\Windows\system32>ldifde -f con -s localhost:389 -d “” -p base -l namingContexts
Connecting to “localhost:389”
Logging in as current user using SSPI
Exporting directory to file con
Searching for entries…
Writing out entries.dn:
1 entries exported
The command has completed successfully
To see the namingContexts in a GUI tool run:
and look for the namingContexts attribute in the right hand pane:
The version of the Schema in use by AD DS and AD LDS (ADAM) is to be found in the objectVersion attribute of the Schema Naming context and as such can be determined by navigating to the Schema Naming context using say ADSIedit or ldp.exe. From the command line we can use the Active Directory powershell module or ldifde or repadmin:
The commands above were run on a DC hence localhost:389, substitute the DC name as required. Repadmin and ldifde were run in the PowerShell window but could just be run from the command line on any device with AD DS tools installed.