That question in the title has caused some confusion with our customers. It usually comes up after "What is a Package Accelerator?" , or "There is a Package Accelerator for Office?"
If you follow the links above, you will go straight to an in-depth series of articles on Package Accelerators and to the Accelerator itself. The short answer, however, is that Package Accelerators are new feature with the App-V 4.6 SP1 Sequencer that allow someone else to do the hard work of sequencing and another user to benefit with a rapidly created package.
You can create Package Accelerators to share with the community, or you can use this easy-to-remember URL to download existing Package Accelerators: www.tinyurl.com/appvpa.
Now, back to the original question: With Microsoft Application Virtualization, do you need to sequence from scratch or can you use the Package Accelerator?
The Package Accelerator is for you if…
Sequencing from scratch is for you if…
The Prescriptive Guidance for Sequencing Office 2010 is available. An alternate version will be published soon that addresses workflow changes specific to the App-V 4.6 SP1 Sequencer.
Steve Bucci | Support Escalation Engineer
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
I love these sightly coy posts...
I'm going to ignore the...brilliance...involved in #3 being "1 + 2 and you want it to work"...and focus on what you left out.
For the record I have verified the following across three enterprises, with three different people doing the work, one (me) on XenServer running Win7x32, one running Win7x32 on a physical HP machine, and one running Win7x32 on VirtualBox (these were the sequencing machines).
This is not for you if:
You want to apply patches, as 75% of the time you get to the Customize stage and find VScontent installer, another VS item, and XML editor are all labeled as missing.
You don't use Communicator or several of the most common spam filter addins for Outlook.
You don't mind it not working.
You don't mind manually editing 26 text files because the "not perfect, but at least relevant" sequencer is still too dumb to allow you to set stuff like that when you use accelerators.
You don't mind the package literally HALVING in size just from running an "upgrade" where you literally don't even upgrade anything, just run through it and don't install anything and see how much it "forgets".
Hey, nice try though guys, maybe in version 10 office will just work...of course we'll all be using it local by then because we got sick of holding our breath and praying everytime our Office config req's change and we have to redo it all.
To anyone else, my advice is do one of two things.
1) Install Office 2010 locally because App-V + the ADK is a cobbled together wad of duct tape and chewed bubble gum that just isn't capable of handling complex software properly...AT ALL.
2) Stick to 4.6 non-SP1, do a base (with Office SP1/July CU if it decides it doesn't mind that. Just extract them both and put all the .msp's in the "updates" folder in your office install source location) and then BACK THAT UP and try to add your plugins that don't like Suiting from there, ONE AT A TIME otherwise you are going to spend a lot of fruitless time in procmon trying to find things the sequencer wont let you modify anyway.
But hey, at least we have the ability to make accelerators...and a pointless new multi-path workflow...
I think someone should amend "make a decision between perfect and in time to be relevant" to "slightly less poor".
Do I seem annoyed yet? I'm not the only one. Here's hoping you guys add some Windows 95-era capabilities in SP2 and make fewer "clever" posts.
SP2 Wishlist request.
Scan and Capture option. Because monitoring SUCKS, it sucked for MSI's 80% of the time and it sucks for App-V. I can't help but wonder how many unsequencable applications would sequence fine if the pathetic monitor didn't puke for Random Reason #12398,745,345
And bring back the ability to start and stop monitoring.
Or at the very least update it so such space age technology as "command line arguments" can be used with the "select an install" dialog box. And the Run dialog box which requires you to wrap everything in quotes if you have arguments to use (and pray they don't need quotes in them).
And fix the issue where you cannot set any settings via anything other than a template because it triggers a "new project" status that has to be discarded before ACTUALLY starting a project.
Define soon, when is comes to an update on the prescriptive guidence for sequencing MS Office 2010 with the new 4.6 SP1 Sequencer.
There are 4 blog posts about using the 4.6 SP1 sequencer for Office 2010.