Description:

This step creates a new Active Directory computer account.

The Create Active Directory Computer workflow step connects to Microsoft Active Directory via a configured LDAP connection and creates a new computer object using the specified computer name.

The step creates the computer account in the configured Active Directory domain, allowing the computer to be managed through Active Directory and to participate in domain-based authentication, Group Policy, and centralized administration.

This step provides an efficient way to automate computer account provisioning as part of device deployment, infrastructure automation, desktop provisioning, or identity lifecycle workflows.

The step supports:

• Active Directory computer account creation
• Automated computer provisioning
• Configurable LDAP connections
• Dynamic computer name input using workflow variables
• Integration with Microsoft Active Directory

This step can be used for:

• Device provisioning
• Automated workstation deployment
• Server deployment
• Infrastructure automation
• Domain onboarding
• IT asset management
• Business process automation

Usage:

The Create Active Directory Computer step is typically placed during device provisioning, server deployment, or infrastructure onboarding workflows.

The workflow creates a new Active Directory computer account using the configured LDAP connection.

A typical workflow might look like this:

Once the computer account has been created, later workflow steps can:

• Join the device to the domain
• Apply Group Policy
• Register the computer in the asset management systems
• Notify administrators
• Synchronize inventory systems
• Continue infrastructure provisioning workflows

You need to set up an LDAP connection before using this step.

Go to:

Integration → Connections → Generic Connections

On the Manage Generic Connections page, click:

Actions → Create

Configure an Active Directory connection before using this workflow step.

A sample connection is provided here for reference. 

Example:

Let’s build and execute the “clsCreateADComputerDef” example:

• Create a new process definition named “clsCreateADComputerDef” and open it in designer mode. 
• Drag a “clsCreateADComputer” step to the canvas.
• Connect the dots between the “Start” and “clsCreateADComputer” steps.
• Click the "clsCreateADComputer" step to configure its "Required" properties. Provide a name for the step. Select the LDAP connection from the drop-down list. Enter the “Computer Name”. Click the Save button to confirm. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Create Computer step, FlowWright connects to the configured Active Directory server using the selected LDAP connection and attempts to create the specified computer account. If the operation completes successfully, the workflow follows the Created return path. If the computer account already exists, the computer name is invalid, or the LDAP connection cannot be established, the workflow follows the NotCreated return path.

• Click the process step to view its properties. The step should create the specified Active Directory computer account and return Created upon successful completion. Use the appropriate Active Directory management tools or, if available, a Read Computer workflow step to verify that the computer account has been created successfully.

Tips:

• Verify that the LDAP connection has been configured before using this step.
• Ensure that the LDAP account has permission to create Active Directory computer objects.
• Verify that the specified computer name is unique within the Active Directory domain.
• Use workflow variables to dynamically provide the computer name.
• Follow your organization's computer naming conventions to ensure consistency.
• Use the Created and NotCreated return paths to implement appropriate success and error handling.
• Combine this step with the Create Organizational Unit, Move Computer, Enable Computer, or inventory management workflows to automate the complete device provisioning process.

Notes:

• A valid LDAP connection must exist before this step can execute.
• The configured LDAP account must have sufficient permissions to create Active Directory computer objects.
• The specified computer name must comply with Active Directory naming rules.
• If a computer account with the same name already exists, the creation operation may fail.
• Creating a computer account does not automatically join a physical or virtual machine to the domain.
• Network connectivity or authentication issues may prevent the computer account from being created.
• The workflow should include appropriate error handling for the NotCreated return path.
• The workflow result depends on the current state of Active Directory and the permissions granted to the configured LDAP connection.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Note: Verify and complete any missing configuration after importing the sample, including:

• LDAP connection
• Computer name mapping
• Workflow variable mappings
• Active Directory permissions
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.