- Spindle Professional v6*
- Spindle Professional 2012
- Spindle Professional 2009
- Spindle Professional 2007
- Spindle Professional 2005
* When using Spindle Professional v6 under Windows 8 or Server 2012 and later, or when using Spindle Document Management (v7), there is no need to create the .cmd file as described below.
More and more sites are now trending to deploy centralised Servers which host all software applications and devices. Instead of having IT Administrators maintain local machines all software updates configurations are made the one Server. The remote application gives the user the impression of the application running from the local machine. However the application is actually running from the server.
After installation of Spindle Professional on a Server which hosts;
- Citrix Published Applications.
- Citrix XenApps.
- Windows Remote Applications.
- Or similar
Any documents printed to any of the Spindle Printer drivers throw the following error message “The Spindle Pro Auto Printing Agent was not found”.
If Published Applications are being used the client session will only have the accounts package running i.e. Sage.exe. When Documents are processed via a Spindle Printer, the printer drivers look for the Spindle Professional Monitor process running. As this is not present on the user’s remote application session the client will get the error message that the Printing Agent was not found.
To support this environment the Spindle Professional Monitor executable has to run in the same remote session as the remote Published Application.
There are a number of methods to achieve this, using Group Policy, editing the Registry or by creating a Windows batch file (*.cmd) that will launch the Spindle Professional Monitor executable in the background of the client's published application session, and then launches the required published application.
Example cmd file:
CD "C:\Program Files (x86)\Draycir\Spindle Professional 6" START SpindlePro6Monitor.exe CD "C:\Program Files (x86)\Sage\MMS\" START SageMMSDesktop.exe
The example above uses Sage 200 as the accounts package, we would configure the correct paths for any other accounts package.
We now use this .cmd file as our published application, so that to the user there are no extra steps obver launching the accounts package from its own published application icon.
|Related Product||Spindle Professional|
|Original Author||Hiren Kansara|
|Update Author||Vince Hodgson|