Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 27 Next »

Activities

Check for Updates

This activity checks for OS Updates on a specified Windows workstation.

Prerequisites (for the remote machine)

1. Windows Firewall


 

                       

2.  Windows Group Policy Object Editor

  • Open Group Policy Object Editor (gpedit.msc)
  • Open Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile & Standard Profile.
  • Here enable the following exceptions: "Allow inbound remote administration exception"


3.  Windows Updates

 Windows Updates must be available for checking and installation on the affected virtual machines.

 


4. Enable PowerShell Remoting


On the virtual machine you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):

Enable-PSRemoting -Force

 

Run the Enable-PSRemoting -Force command on the computer you want to connect from, as well. (Remember to launch PowerShell as Administrator before running this command.)

On both computers, configure the TrustedHosts setting so the computers will trust each other. For example, if you’re doing this on a trusted home network, you can use this command to allow any computer to connect:

Set-Item wsman:\localhost\client\trustedhosts *

On both computers, restart the WinRM service so your new settings will take effect:

Restart-Service WinRM

 


5. User Rights


The user that will be entered as input for Check For Updates and Install Missing Updates activities must have rights to read/write files and scheduled tasks on the affected virtual machine.



Activity Parameters

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

Parameters:

  • Computer name (text box editor type) (type: string): the IP or hostname of the machine you want to run the check against. If none is provided, localhost will be used.
  • Update Type (combobox control type) (type: string): filter the update types (All, Important, Optional). The default value is "All".
  • Username (text box editor type) (type: string): the username that will be used to connect to the target machine.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output status (type: boolean): outputs True if any updates are found, and False if none.
  • Output Count (type: int): outputs the number of updates found.
  • Output Updates (type: List<string>): outputs a list of the available updates (names).





Cmd

This activity runs a Windows CMD.exe command.

Activity Parameters

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

Parameters:

  • Command (text box editor type) (type: string): the command that you want to be executed. For example: mkdir "C:\\FlowsterSolutions" (this command creates a folder with the specified path).
    For easier editing, the user can use the internal editor via the ellipsis button situated on the right hand side of the edit field, or an external editor of his/her choice (customizable in the Designer Settings) via the button to the left of the edit field ().
  • Command Block (text box editor type) (type: string): the command that needs to be executed. The main difference between the Command field and Command Block is the possibility to use variables:
  • Timeout (text box editor type) (type: int32): the number of seconds to wait for the Command to execute.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: string): outputs the Command ExitCode as a String.
  • Output Error (type: string): outputs the Command Output Error as a String.
  • Output (type: string): outputs the Command Output Result as a String.



Delete Scheduled Task

This activity deletes a scheduled task on Windows Task Scheduler.

Activity Parameters

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

Parameters:

  • Machine Name (text box editor type) (type: string): the remote computer name. Not needed for local connections.
     
  • Task Name (text box editor type) (type: string): the name of the scheduled task you want to delete.
  • User (text box editor type) (type: string): the username used to connect to remote machine. Not needed for local connections.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Exists (type: boolean): outputs if the task exists or not.
  • Output Status(type: boolean): outputs the status of the operation.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Delete Scheduled Task activity:




Edit Windows Service

This activity updates the logon credentials and the startup type of a Windows service on a specified machine.

Activity Parameters

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

Parameters:

  • Computer name (text box editor type) (type: string): the IP or hostname of the machine you want to run the check against. If none is provided, localhost will be used.
  • Service name (text box editor type) (type: string): the name of the service to be updated.
  • Startup Type (text box editor type with combobox filter) (type: string): Enter or select the type of startup (Automatic, Manual, Disabled) the service should have after the activity runs.
  • Username (text box editor type) (type: string): the username that will be used to connect to the target machine and that will be set as logon user for the service.
  • Remote Full Username (text box editor type) (type: string): the domain and username that has rights on the remote machine. Not required on local machine. E.g. "mydomain\demo_user"
  • Remote Password (password box editor type) (type: string): the username password on the remote machine. Not required on local machine.
  • Remote Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).

The Read Only Output variable are the possible output values that the activity will provide:

  • Output status (type: boolean): outputs True if the operation succeeded, and False otherwise.



End Process

This activity terminates a process locally or remote.

Activity Parameters

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

Parameters:

  • Machine (text box editor type) (type: string): the IP or name of the machine where the process is running.
  • Password (password box editor type) (type: string): the username password if the process should be executed on a remote machine. Not required when process should be executed locally.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).
  • Process Name (text box editor type) (type: string): the process name that will be terminated.
  • Process PID (text box editor type) (type: string): the process PID that will be terminated.
  • Username (text box editor type) (type: string): the username if the process should be executed on a remote machine. Not required when process should be executed locally.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Status (type: boolean): outputs the result status. If the operation succeeded then TRUE, otherwise FALSE.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the End Process activity:



Get Current User Info

This actvity returns the Username (sAMAccountname) and Domain of the currently logged in user.

Activity Parameters

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

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Domain (type: string): outputs the current user domain.
  • Output Username (type: string): outputs the current Username.



Get MAC Address

This activity checks for OS Updates on a specified Windows workstation.

Activity Parameters

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

Parameters:

  • Computer name (text box editor type) (type: string): the IP or hostname of the machine you want to run the check against. If none is provided, localhost will be used.
  • Username (text box editor type) (type: string): the username that will be used to connect to the target machine.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: List<Tuple<string,string>>): outputs a list of [adapter name, MAC address] pairs.



Install Missing Updates

This activity installs required OS Updates on a specified Windows workstation.


Prerequisites (for the remote machine)

1. Windows Firewall


 

                       

2.  Windows Group Policy Object Editor

  • Open Group Policy Object Editor (gpedit.msc)
  • Open Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall -> Domain Profile & Standard Profile.
  • Here enable the following exceptions: "Allow inbound remote administration exception"


3.  Windows Updates

 Windows Updates must be available for checking and installation on the affected virtual machines.

 


4. Enable PowerShell Remoting


On the virtual machine you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):

Enable-PSRemoting -Force

 

Run the Enable-PSRemoting -Force command on the computer you want to connect from, as well. (Remember to launch PowerShell as Administrator before running this command.)

On both computers, configure the TrustedHosts setting so the computers will trust each other. For example, if you’re doing this on a trusted home network, you can use this command to allow any computer to connect:

Set-Item wsman:\localhost\client\trustedhosts *

On both computers, restart the WinRM service so your new settings will take effect:

Restart-Service WinRM

 


5. User Rights


The user that will be entered as input for Check For Updates and Install Missing Updates activities must have rights to read/write files and scheduled tasks on the affected virtual machine.

Activity Parameters

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

Parameters:

  • Computer name (text box editor type) (type: string): the IP or hostname of the machine you want to run the check against. If none is provided, localhost will be used.
  • Update Type (combobox control type) (type: string): filter the update types (All, Important, Optional). The default value is "All".
  • Username (text box editor type) (type: string): the username that will be used to connect to the target machine.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output status (type: boolean): outputs True if any updates are found, and False if none.
  • Output restart needed (type: boolean): outputs True if a restart is required after the update(s) install, and False otherwise.



List Windows Services

This activity returns a list of the windows services and their properties. Optionally, it can output the properties of a specific service.

Activity Parameters

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

Parameters:

  • Computer name (text box editor type) (type: string): the IP or hostname of the machine you want to run the check against. If none is provided, localhost will be used.
  • Username (text box editor type) (type: string): the username that will be used to connect to the target machine.
  • (optional) Service Name (combobox control type) (type: string): the name of the Windows Service (e.g. FlowsterEngineService). Only enter a value in this field if you want to output the properties of this specific service.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: Collection<Dictionary<String,String>>): outputs a collection of Dictionaries containing the workstation's Windows services. Output service properties: Name, StartupType and State.


Run C# expression

This activity runs a C# code and returns the compiled value.

Activity Parameters

The Run C# Expression activity parameters can be provided by manual inserted values or via IN arguments or variables:

Parameters:

  • Expression (text box editor type) (type: string): the expression code that will be compiled and executed.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: string): outputs result of the executed code.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Run C# Expression activity:



 

Run Program

This activity runs a program locally or remotely.

Activity Parameters

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

Parameters:

  • Machine (text box editor type) (type: string): the IP or name of the machine where to execute the process.
  • Password (password box editor type) (type: string): the username password if the process should be executed on a remote machine. Not required when process should be executed locally.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).
  • Process (text box editor type) (type: string): the process path or name of the process(executable). Only process name if can be found directly in System32 folder.
  • Username (text box editor type) (type: string): the username if the process should be executed on a remote machine. Not required when process should be executed locally.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Run Program activity:

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: collection<string>): outputs a collection with WMI return value and PID. The return value is the Exit Code, displayed as an Integer (e.g. 0 or 1), as it can be seen below:



Schedule Daily Task

This activity creates a new daily scheduled task on Windows Task Scheduler. For example if all parameters are filled this will create a Daily trigger to run every X minutes for a duration of Y hours.

Activity Parameters

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

Parameters:

  • Duration (text box editor type) (type: string): enter a timespan format: 'HH,mm,ss'.
  • Machine Name (text box editor type) (type: string): the remote computer name. Not needed for local connections.   
  • Minutes (text box editor type) (type: int32): enter number of minutes.
  • Program Path (file browser editor type) (type: string): enter the path for the program to be executed. 
  • Start Date (calendar editor type) (type: string): enter the start date in the following format: 'dd/MM/yyyy HH:mm:ss'.
  • Start Time (text box editor type) (type: string): enter the start time in a timespan format: 'HH,mm,ss'.
  • Task Name (text box editor type) (type: string): the name of the scheduled task you want to schedule.
  • User (text box editor type) (type: string): the username used to connect to remote machine. Not needed for local connections.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Error Message (type: string): outputs the error message if any.
  • Output Status(type: boolean): outputs the status of the operation.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Schedule Daily Task activity:


Schedule Hourly Task

This activity creates a new hourly scheduled task on Windows Task Scheduler. For example if all parameters are filled this will create a Hourly trigger to run.

Activity Parameters

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

Parameters:

  • Machine Name (text box editor type) (type: string): the remote computer name. Not needed for local connections.   
     
  • Program Path (file browser editor type) (type: string): enter the path for the program to be executed. 
     
  • Task Name (text box editor type) (type: string): the name of the scheduled task you want to schedule.
  • User (text box editor type) (type: string): the username used to connect to remote machine. Not needed for local connections.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Error Message (type: string): outputs the error message if any.
  • Output Status(type: boolean): outputs the status of the operation.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Schedule HourlyTask activity:




Schedule Weekly Task

This activity creates a new weekly scheduled task on Windows Task Scheduler.

Activity Parameters

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

Parameters:

  • Machine Name (text box editor type) (type: string): the remote computer name. Not needed for local connections.   
  • Minutes (text box editor type) (type: int32): enter number of minutes.
  • Program Path (file browser editor type) (type: string): enter the path for the program to be executed. 
     
  • Run Every X Week (text box editor type) (type: int32): enter 1 to run every week.
  • Task Name (text box editor type) (type: string): the name of the scheduled task you want to schedule.
  • User (text box editor type) (type: string): the username used to connect to remote machine. Not needed for local connections.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Error Message (type: string): outputs the error message if any.
  • Output Status(type: boolean): outputs the status of the operation.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Schedule Weekly Task activity:

 


Schedule Monthly Task

This activity creates a new monthly scheduled task on Windows Task Scheduler. For example, if all parameters are filled this will create a Monthly trigger to run on X day of month for every Y minutes.

Activity Parameters

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

Parameters:

  • Machine Name (text box editor type) (type: string): the remote computer name. Not needed for local connections.   
  • Minutes (text box editor type) (type: int32): enter number of minutes.
  • Program Path (file browser editor type) (type: string): enter the path for the program to be executed.   
  • Run Months Apart (text box editor type) (type: int32): enter 12 to run only in December.
  • Run On Day (text box editor type) (type: int32): enter 1 to run on the first day of the month.
  • Task Name (text box editor type) (type: string): the name of the scheduled task you want to schedule.
  • User (text box editor type) (type: string): the username used to connect to remote machine. Not needed for local connections.

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Error Message (type: string): outputs the error message if any.
  • Output Status(type: boolean): outputs the status of the operation.


As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Schedule MonthlyTask activity:


Server Boot Operations

This activity Server Boot Operations locally or remote.

Activity Parameters

The Server Boot Operations activity parameters can be provided by manual inserted values or via IN arguments or variables.

Parameters:

  • Machine (text box editor type) (type: string): the IP or name of the machine you want to do the operation on.
  • Password (password box editor type) (type: string): the username password on the remote machine. Not required on local machine.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).
  • Operation (text box editor type) (type: string): the operation you want to be executed on the machine.
  • Username (text box editor type) (type: string): the username that has rights on the remote machine. Not required on local machine.

The Read Only Output variable are the possible output values that the activity will provide:

  • Entries Collection (type: string): outputs the Windows code for the operation result.


 

Windows Service Tasks

This activity starts stops or restarts a windows service locally or remote.

Activity Parameters

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

Parameters:

  • Computer Name (text box editor type) (type: string): the computer name or IP. For example '10.10.10.10'.
  • Operation (combo box control) (type: string): the operation you want to be executed on the windows service.
  • Service Name (text box editor type) (type: string): the service name. For example : 'Flowster Studio Email trigger'.
  • Remote Full Username (text box editor type) (type: string): the domain and username that has rights on the remote machine. Not required on local machine. E.g. "mydomain\demo_user"
  • Remote Password (password box editor type) (type: string): the username password on the remote machine. Not required on local machine.
  • Remote Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).

The Read Only Output variable are the possible output values that the activity will provide:

  • Output Status (type: boolean): outputs the result status. If the operation succeeded then TRUE, otherwise FALSE.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the Windows Service Tasks activity:




 

WMI Query

This activity executes a WMI query locally or remote.

Activity Parameters

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

Parameters:

  • Machine (text box editor type) (type: string): the IP or name of the machine where the WMI query should be executed.
  • Password (password box editor type) (type: string): the username password on the remote machine. Not required on local machine.
  • Password Binding (text box editor type) (type: string): bind to a variable containing the encrypted password for connection. (This parameter is used only when the user wants to send an encripted password from outside the task, for example Flowster Studio Portal).
  • Query (text box editor type) (type: string): the query which should be executed.
  • Username (text box editor type) (type: string): the username if the process should be executed on a remote machine. Not required when process should be executed locally.

As mentioned above, the values for all the required parameters can be provided by IN arguments or variables. Below is an example of predefined arguments, ready to be used by the WMI Query activity:

The Read Only Output variable are the possible output values that the activity will provide:

  • Output (type: collection<dictionary<string>>): outputs a collection with WMI return object properties converted to string.


  • No labels