Getting Started with Sequencing in App-V
What to Sequencing On
The App-V Sequencer is used on very clean OS images. The less that is on the image the better. I prefer just the OS and Service packs. Hotfixes are usually OK, but don’t usually matter given how you use this OS. We usually sequence on a virtual machine that we can create a snapshot/checkpoint, allowing us to revert back to a known state before sequencing an app. Here is a blog post I previously wrote documenting my lab sequencer build.
We usually sequence on desktop OS rather than an RDS Server, even if we plan to deploy on the server. We also select an OS version that is as old as the oldest client we might deploy apps to. So for many customers this means a Windows 7 with SP1 operating system. Sometimes there are apps that require the server OS, so we use that also when we have to. If I use the Server OS, my preference is to NOT add the RDS role.
If you have both 32 and 64 bit operating systems in use for clients, we’ll normally sequence on the 32-bit OS. The biggest exception here is due to shell extensions. If you need them, you must sequence on the OS bitness (Microsoft uses the confusing term “Architecture”) as the client. XenApp customers that don’t allow full access to the RDS desktop won’t care about the shell extensions.
When possible, the mantra is sequence only once, run everywhere.
Read the entire article here, Getting Started with Sequencing
via the fine folks at FSLogix