Every Friday, we dedicate this space to sharing solutions for some of the most frequently asked questions posed to our ThinManager Technical Support team. This weekly feature will help educate ThinManager Platform users and provide them with answers to questions they may have about licenses, installation, integration, deployment, upgrades, maintenance, and daily operation. Great technical support is an essential part of the ThinManager Platform, and we are constantly striving to make your environment as productive and efficient as possible.
We have configured our network to see our 2nd ThinManager server as PXE secondary server. After testing some of our terminals they succeeded in seeing and getting the image from our 2nd server.
Now, for balancing purposes Is there a way we can tell which ones are being assisted by the primary and secondary server?
The PXE boot process isn’t load balanced. For a synchronized pair of ThinManager servers all PXE requests will be replied to by the master server. If that server fails then the secondary will begin replying to PXE requests.
You can check the boot server on the bottom of the properties tab for a selected terminal.
We also have a quick video which discusses our PXE Server here.
We recently added a number of new client to our ThinManager system, however when we try to shadow these clients we see the error “Client Connection aborted”. Is there anything that has been known to cause this issue or anything that I can get from the system which may further indicate as to what is causing this? Our existing clients work fine. Are there any logs to check?
It sounds like a network issue. Make sure Windows Firewall is off or appropriately patched, and that there are no hardware firewalls in the network.
Below is a link with all of our port information:
I have found that a new windows update KB2762895 has now made WinTMC inoperable on my Windows 64 bit machine. Is there a fix for this?
We just released a new version of WinTMC, you can download it from our downloads site:
We are experiencing an auto-synchronization is the issue, and had to turn off the auto-sync feature. What user does the auto-synchronization use to access the other server?
To review the cost savings of using the ThinManager Platform, visit our ROI Calculator here.
To read about successful ThinManager Platform deployments, visit here.
To see when the next ThinManager 2-Day Training Session is being offered, visit here.