Winflector Setup Guide Install and Publish Windows Apps for Remote Users
Install one Windows application on a single office PC, and every user opens that same app from their own machine — only the app window travels, not the data. That is Winflector, and this is the full setup.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 9 minute read
🎥 Watch the full video — Winflector installation and app publishing, shown live step by step
Winflector is a small server program (made by OTC) that you install on one Windows computer — the server. The applications your office uses are installed on that one machine only. Users then connect from a web browser or the small Winflector client and see just the application window, as if it were running on their own PC. Winflector uses its own lightweight protocol, not RDP, which is why it also works on a normal Windows 10 or 11 PC, not only on Windows Server. Below is the complete flow: prepare the server, install, create users, publish your first app and connect.
Winflector Server — published applications and connected users
📊 TallyPrime — published application3 users connected
📄 Office Billing App — published application1 user connected
🖨️ Winflector PDF Printer — ready for remote printingReady
🔌 Server status — wfserver.exe runningRunning
☝️ One server, the apps installed once — every user opens the same published applications from their own device
1
Prepare the Server PC First
The server does all the real work, so prepare it like a small server, not like a spare desktop.
Install the application you want to share (for example your accounting software) on this PC and confirm it runs correctly locally first
Give the PC a fixed IP address on your office network so users always find it at the same address
Keep RAM in mind: every connected user runs a real copy of the app on this machine, so a busy app with 5 users needs noticeably more RAM and CPU than a single user
Keep the PC on during working hours — if the server sleeps or shuts down, every user is cut off
2
Install the Winflector Server
Download Winflector only from the official website, winflector.com — modified copies from random download sites are a real security risk on a machine that holds your data
Run the installer on the server PC and complete the server installation (the server program is wfserver.exe)
Start the Winflector server and let Windows Firewall allow it when prompted — the server must be reachable by your users
The free version works for 2 concurrent client devices and has no time expiry, so you can complete and test this whole setup before paying anything
3
Create User Accounts
Every person who connects needs an account. Winflector gives you two honest choices.
Winflector accounts — create a user name and password inside Winflector itself. Simple, and best for small offices
Windows authentication — users log in with their normal Windows (or Active Directory domain) account. Better for bigger offices where accounts are already managed centrally
Give each person their own account. One shared login for the whole office means no record of who did what, and no way to block one person who leaves
4
Publish Your First Application
In the Winflector server, add a new application and point it to the program file, for example C:\TallyPrime\tally.exe — use the real path of your installed app
Set the working directory to the folder the application expects (usually the folder the program is installed in). A wrong working folder is a common reason an app opens on the server but fails for remote users
Choose which users are allowed to see and run this application — a user should only see the apps that belong to their job
Save. The application is now published and appears in the user's application list after login
5
Connect From a Browser or the Client
Browser (HTML5) way: the Winflector server has a built-in web server, so the user just opens the server address in a browser, logs in, and clicks the application — nothing to install on the user PC
Native client way: install the small Winflector client (wfc.exe) on the user PC, enter the server address, user name and password, and launch the app. The native client connects on port 6601 by default
The application window opens on the user's screen, but the program and its data stay on the server. Test first inside the office network; opening access from outside the office needs the safety steps covered in our internet access guide
🔴 Test inside the office first. Get everything working on the local network before you think about access from home or other branches. Most setup mistakes are found in five minutes on the LAN — and are much harder to diagnose over the internet.
🎥 Watch the Complete Setup in the Full Video
Server installation, user creation and publishing an application — the complete Winflector process is shown live in the video, screen by screen.
Partly. The free version is the full software with no time expiry and can even be used commercially, but it is limited to 2 concurrent client devices and has some feature limits (for example, no server farm and no additional SSL security for HTML5 clients). For more simultaneous users you buy licences counted per concurrent device.
Does Winflector need Remote Desktop or RDS CALs?
No. Winflector does not use RDP technology — it has its own protocol for sending the application window to the user. That is also why the server can run on a normal Windows 10 or 11 PC and not only on Windows Server. Your application itself still needs whatever licence its own maker requires for multi-user use.
Can users open the app on a phone or tablet?
Yes. Users can connect from a browser on almost any device, and there are native clients for Windows, Linux and Android. On the server side nothing changes — the same published application serves all of them.
This guide is based on the Technical Anshu Winflector setup video • Stuck on any step? Ask in the video comments — help is available there 🙏