Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Registering workstation clients#10646

Open
katarzyna-koltun-mx wants to merge 3 commits intodevelopmentmendix/docs:developmentfrom
kk-wks-register-multiplemendix/docs:kk-wks-register-multipleCopy head branch name to clipboard
Open

Registering workstation clients#10646
katarzyna-koltun-mx wants to merge 3 commits intodevelopmentmendix/docs:developmentfrom
kk-wks-register-multiplemendix/docs:kk-wks-register-multipleCopy head branch name to clipboard

Conversation

@katarzyna-koltun-mx
Copy link
Collaborator

No description provided.

@katarzyna-koltun-mx katarzyna-koltun-mx self-assigned this Jan 23, 2026
@katarzyna-koltun-mx
Copy link
Collaborator Author

@MXLino @mendix-nleimer Can you take a look at the proposed document and let me know if you have any corrections?

@katarzyna-koltun-mx
Copy link
Collaborator Author

Watch the sprint demo from Feb 5 - UI changes.

Copy link
Contributor

@MXLino MXLino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to adjust a few things, as the described steps do not correspond to the latest version.

weight: 30
---

## Introduction
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add here a little bit more context:

The ultimate goal of the Mendix Workstation Client is to establish a secure and reliable connection between the Mendix Application Client and the specific hardware, peripherals, or local data sources attached to that same workstation. This vital connection is facilitated via the Workstation Connector and the Workstation Client.

To enable this crucial functionality, the registration process is a critical first step: it onboards your local Workstation Client installation into your Mendix Workstation Management environment. This onboarding allows for centralized management, configuration deployment, and monitoring of your clients, ensuring they are properly set up to bridge your Mendix applications with the physical world.


1. Navigate to the **Workspaces** page in [Workstation Management](https://workstation.home.mendix.com/).
2. Click **Create Workspace**, or select an existing workspace from the overview.
3. Click **Create Station**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To remain consistent, I would also add here: ...,or select an existing station from the list for which no computer is yet registered.

3. Click **Create Station**.
4. Enter a name for the station and optionally select or create a group to categorize it, such as *Assembly*.
5. Add devices in the **Devices** section.
6. Click **Register Computer** to register your computer.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add some orientation help? For example: Click “Register Computer,” located at the top right of the banner, to start registering a computer.

1. Navigate to the **Workspaces** page in [Workstation Management](https://workstation.home.mendix.com/).
2. Click **Create Workspace**, or select an existing workspace from the overview.
3. Click **Create Station**.
4. Enter a name for the station and optionally select or create a group to categorize it, such as *Assembly*.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think point 4 and 5 we can skip here. specifically number 5 is not needed to register a computer,

4. Enter a name for the station and optionally select or create a group to categorize it, such as *Assembly*.
5. Add devices in the **Devices** section.
6. Click **Register Computer** to register your computer.
7. Click **Download** to navigate to the Workstation Client listing in the Marketplace, download the Client installer for Windows, install it, and launch it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Click Download to navigate to the Workstation Client listing in the Marketplace. Download and install the Client installer for Windows, then launch the application.
We should also add here the links to the different Versions of the Client, or if we have the links already somewhere else at least mention the available options.

For Windows: https://marketplace.mendix.com/link/component/247448
For Windows (portable version): https://marketplace.mendix.com/link/component/247456
For Linux ARM64: https://marketplace.mendix.com/link/component/247459
For maxOS: https://marketplace.mendix.com/link/component/253905

The **Create Bulk Registration Token** dialog opens. You can use it to activate a time-limited token which can then be entered into the registration field of multiple Workstation Clients.

4. Specify the timeframe during which the token is valid.
5. Copy the token to a clipboard and save it in a secure location. For security reasons, the token is only displayed once.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part is outdated. We have revised it, and as long as the token is active, it can be viewed and copied by the appropriate roles.

4. Specify the timeframe during which the token is valid.
5. Copy the token to a clipboard and save it in a secure location. For security reasons, the token is only displayed once.
6. Click **Activate Token**. The **Stations** page displays the timeframe during which the bulk registration is scheduled.
7. Use an automated script to distribute the token to client computers during the allowed timeframe. For example, on Windows machines, you can use the following script: `Start-Process -FilePath {path where the Workstation Client is installed} -ArgumentList "--registration-token {bulk registration token}" -Wait`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would describe it as an option: You can also...

It would be good to add the command for Linux here as well. Alawi will provide us with the commands tomorrow after testing.

6. Click **Activate Token**. The **Stations** page displays the timeframe during which the bulk registration is scheduled.
7. Use an automated script to distribute the token to client computers during the allowed timeframe. For example, on Windows machines, you can use the following script: `Start-Process -FilePath {path where the Workstation Client is installed} -ArgumentList "--registration-token {bulk registration token}" -Wait`

After the command runs, the Workstation Clients display the status **Waiting for station assignment**. This indicates that the clients are registered, but not yet associated with a specific station. On the **Stations** page in Workstation Management, you can now see placeholder stations also named **Waiting for station assignment**. These stations correspond to computers which were registered during bulk import.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the command runs or the token is entered manually, the Workstation Clients will initially display the status "Computer not matched to available station." This status indicates that while the clients are successfully registered, they haven't yet been associated with a specific station.

To view these newly registered clients, refresh the Stations page in Workstation Management. You'll find them listed under a separate section as "unassigned computers."

Alternatively, you can pre-configure the computer name for a station in advance. This is done by entering the computer's name in the "Auto-Accepted Computer Name" field when creating a new station or editing an existing one. If the computer name is pre-configured, the client will automatically switch to an Active status with the correct configuration upon registration, and the station status in Workstation Management will update to "Computer Registered" after refresh.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I see the automatically assigning is documented on the bottom.


After the command runs, the Workstation Clients display the status **Waiting for station assignment**. This indicates that the clients are registered, but not yet associated with a specific station. On the **Stations** page in Workstation Management, you can now see placeholder stations also named **Waiting for station assignment**. These stations correspond to computers which were registered during bulk import.

8. On the **Stations** page, click **View** by a placeholder **Waiting for station assignment** station.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Point 8 and 9 is also outdated:

In the case of an “unassigned computer,” you have three options:

  1. Accept Computer: Creates an empty station.
  2. Assign Computer: Allows us to assign an existing configured station.
  3. Reject Computer: Rejects the computer and disconnects/deregisters it.


Instead of reassigning computers to stations manually after the bulk import, you can configure stations to automatically accept computers with a specific name.

1. On the **Stations** page, click the three-dot menu by the station where you want to automatically register a computer.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can also be configured during creation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments

Close sidebar
Morty Proxy This is a proxified and sanitized view of the page, visit original site.