...
The Connect to Active Directory activity parameters can be provided by manual inserted values or via IN arguments or variables:
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, in full address format: DEMOSERVER.demo.intern: "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 Add Computer to Group activity parameters can be provided by manual inserted values or via IN arguments or variables:
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://VSRPDC201ServerName.FMRPdc1.interncom/CN=TestingMachine,OU=Computers,OU=__DEV-Testing,DC=FMRPdc1,DC=interncom"
- 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://VSRPDC201ServerName.FMRPdc1.interncom/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=FMRPdc1,DC=interncom"
Execution: the activity will search if the provided entry paths are valid and if yes, it will add the indicated computer to the indicated group:
.
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 Add Computer to Group activity types:
...
The Add Domain User to Local Group activity parameters can be provided by manual inserted values or via IN arguments or variables:
Parameters:
- Domain (text box editor type) (type: string): the domain from where the user will be added into the local group (e.g. "fmrpdc1").
- 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:
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://VSRPDC201servername.FMRPdc1.interncom/CN=TestingGroup,OU=Groups,OU=__DEV-Testing,DC=FMRPdc1,DC=interncom"
- Group To Be Added (text box editor type) (type: string): the entry path of the group that will be added into another 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://VSRPDC201servername.FMRPdc1.interncom/CN=DemoGroup,OU=Groups,OU=__DEV-Testing,DC=FMRPdc1,DC=interncom"
Execution: the activity will search if the provided entry paths are valid and if yes, it will add the indicated group to the other group:
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 Add Group to Group activity types:
...