Activities

• Connect to Active Directory
• Disconnect from from Active Directory 
• Add Computer to Group
• Add Domain User to Local Group
• Add Group to Group
• Add User to Group
• Change User Password
• Change User Password (non-encrypted)
• ClearADAttributeValue
• Computer Exists
• Create Computer
• Create Group
• Create User
• Create User With Password String
• Delete Entry
• Edit Account Expires
• Edit Computer Account Status
• Edit Entry
• Edit User Account Status
• Get Account Expires
• Get Entries by Filter
• Get Entry
• Get Entry Attributes
• Get Password Expiration Date
• Get User Account Status
• Get User Groups
• Get Users in Group
• Get Entry SID
• Group Exists
• Is Member
• Join Computer to Domain
• Move Entry
• Remove Computer from Group
• Remove Group from Group
• Remove User from Group
• User Exists

Image Added

Connect to Active Directory

...

The Connect to Active Directory activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• AD Path (combo box control) (type: string): the Active Directory connection string, without "LDAP:\\\\" part. Here can be inserted, for example, the name of the Domain Controller server: "dc1.com"
• Logon Provider (combo box control) (type: string): choose from the drop down list the logon provider. Flowster Studio provides the following options:
  • Default: Use the standard logon provider for the system. The default security provider is negotiate, unless you pass NULL for the domain name and the user name is not in UPN format. In this case the default provider is NTLM.
  • WinNT50: Use the negotiate logon provider. This value is not support for Windows NT 4 or earlier.
  • WinNT40: Use the NTLM logon provider
  • WinNT35: Use the Windows NT 3.5 logon provider
• Logon Type (combo box control) (type: string): choose from the drop down list the type of logon operation to perform.
  
  • Interactive: used for a logon at the console of a computer. An Interactive logon is logged when it is attempted to log on at a Windows computer’s local keyboard and screen
  • Network: occurs when there are accessed remote file shares or printers. Also, most logons to Internet Information Services (IIS) are classified as network logons, other than IIS logons that use the basic authentication protocol (those are logged as logon type Network Clear Text)
  • Batch: used for scheduled workflows. When the Windows Scheduler service starts a scheduled workflow, it first creates a new logon session for the workflow, so that it can run in the security context of the account that was specified when the workflow was created
  • Service: used for services and service accounts that log on to start a service. When a service starts, Windows first creates a logon session for the user account that is specified in the service configuration
  • Unlock: used whenever a Windows machine is unlocked
  • Network Clear Text: used when log on over a network and the password is sent in clear text. This happens, for example, when basic authentication is used to authenticate to an IIS server
  • New Credentials: used when running an application using the RunAs command and specify the /netonly switch. When you start a program with RunAs using /netonly, the program starts in a new logon session that has the same local identity (this is the identity of the currently logged on user), but uses different credentials (the ones specified in the runas command) for other network connections. Without /netonly, Windows runs the program on the local computer and on the network as the user specified in the runas command, and logs the logon event with type Interactive
• Password (password editor type) (type: string): the password for the provided username.
• Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the connection. (This parameter is used only when the user wants to send an encripted password from outside the workflow, for example Flowster Portal).
• Root (combo box control) (type: string): the root type: 
  • LDAP: when the scope of a search is the domain or an organizational unit
  • GC: when the scope of a search is the forest
• Secure Connection (combo box control) (type: string): this can be used as input when you need a secure connection. You can either choose from the drop down list if the connection should be secured or you can bind this parameter to a Variable/Global Variable or IN argument. 
• Username (text box editor type) (type: string): the username to query and perform Active Directory operations. The accepted format is domain\username

...

The Disconnect from Active Directory activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Connection (text box editor type) (type: object): the Active Directory Connection. The output parameter from Connect To Active Directory activity should be used as Input here.
  
  

...

The Add Computer to Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Computer (text box editor type) (type: string): the entry path of the computer, or bind this parameter with the output parameter of a Get Entry activity. If the Computer Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://ServerName.dc1.com/CN=TestingMachine,OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com"
• Group (text box editor type) (type: string): the entry path of the group, or bind this parameter with the output parameter of a Get Entry activity. If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://ServerName.dc1.com/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com"
  
  
  

...

The Add Domain User to Local Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Domain (text box editor type) (type: string): the domain from where the user will be added into the local group (e.g. "dc1").
• Group Name (text box editor type) (type: string): the name of the local group where the domain user will be added (e.g. "FlowsterLocalGroup").
• User Name (text box editor type) (type: string): the sAMAccountName of the domain user which will be added to the local group (e.g. "demouser"). This is the Active Directory attribute after which the activity will retrieve the user.
  
  

...

The Add Group to Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Group (text box editor type) (type: string): the entry path of the group where the other group will be added, or bind this parameter with the output parameter of a Get Entry activity. If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://servername.dc1.com/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com"

...

• use a Get Entry activity to extract the first Group entry (the group where the second group will be added):Image Removed

Image Added

• use another Get Entry activity to extract the second Group entry path (the group which will be added into the first group)
  Image Removed
  Image Added
  
  
• bind the obtained paths (stored in variables) to the Group and Group To Be Added fields from the Add Group To Group activity:
  Image Removed
  Image Added

Add User to Group

...

The Add User to Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Group (text box editor type) (type: string): the entry path of the group where the user will be added, or bind this parameter with the output parameter of a Get Entry activity. If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://servername.dc1.com/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com"

...

• use a Get Entry activity to extract the Group entry (the group where the user will be added):
  Image Removed
  Image Added
  
  
• use another Get Entry activity to extract the User entry path (the user which will be added into the group)
  Image Removed
  Image Added
  
  
• bind the obtained paths (stored in variables) to the Group and Group To Be Added fields from the Add Group To Group activity:
  Image Removed
  Image Added

Change User Password

...

The Change User Password activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Entry (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=TestingUser,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"
• Password (text box editor type) (type: string): the new password for the User.
• Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the User. (This parameter is used only when the user wants to send an encripted password from outside the workflow, for example Flowster Portal)

...

• use another Get Entry activity to extract the User entry path:
  Image Removed
  Image Added
  
  
• bind the obtained path (stored in a variable) to the User field from the Change User Password activity:
  Image Removed
  Image Added

Change User Password(non-encrypted)

...

The Change User Password (non-encrypted) activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Entry (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=TestingUser,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"
• Password Binding (text box editor type) (type: string): bind to a variable containing the non-encrypted password or input the string password. E.g. "Welcome2016". The variable can be defined in the Variables section and should be of type String.
  
  
  

...

• use another Get Entry activity to extract the User entry path:
  Image Removed
  Image Added
  
  
• bind the obtained path (stored in a variable) to the User field from the Change User Password (non-encrypted) activity:
  Image Removed
  Image Added

ClearADAttributeValue

...

The ClearADAttributeValue activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• ClearAttribute (text box editor type) (type: string): the attribute that will be cleared/removed.
• Entry (text box editor type) (type: string): the entry path of the Active Directory entry, or bind this parameter with the output parameter of a Get Entry activity. If the Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://servername.dc1.com/CN=DemoUser,OU=DemoOU,DC=dc1,DC=com"

Using Get Entry activities: get Entry activities can be used in order to extract the needed entry paths from Active Directory. The steps below are describing a scenario of how to use both Get Entry and ClearADAttributeValue activity:

• use a Get Entry activity to extract the Entry path:Image Removed

Image Added

• bind the obtained path (stored in variable) to the Entry field from ClearADAttributeValue activity:Image Removed

Image Added

Computer Exists

This activity checks in the Active Directory if specified computer has an entry in 'Computer' class.

...

The Computer Exists activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Check Entry By (text box editor type)  (type: string): the activity will search into Active Directory for a computer type object with the specified value of this attribute. By default it is set to sAMAccountName, which is an AD attribute with unique values
• Value (text box editor type)  (type: string): the value for selected attribute in Check Entry By parameter. In the example above, the value for sAMAccountName (e.g. TestingMachine)

...

The Create Computer activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Attributes (text box editor type) (type: string): enter computer specific Attributes for the new created computer. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD).
• CN String (text box editor type) (type: string): the CN String value that will be associated with the Canonical Name of the object. For Example: 'CN=DemoComputer1' will create a computer with the Canonical Name: dc1.com/__DEV-Testing/Computers/DemoComputer1.
• CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field.
  
• Parent Entry (text box editor type) (type: string): the parent entry for the new created computer. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com"
• sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new computer.

...

The Create Group activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Attributes (text box editor type) (type: string): enter group specific Attributes for the new created group. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD). For example, it can be inserted the displayName attribute. In the Collection editor window, when adding a new member, at Name insert the attribute's name (e.g. displayName) and at Value insert the value that the attribute should take.
• CN String (text box editor type) (type: string): the CN String value of the place where the group will be created. For Example: 'CN=TEST'. This value will be associated with the CN attribute.
• CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field. The example presented in the screenshot can be translated as "displayName,TestingGroup".
  
• Group Type (combo box control) (type: string): choose the type of the group you want to create. Flowster Studio provides the following options:
  • Local Security Group
  • Global Security Group
  • Builtin Group
  • Universal Security Group
  • Global Distribution Group
  • Local Distribution group
  • Universal Distribution group
• Parent Entry (text box editor type) (type: string): the parent entry for the new created group. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".
• sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new group.

...

The Create User activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Attributes (text box editor type) (type: string): enter user specific Attributes for the new created user. Here can be inserted attributes that would not be created by default with the activity (optional attributes in AD). For example, it can be inserted the displayName attribute. In the Collection editor window, when adding a new member, at Name insert the attribute's name (e.g. displayName) and at Value insert the value that the attribute should take:
• CN String (text box editor type) (type: string): the CN String value of the place where the user will be created. For Example: 'CN=TEST'. This value will be associated with the CN attribute.
• CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "Attribute1Name,Attribute1Value;Attribute2Name,Attribute2Value". This field can be used in order to provide all the desired attributes and their values on a single field. The example presented in the screenshot can be translated as "displayName,TestingUser;mail,TstUser@flowster.de;company,Flowster Solutions".
• Parent Entry (text box editor type) (type: string): the parent entry for the new created user. The parent entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
• Password (text box editor type) (type: string): the password for the User.
• Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for the User. (This parameter is used only when the user wants to send an encripted password from outside the workflow, for example Flowster Portal)
• sAMAccountName (text box editor type) (type: string): the sAMAccountName for the new user.

...

...

The Delete Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Entry (combo box control) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser_1,OU=Users,DC=dc1,DC=com"

...

The Edit Account Expires activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Date (text box editor type) (type: string): the value for the date and time when the account should expire. The value must be inserted as a string, following the format given inside the Date Format parameter (e.g. 07/01/2017 10:10:10, which means that the account will expire on January 7, 2017 at 10:00:00)
• Date Format (text box editor type) (type: string): the format of the date and time when the account will expire. If no value is provided, the the activity will take the System's defaults.
• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• use another Get Entry activity to extract the User entry path:
  Image Removed
  Image Added
  
  
• bind the obtained path (stored in a variable) to the User field from the Edit Account Status activity:
  Image Removed
  Image Added

Edit Computer Account Status

...

The Edit Computer Account Status activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Action (combo box control) (type: string): choose to Enable/Disable the specified computer account.
• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for a computer account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoComputer1,OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com".

...

The Edit Entry activity parameters can be provided by manual inserted values or via IN arguments or variables:

Image RemovedImage Added

Parameters:

• Attribute (text box editor type) (type: string): the attribute for which the value(s) will be edited. Here should be inserted the name exactly as seen in Active Directory (e.g. displayName)
• Attributes (text box editor type) (type: string): the attributes as a collection for the AD entry that you want to edit. This parameter can be used in case of multiple attributes that will be edited. Attributes will be added as a list, with their Names and new Values
• CSV Attributes (text box editor type) (type: string): overrides the 'Attributes' parameter. The values must be entered with the format: "AttributeName1,Attribute1Value;Attribute2Name,Attribute2Value". This parameter can be used instead of the Attributes one if there is desired to write all attributes and their values as a single string
  
• Date Format (text box editor type) (type: string): if 'Value Type' is 'DateTime', enter the date format string. For example: dd.MM.yyyy; if no value is entered, the system defaults are used.
• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
• Value Type (combo box control) (type: string): choose Data type for the edited value. In our example String will be needed
• Value(s) (text box editor type) (type: IEnumerable<string>): enter new value(s) for the attribute (the one provided in the Attribute field), separated by ','. Being of type IEnumerable<of string>, the value(s) should be written between {}
  
  • Examples of values:
    • simple string: {"Demo Test"}
    • multiple values: {"Demo Test","Demo Name","Demo Value"}
    • simple string with comma in it: {"Demo, Test"}
    • multiple values with comma inside of the string: {"Demo, Test","Demo, Name"","Demo, Value"}

Edit User Account Status

...

• Action (combo box control) (type: string): choose to Enable/Disable or Lock/Unlock the specified user account.
• Attempts (text box editor type) (type: string): the number of allowed bad password attempts.
• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Entry (text box editor type) (type: string):  the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"
• Selected Attribute (text box editor type) (type: string): specify an attribute for which you want a separate output. This parameter is used when it is desired for the activity to return only the value(s) for a single attribute (e.g. sAMAccountName)

...

• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry (for GetEntry binding usage, see the Add Computer To Group activity) activity or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com"

...

• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=Demouser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Entry (text box editor type) (type: string): the entry for the account, in this case the entry for an user account. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Attributes (text box editor type) (type: string): the attributes to retrieve for found users, in addition to the 'Path' attribute, which is retrieved by default. The attributes must be separated by ','. For example: name,distinguishedName,sAMAccount.
• Group Name (text box editor type) (type: string): the group name. This value can be used when no path is given for the group
• Group Path (text box editor type) (type: string): the entry for the group. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group13669534395 activity) or written by hand. The accepted format should be written as in the given example: "LDAP://servername.dc1.com/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".
  
  
  

...

• Entry Path (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
• Group Path (text box editor type) (type: string): the entry for the group. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoGroup1,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Entry (text box editor type) (type: string): the entry for the user. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group13669534395 activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=Demouser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".
• Entry New Location (text box editor type) (type: string): the entry for the new location (in this example a group is given). The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/OU=DemoUsers,DC=dc1,DC=com".

...

• Computer (text box editor type) (type: string): the entry for the computer. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoComputer1,OU=Computers,OU=__DEV-Testing,DC=dc1,DC=com".
• Group (text box editor type) (type: string): the entry for the group where the computer is a member of. The entry can be linked to a variable outputed by the GetEntry activity (for GetEntry binding usage, see the Add Computer To Group activity) or written by hand. The accepted format should be written as in the given example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Group (text box editor type) (type: string): the entry path of the group where the other group is a member of, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".

• Group To Be Removed (text box editor type) (type: string): the entry path of the group that will be removed from the group, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroup1,OU=DemoGroups,OU=__DEV-Testing,DC=dc1,DC=com".

...

• Group (text box editor type) (type: string): the entry path of the group where the user is a member of, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoGroups,OU=Groups,OU=__DEV-Testing,DC=dc1,DC=com".

• User (text box editor type) (type: string): the entry path of the user that will be removed from the group, or bind this parameter with the output parameter of a Get Entry activity (for GetEntry binding usage, see the Add Computer To Group activity). If the Group Entry Path will be manually inserted, the accepted format should be written like in the following example: "LDAP://srvname.dc1.com/CN=DemoUser1,OU=Users,OU=__DEV-Testing,DC=dc1,DC=com".

...