Despite its critical role, the Multi User Server is not hardware-intensive. Unlike a Tekla Structures workstation, the server’s primary job is to process network requests for object ID numbers, not to render complex 3D graphics.
The server machine requires a fixed network IP address so client workstations do not lose connection due to dynamic DHCP lease renewals.
Understanding how to deploy, manage, and configure this background service ensures error-free collaboration without structural database corruption. How Tekla Multi-User Server Architecture Works Tekla Structures Multi User Server 23 20
In the world of high-stakes structural detailing and BIM, speed and coordination are everything. While many teams are moving toward cloud-based solutions, the remains a cornerstone for firms operating on robust local networks.
Users work on local cached versions of the model. When a user clicks "Save," the client machine communicates with the Multi-User Server to stream changes back to the master model database file. Despite its critical role, the Multi User Server
: The software must be installed on a dedicated server or a workstation that acts as the host for the multiuser service.
The is a dedicated background service developed by Trimble to allow multiple structural engineers and detailers to work on the same 3D BIM model simultaneously. By eliminating the need to copy, split, or manually merge separate files, it keeps the entire project team synchronized in real-time. Understanding how to deploy, manage, and configure this
| Feature | Tekla 20.0 | Tekla 23.0 | |--------|-----------|-----------| | | 2015 | 2016 | | Server OS Support | Windows Server 2008 R2 – 2012 R2 | Windows Server 2012 – 2016 | | Tekla Client Compatibility | TS 20.x only | TS 21.0 – 23.1 | | .NET Framework Required | 4.0 | 4.5.2+ | | Automatic User Disconnect | Manual only | Configurable timeout | | Performance for Large Models | Moderate | Improved (better lock handling) |