Linux has its own user base regardless of whether just barely, it’s there, and if you are using it, and consistently needed to run Windows applications on it, then the ongoing application on Github — WinApps — brings a lot of promises. The product executes so that Microsoft Office apps and Adobe Apps feel local, but recall it is still virtualized. Along with it, the product likewise underpins IE, Explorer, Powershell, Visual Studio, and Windows Full RDP.
How WinApps works?
It’s a slick stunt, and it’s very much executed. You should install Windows on a Virtual Machine in Linux and afterward install the upheld applications like Office, Adobe, and so forth That done, you should configure the username and secret phrase of the Windows user and connect through RDP. There are a couple of more steps, and when done that, you will have the option to get to the applications instead of going through the VM locally. Here is a fast demo
You can look for files and projects and afterward click to open it.
How to Install Office on Linux
To begin with, download WinApps from Github.com. Having done that, follow these steps:
1] Creating WinApps configuration file
This configuration file will hold the RDP username and secret key to connect with Windows running on a virtual machine. Here is the location followed by subtleties in the configuration file:
RDP_USER="MyWinUserName" RDP_PASS="MyWinPassword" #RDP_DOMAIN="MYDOMAIN" #RDP_IP="192.168.123.111" #RDP_SCALE=100 #MULTIMON="true" #DEBUG="true
You can change these as needed by the configuration arrangement you have on Linux.
2] Clone WinApps git repo and install KVM and RDP
sudo apt-get install -y freerdp2-x11 git clone https://github.com/Fmstrat/winapps.git cd winapps
3] Setting up your Windows VM
If you as of now have an RDP worker or a VM, you can jump to section 4, but if you don’t, I recommend you take a gander at all the orders you can use there.
4] Configuring Windows VM
The following stage involves merging a registry in the Windows VM so the applications can be opened. You will likewise need to rename the PC name to RDPWindows if you are using KVM to permit WinApps to recognize the nearby IP.
Press the Windows key, and type ABOUT in the inquiry box. At the point when the section shows up, click on it to open the About section. You can likewise go to Windows 10 Settings (Win + I) and afterward explore to System > About. Click on the Rename this PC button to change the name.
In the System section, click on Remote Desktop, and afterward, toggle on the Enable Remote Desktop option.
Ultimately, consolidate KVM/RDPApps.reg into the registry to empower RDP Applications
5] Connect GNOME/KDE to your Windows VM with alternate ways and file associations
Ultimately, watch that FreeRDP can connect with using this command:
There will be yield from FreeRDP, trailed by a prompt that you have to acknowledge a certificate to add to a confided in source. Next, you should see a Windows Explorer window. This confirms that the connection is made. Close and drop the FreeRDP yield
6] Run the installer
Then the final advance is to run the installer:
$ ./installer.sh --user Removing any old configurations... Installing... Checking for installed apps in RDP machine (this may take a while)... Finished. Configuring Excel... Finished. Configuring PowerPoint... Finished. Configuring Word... Finished. Configuring Windows... Finished. Installation complete.
Is this new? It doesn’t feel like, but the implementation is better. Likewise, it is altogether different from WSL. Since it is done through VM, there will be overheads and will consume additional assets. That is something you should remember. So except if you need something like this, you are in an ideal situation with a VirtualBox’s Seamless Mode or VMware’s Unity Mode.