jh,
Deployment in TestStand can be a big pain in the neck. You can force the shortcut back by using a batch script. On the Installer Options tab in the TestStand Deployment Utility there is a button titled 'Custom Commands'. You can run any number of scripts or command line arguments. You will just have to figure out how to create the batch script to create the shortcut and point it to TestExec.exe. Should be a pretty simple google.
I'm probably the one that told you to check that box but I never use it. I've never found it reliable. So if I need to deploy an ini or something I add it to my workspace and make sure I put it in the right place when distributing the files.
The best thing I've found with TS deployment is to create a baseline. Basically start with a blank/new (no NI software) computer. Install LV, TS or whatever else so it is all default. Then go into TS and set up all your station options, report options, process model, etc. for what you would like on your deployment machine. Then create a workspace with a single project. In there put any files that will be deployed to all your machines. Then create a .tsd using the TS Deployment Utility. In here you won't really be deploying any sequences. Include all necessary driver, run time engines, etc... that will need to be on all your deployment machines. Set up all custom commands to associate sequence files with TestExec.exe or any batch files that will create shortcuts, etc... If you have your own TestExec then you will need to include it as well. Then build it. it should be huge (like 1G or more if you include all the NI drivers).
Once you have that build you can install it on any computer and then simply deploy you sequence and dependancies (nothing else). It makes build time quicker because now all you have is the sequence file and some VIs or dlls. Then all you do is install the baseline and then any other builds (tests) on top of it. Most of your headaches will go away doing it this way.
