In older versions of the App-V sequencer you could setup a template using the default.sprj file, which was a great way of enforcing certain standards, I posted a blog post about this last year. You can read about it HERE .Before going into the Templates I should explain that although similar, I am not describing Package Accelerators which are like application specific templates, Package Accelerators can also contain more than just a template, it can be accompanied with other useful data or information in regards to packaging an application, which is amazing when you are sequencing applications as somebody else has done the hard work for you. For an example of these Accelerators take a look at the Technet site which is HERE
There was also an option in the later versions of 4.x which allowed you to create a template, save it and then point your sequencer to use that template. In App-V 5.0, Microsoft got rid of the .sprj file format and also those template methods.You can no longer point to a template file, but you can create a template which you can load if desired. You will see the Template Save and Load option under File.
First you should actually create your template. To do this you open your sequencer, browse to Tools and then click on Options.
You are going into Options as this is where you can modify the options which you can save into your template. The above dialog shows exactly what can be saved, General Options and Exclusion Items. The default tab which appears when you open options is the General Options as mentioned above.
In the above example you can see an option to Package Pre-installed VC runtime dependencies which is a feature new to App-V 5.0 SP2 which as of this post is in beta. For a full description take a look at Nickes post HERE The other options here which you can modify for your template is the scratch location which is like a specific temporary working directory for the App-V Sequencer. You can allow Windows Updates to be captured during the sequence, it’s Best Practice to disable Windows Updates as it creates noise, meaning files or registry which get modified or added by a Windows Update that are not related to your application that you are sequencing. I guess an option you may want to allow it, is when you have a certain Microsoft application which you want to install during the sequence and then install a Windows Update(s) for the app. There’s an option to append the filename for each time you save the application, it’s not really relevant any more but I like to leave it checked so I can see which iteration of the app I am working on as I document this. Always trust the source of Package Accelerators is an option to allow the use of any and all package accelerators, why this is relevant is because you can download Accelerators created by the Online App-V Community.
The Exclusion items is a big one which you will certainly want to give some attention to. Microsofts default exclusion items are quite good. If you run the Sequencer on a vanilla Windows machine the settings are likely to be good for your sequencing. The Exclusion items lists the Directories and Registry hives which get ignored by the Sequencer, so any changes to these directories do not get included into your virtual applications, the identified directories are selected because they routinely receive changes that are unique to a user which you obviously don’t want saved to your application (in most cases) that is because files or registry unique to you will likely not work for the next user. These files or registry that are unique to a user also tend to get re-created if they do not exist when the application is run. You should note, if you are using a VM on your domain and it receives Group Policies or if you have your companies applications or any services configured to run on the Virtual Machine then the out of the box Exclusion items, likely will not be good enough. So how do you know what you need to exclude for your environment?