Citrix Installation - Top Ten Tips

Would anybody be kind enough to put together a set of tips which should be considered when starting a Citrix/Terminal Server installation for Navision (e.g. Reboot the server every night or use IP printing rather than IPX). Thanks.

IMHO… 1)You dont need to reboot servers every night, every week, or month or year. People who say this have no idea what they are on about. This, of course, is making the assumption that the hardware and software are installed and working correctly, and ignoring the fact that NT/2000 have always had memory leaks and do often run out of memory. I have had other OSes (Novell/*nix/etc) run for a year or more without a reboot. Our NT servers here are rebooted maybe 5 times a year. (Citrix, SQL, etc) 2) Use IP whenever possible, Netbeui/bios and IPX are slow, especially when you combine them all on a box, because people want internet access or something. Navision uses IP very well, so try and use IP only, and it cant use IPX. You would be suprised how quick a network can be with only TCPIP running on it. IP printing works well too. 3) The default settings for installations of NT/TS/Citrix are perfectly acceptable for most installs. Tuning of registry settings and the server settings is definitely possible, and worthwhile, but dont “over optimise”. 4) Citrix - turn off sound 5) Citrix - try and do things like 4) and default display settings etc from the server connection settings rather than each client 6) If using a WAN, think about using the IP address in the Navision connection rather than the server name - no worries about name resolution - helps if you arent using WINS, or DHCP etc. 7) Set all the connection properties for the Navision client from the icon, eg, servername=x,company=y, on the start menu for all users or desktop for all users, or both. Theres 7… :slight_smile: Craig Bradney Project Manager - Technical Navision Solutions & Services Deloitte Growth Solutions Deloitte Touche Tohmatsu P:+61-2-9322-7796 F:+61-2-9322-7502

…and here’s some more: 8)If You have a LOT of users: Think about what network interfaces You’re using. You should use some card with built-in CPU. 9)Turn of the mapping of local printers. Also download the little patch to codeunit 1 that is avaliable in the download area at Then You wont have any problems with the ne nubers when adding or deleting printers in Your system 10) You must define TEMPPATH in the commandline since You won’t have the same temp diretory the next time You log on. You can have all the users temporary files in the same directory. I’m sure there are more to think of as well. Lars Westman Bizguide AB