we solve it with Termit
Imagine: you've decided (or life has decided for you) to migrate your employees from Windows to Linux. Today I'll tell you how to do this while still allowing users to access their usual applications.
We will solve the problem using our Termit terminal server as an example. Below you will find step-by-step instructions on how to use it to set up terminal access to Windows applications.
Many companies are now migrating to Linux for legal and information security reasons. But users are understandably not thrilled about the prospect of losing access to their familiar Windows applications.
So we are faced with the task:
provide access to familiar applications in the new OS;
guarantee their stable operation;
to make the transition as painless as possible for employees.
Therefore, it remains to take on the mission of achieving interoperability between networks.
We implement Termit, take Windows into a secure environment
Direct migration of users from Windows to Linux is associated with a lot of organizational and technical difficulties. Our approach is to leave applications in the Windows environment, but give Linux users access to them through Termit. This can be easier and faster than changing people's habits. Plus, Termit allows you to flexibly configure access rights to applications.
We pass the mission with Termit
The task has been set, the requirements have been collected. It is time to begin our mission. And may the instructions be with us!
Let's start with deploying Termit. Read how to do this in article.
After deployment, you need to configure Windows Server and connect it to Termit. Detailed instructions are in our wiki.
Adding a Windows Server to Termit
Once the server is configured, we add it to the Termit service:
Log in to Termit with administrator rights.
On the “Servers” tab, select “New Server”.
Enter the FQDN of the server and select the “Windows” type.
Click “Next”.
You can skip the next step (we will add additional parameters later).
We check if everything is correct and click “Create”.
After this, a window will open with a long line of code that you need to copy.
Let's go back to Windows Server and run the copied command in cmd.exe.
After executing the command, check the server status.
Now your Windows Server is ready to work in conjunction with Termit. You can proceed to configuring applications for users.
We publish applications
The applications already exist, but no one can use them yet. Let's move on to organizing access: we need to combine the servers into a group and publish the applications.
To do this in Termit:
Go to the “Server Group” section and click “New Group”.
Enter the group name and select the “Windows” type.
Click “Next”.
Here you need to select a server from the list and click “Next” again.
Skip the rest of the steps and click “Save”.
The next step is publishing applications:
In Termit, go to the Applications tab.
Select “Add application”.
Fill in the fields:
Application name: Notepad… Well, or let's take something more complicated – MS Power BI.
Operating system: Windows.
Type: Application.
Command to launch: specify the full path to the application exe file.
Click “Next”.
Select a server group and click “Next”.
Click on the “+” sign and add the user group from Active Directory for which we will publish the application. Important: also add this group on the Windows server to the local “Remote Desktop Users” group.
Click “Next”.
Check the entered data and click “Create”.
End users
Now it's time to test the settings on real users. Choose a colleague who is ready to try our system first.
We give the test user clear instructions:
Install one of the domestic operating systems: RED OS, ALT Linux or Astra Linux.
Install Termit Desktop:
Log in to Termit using your employee account.
Download the Termit Desktop distribution of the required version.
Run the installation.
After installing Termit Desktop:
Launch the application.
Enter the name Termit Broker.
Log in using your employee account.
Launch your favorite application on Windows.
If the testing is successful and the employee confirms that everything is working fine, you can transfer everyone else to Linux.
We have accomplished a difficult mission, and we did not have to conjure to run Windows applications in an unnatural environment for them. Users work on Linux, as required by corporate standards, and applications run in their native Windows. Everything works stably, everyone is happy, which means we are too.
In the future, if you need to migrate from Windows terminal servers to Linux, you can easily add a new server group to Termit. This will provide access to applications from both Windows and Linux.
If you have similar experience or questions about working with Termit, write in the comments. Let's discuss this important task for many IT specialists.
