infor.com
concierge
infor u
developer portal
Home
Groups
FACTS - Partner Community
Plugin/Multi-User WindX on Terminal Server
salbritton
I have a customer on FACTS 7.7 on a Windows 2008 server. They have a separate terminal server that they are considering using to allow their remote users to log into FACTS, due to slowness with connecting via VPN and traditional stand-alone WindX on the remote PC.
I believe you used to be able to able to install a "Multi-user" WindX license on the terminal server, which (as I understood it) was client side enabled. If I understand correctly, this was the WindX plug-in (as opposed to the standalone WindX).
Our thought was to install the plugin WindX license using the 30 day demo (like the standalone initially is authorized for) to see if this provides satisfactory response times. If acceptable, we would order the Multi-user WindX licensing for the customer.
We've installed the WindX Plugin many times before at other customers on Terminal Servers, always with a Pro Bundle license. However, this customer does not currently have a Pro Bundle ProvideX license (nor should they need one, if we go with the "Multi-User" WindX license (if I understand correctly)).
When I installed the WindX Plugin on the Terminal Server and tried to launch FACTS from the Terminal Server, I got a message "Plugin connections not allowed on this server".
Can anyone provide insight on whether I understand things correctly, and/or what I may have done incompletely or incorrectly? Any advice/direction is sincerely appreciated. Thanks.
Find more posts tagged with
Comments
hpocius
Multi-user Windx is the same as a Stand-Alone WIndx with a user count that is greater than 1.
This is different than what you have traditionally used which is Pro-Bundle + Windx Plugin Client
Legacy Contributor
If you want WindX running on the terminal server, you need multi-user windx, which requires a WindX serial number, a user count, and an auth code. you can exchange multiple single-user windx serial numbers for a multi-user windx with the equivelent user count.
if you want server-side licensing, you need either to upgrade their ProvideX to Pro-bundle (which includes the Thin-Client Plug-in) or add the Thin-Client Plug-in to their ProvideX - it's simply another package ID. there is no trade-in of stand-alone WindX (single-user or multi-user) for either pro-bundle or the Thin-Client Plugin. with Pro-bundle, it's a one-to-one match of users on the ProvideX serial number. with Thin-Client Plugin, you can specify the number of users, from 1 up to the ProvideX serial number license - they are concurrent use.
There is no longer any product called "WindX Plug-in" - that was a Sage product that existed prior to Pvx version 8, when the Thin-Client Plugin was created.
At this time, we're still working with sales on the price sheet for Thin-Client Plugin - you would need to call your RVP for details.
SOCIALSasPLvendornumbers.doc
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
ION Connect
ION Workflow
ION API Gateway
Syteline Development
CPQ Discussion Ask a Colleague
Infor Data Fabric
Infor Document Management (IDM)
LN Development
FAQs, How-To, and Best Practices
API Usage