they start to use the application and will regard it as being slow if many of the features they use are not in primary feature block. Additionally, if you are in an environment where bandwidth is limited, then you want to have an accurate primary feature block so that users are not constantly making calls to the server to download additional files in cache. are online articles relating to sequencing best practices : Microsoft Support: Classifying Applications for Sequencing All applications are different and, therefore, no application will require the same amount of time to sequence. However, sequencing estimates can be put into categories based on the complexity of the application, size (both size on disk and number of files), and finally, reliance on resources outside of the virtual application. Another item to take special note of before sequencing begins: nothing will slow down the sequencing process more than not having access to someone who inherently understands the full functionality of the application. Note: This section includes approximate sequencing times referring to first time sequencing and is not related to sequencing via the use of Package Accelerators. These are also very general in nature. Every application will be different. The times are presented only to assist in estimating the time required for a first time non-accelerator project. Application Type Description Time Scale Simple applications are normally small. An example of an Typical application in this category would be WinZip or Adobe Reader. sequencing time: These applications are very straightforward and normally less than 1 hour small in size (usually under 100MB). Very little, if any, modifications are needed to run these applications.
they start to use the application and will regard it as being slow if many of the features they use are not in primary feature block. Additionally, if you are in an environment where bandwidth is limited, then you want to have an accurate primary feature block so that users are not constantly making calls to the server to download additional files in cache. are online articles relating to sequencing best practices : Microsoft Support: Classifying Applications for Sequencing All applications are different and, therefore, no application will require the same amount of time to sequence. However, sequencing estimates can be put into categories based on the complexity of the application, size (both size on disk and number of files), and finally, reliance on resources outside of the virtual application. Another item to take special note of before sequencing begins: nothing will slow down the sequencing process more than not having access to someone who inherently understands the full functionality of the application. Note: This section includes approximate sequencing times referring to first time sequencing and is not related to sequencing via the use of Package Accelerators. These are also very general in nature. Every application will be different. The times are presented only to assist in estimating the time required for a first time non-accelerator project. Application Type Description Time Scale Simple applications are normally small. An example of an application in this category would be WinZip or Adobe Reader. These applications are very straightforward and normally small in size (usually under 100MB). Very little, if any, modifications are needed to run these applications. Typical sequencing time: less than 1 hour
App-V%204.6%20Service%20Pack%201%20Sequencing%20Guide.docx