User Unable to Schedule Jobs on Remote 32-bit Console
Last Updated January 16, 2019
After setting up a remote 32-bit console on an end user's machine that end user is unable to schedule jobs on client machines from that console. They are able to see the client machines and the jobs but they do not receive the job scheduling pop up box when trying to schedule work to be done.
Ghost Solution Suite 3.x
There is not error message specifically given when trying to schedule the work on the client machine. The scheduling pop up box simply doesn't appear so the job can never be scheduled.
This can be caused by either an installation issue with the remote console or a licensing issue on the remote console.
For the installation issue with the remote console. If a remote push of the console was being performed the remote end user machine would simply reboot and the remote push would fail. If an installation of a remote console was being performed directly on the end user's machine the installation would hang and not continue. It was found that the installation of the vcredist_x64.exe and vcredist_x86.exe files were the cause of the issue. These two files are needed when installing a remote console on an end user's machine. These files may not install correctly when called by the Ghost Solution Suite Installer and this causes the hang. To resolve this issue run each of these files manually on the end user's machine. These files can be found in the DSSetup folder on your Ghost Solution Suite Server. There may be prerequisites for these files in which cause you'll need to install those first. Once these two files have been ran successfully, rename them so they can't be called by the GSS installer. Then run the installation of the console again. It will complete and function as expected.
For the licensing issue it may be necessary to install the license through the remote console. In this situation, the remote console was configured manually by the customer. The ODBC entry and desktop shortcut to express.exe was created manually. To resolve this issue simply register the console using your existing license file (.slf). Open the remote console on the end user's machine, click on Help, and then go to Register. Browse to your license file and apply it. Close the console and reopen it. This should allow the end user to schedule jobs correctly.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe