Notes on IT (mainly Microsoft)

Archive for the ‘powershell’ Category

General Availability of Windows Azure Infrastructure as a Service (IaaS)

leave a comment »

Read this post.

Watch this video at:

General Availability of Windows Azure Infrastructure as a Service (IaaS)

and the follow links on that page.

Nordic Infrastructure Conference 2013 – session videos available

leave a comment »

Videos of talks covering topics in:

Windows server
Virtualization & Cloud
System Management
Unified Communication
Windows Client
Partner talks

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.

How to find out which naming contexts and application partitions are hosted by an AD LDS instance

leave a comment »

Suppose we have an AD LDS instance running on localhost port 389. What naming contexts does it hold?

The naming contexts can be enumerated by retrieving namingContexts attribute of the RootDSE of the AD LDS instance:



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:
changetype: add
namingContexts: CN=Configuration,CN={0FF76061-6F79-4DF9-AA3F-58239ED6EEA2}
namingContexts: O=msft

1 entries exported

The command has completed successfully

To see the namingContexts in a GUI tool run:

ldp.exe localhost:389

and look for the namingContexts attribute in the right hand pane:

Written by adamsync

June 21, 2012 at 22:57

How to determine AD Schema Version from the command line using PowerShell, ldifde or repadmin

leave a comment »

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.

Written by adamsync

May 27, 2012 at 18:09