A. Ensure to install AyaNova when physically at the terminal server (not via remote access). The reason for this is when installing, you will want full rights. If installing via terminal services, you will not have actual full rights.

B. Ensure to be logged in with full rights to the station as AyaNova checks system files and updates if required, as well as registers files

C. Ensure terminal users are not restricted from accessing Windows System files or the installed Crystal Report printing engine files. (when installed to a local station, the common directory is C:\Program Files\Common Files\Crystal Decisions\2.0\bin)

AyaNova uses Crystal Reports printing engine for all printing related features, and we follow the Crystal Reports guidelines for installation of the printing engine and registration. When a user requests a report, that feature  is "taken over" by the printing engine, and if restrictions are placed on the terminal users in that they do not have access to the Crystal Reports printing engine files and the related Windows System files they use, printing will not be able to be accomplished.

D. A couple of users have indicated if the AyaNova database folder is shared to the network from another server other than the terminal server itself, than printing problems occur. This has occurred in some instances, but not all. It is best to test out the trial AyaNova in your environment to determine if this is so.

E. In some cases, if the terminal client is printing to a local printer, printing will not occur; but if the terminal client prints to a shared network client, printing is than fine. This has occurred in some instances, but not all. It is best to test out the trial AyaNova in your environment to determine if this is so.

As the AyaNova trial is full-featured, it is recommended to set up AyaNova in the exact same configuration as you would use before purchasing.

Let us know if you have any questions.

- Joyce

AyaNova Sales & Technical Support

http://www.ayanova.com

As far as the recommendations go, I would like to add these comments:

 

A. Ensure to install AyaNova when physically at the terminal server (not via remote access). Software should always be installed this way on a Terminal Server.  It should also be placed in install mode before installing, or install from Control Panel Add/Remove Programs to be sure the registry is updated properly.

B. Ensure to be logged in with full rights to the station as AyaNova checks system files and updates if required, as well as registers files.

C. Ensure terminal users are not restricted from accessing Windows System files or the installed Crystal Report printing engine files. (when installed to a local station, the common directory is C:\Program Files\Common Files\Crystal Decisions\2.0\bin)

AyaNova uses Crystal Reports printing engine for all printing related features, and we follow the Crystal Reports guidelines for installation of the printing engine and registration. When a user requests a report, that feature is "taken over" by the printing engine, and if restrictions are placed on the terminal users in that they do not have access to the Crystal Reports printing engine files and the related Windows System files they use, printing will not be able to be accomplished. We have a group call Terminal Server Users with Modify rights to the C:\Program Files\Common Files\Crystal Decisions directory.

D. A couple of users have indicated if the AyaNova database folder is shared to the network from another server other than the terminal server itself, than printing problems occur. This has occurred in some instances, but not all. It is best to test out the trial AyaNova in your environment to determine if this is so. We have our database on our file server, separate from the terminal server and it is working fine.

E. In some cases, if the terminal client is printing to a local printer, printing will not occur; but if the terminal client prints to a shared network client, printing is than fine. This has occurred in some instances, but not all. It is best to test out the trial AyaNova in your environment to determine if this is so. We have never had any printing problems specific to Ayanova.  I'm guessing the people who had problems printing locally had problems in all applications, not just Ayanova.  I strongly recommend installing the trial Ayanova anyway to be sure everything does work OK, and the program works the way you want it to.  In our trial, the tech support worked with us to get everything working.  We have upgraded servers a couple of times since then and haven't had any problems getting the application to run without any help from tech support.  It has been a very solid product running on TS for us.

As the AyaNova trial is full-featured, it is recommended to set up AyaNova in the exact same configuration as you would use before purchasing.