I think that you merge two things here which do not fit well together:
Deployment and runtime flexibility.
I ASSUME that your word "installation" refers to "what is executed later on that machine".
"Installation" in a traditional view is "what is COPIED to your machine". So installation tells nothing about what is executed later or not.
My recommendation is that you INSTALL all sequence files on the target machine. You should add some custom code which pre-selects sequence files available for the SPECIFIC TARGET, essentially making all other sequence files on the target (which are present, but shouldn't run on this machine) 'inexecutable'.
The alternative would be to go into the MSI package which was created by the TestStand Deployment Utility. I am quite sure that you can alter its setup to do what you seek, but i don't know how. I can imagine that you require additional tools from Microsoft for this.
Norbert
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.