Return
-
Title
"Method invocation failed because [System.DirectoryServices.DirectoryEntry] does not contain a method named 'Control'." when using SDK sample -
Description
The SDK for Active Roles includes the sample script shown below. When attempting to run this sample, PowerShell throws an exception advising Method invocation failed because [System.DirectoryServices.DirectoryEntry] does not contain a method named 'Control'.
[PowerShell]
$EDS_CONTROL_LDAP_SERVER = 13# Create User object in the specified OU$cont = [ADSI]"EDMS://OU=Sales,DC=Mycompany,DC=com"$usr = $cont.Create("user", "CN=John MCDuglas")# Set the User properties$usr.Put("samAccountName", "JMCDuglas")$usr.Put("edsaAccountIsDisabled", $false)# Set the InControl value$usr.Control($EDS_CONTROL_LDAP_SERVER) = "FirstDC.Mycompany.com"# Commit changes$usr.SetInfo() -
Cause
This issue has been identified as a documentation defect and is being tracked as Defect ID 720950. -
Resolution
WORKAROUND
The documentation is ambiguous and the PowerShell example is a bit misleading. The ‘Control’ property is a native Active Roles COM type. VBScript works differently and this is why it is possible to access the ‘Control’ property directly. With PowerShell it is necessary to use a .Net Wrapper to achieve the same result.The correct usage in PowerShell should be either using Invoke or InvokeGet which should provide a managed wrapper to access public IEDM interfaces. The updated usage is as below:$usr.InvokeSet('Control', $EDS_CONTROL_LDAP_SERVER, $true, "FirstDC.Mycompany.com")Alternatively, it is also possible to use the Active Roles Management Shell PowerShell cmdlets with the -Control parameter to send control codes to the service.STATUS
Waiting for fix in a future release of Active Roles.
-
Change Request
TF00720950