On the server side:
If the web server has been set up for Guacamole, add the lines between the
<VirtualHost *:80>
ServerName examplehost.crecom.com.au
Alias /printers /var/www/html/printers
<Directory /var/www/html/printers>
Options Indexes FollowSymLinks MultiViews ExecCGI
AllowOverride None
Order allow,deny
Allow from all
</Directory>
ProxyPassMatch ^/printers !
Proxypass / http://localhost:8080/guacamole/
ProxyPassReverse / http://localhost:8080/guacamole/
ErrorLog logs/guacamole.log
CustomLog logs/guacamole-access.log combined
</VirtualHost>
<VirtualHost *:80>Create the following directoriy /var/www/html/printers/
And copy 2 files from sam
/u/ccdev/std/internet/cgi/deviceservice.cgi /u/ccdev/std/binl/printer
run prnaad and for the "System printer name" you have to specify a directory (start and end with slash). To make things less messy, put them in a subdirectory containing all the printers:
/printers/docket/ /printers/laser/ /printers/label/
Program should automatically create them (below your $CCDIR). If it does not, then you may have to do it yourself.
If this is for a company with many locations, or a server with multiple companies, it might be a good idea to place these under the company directory (and maybe with individual directories for locations).
Once the above is all set, proceed to setting up the client.
On the client side:
Download 2 files:
http://customers.crecom.com.au/winprint/jre-8u171-windows-i586.exe
http://customers.crecom.com.au/winprint/testclient.zip
Run the jre-installer, follow all the defaults.
Unzip the testclient.zip into c:\crecomps\
Run the install.bat file. It should open some DOS windows and close with no errors. Check the logs under c:\crecomps\logs . You should not see any obvious errors.
Run the crecompsw.exe program. Go to the startup tab and look under arguments
start&URL=<URL>&SECS=<INTERVAL>&CENV=<CCDIR>&CP_<CREPRINTERx>=<WINPRINTERNAME>&CP_<CREPRINTERx>=nexa
Where:
<URL> is in the format http://drboom.crecom.com.au/printers/deviceservice.cgi
<INTERVAL>is number of seconds between checking for new jobs. 5 seconds seem ok, If server and client can take it, you can go as low as 1 second
<CCDIR> is their CCDIR like /u/cc/
<CREPRINTERx> is the Control short printer name (the ones you set up in prnaad on the server). x is 1 to 3
<WINPRINTERNAME> is the corresponding windows printer name
Go back to the General tab and set startup type to "Automatic". Click "start" and "Apply". This should allow the program to automatically start up when you reboot the computer.