Sorry Zubaz, I just don’t have time to pull all my machines off the network and link them in that fashion, also some of the machines do not have firewire - so the alternate connection method isn’t feasible in this situation. Thanks for the troubleshooting suggestion though, I do appreciate it. Are you with Stardock or just a friendly board member?
The PC's are connected via a 10/100 hub, which in turn, is uplinked to the production network at our workplace. The machines in question are all on the same hub in each instance respectively. (Not all 10 users on the same hub, but rather 3 machines per user connected to their own hub) Cross over and firewire are not an option for use, but where these are separate hubs/switches ranging in brand, I am not sure that would yield any test results that could lead to a resolution. Is
Additional issue in relation to machines being cycled. While a secondary is in the reboot process, the primary machine tends to grab the mouse control back on a cycle. Seems like every 20 seconds or so while a secondary machine is rebooting the mouse control will revert to the primary without warning (ie. I’m closing applications on a secondary and notice the cursor is unresponsive, look over to my main machine and find that I have just shut down a RDP session). This is a
I am using the most recent version of Multiplicity PRO as is 10 other tech's in my group. We like your product, but really cant purchase any more licenses until the underlying issues are resolved... As you probably already know, if someone were to hit cntrl+alt+del to unlock a secondary machine by accident (forgetting the cntrl+alt+bkspc), multiplicty delivers some odd behavior. Sometimes the result is that you cannot click on icons, sometimes alt or cntrl will just not function.... The