sequencing office pro plus 2010 32bit with app v

Appv and office 2010

Why office on appv

Isolation - no conflicts
Multiple versions of office

Fast deployment
Centrally manage apps
Install once deploy many times
Streaming the app to the use

Control over apps add-in's
Virtualize the app
Virtualize the add-in
Only deliver apps and add-in's to those that need it

Easy servicing updating apps / plugins etc

SCCM integration, simple delivery

Apps virtualized on appv think they are installed on the OS and can see the OS files.
The OS cannot see the appv application files.

This yeilds benefits and issues called integration limitations. For example a user is on sharepoint in IE (which cannot be virtualized) They click on a link that should open a document IE looks for the activex control that should launch office but since office is virtualized it cannot find it and fails.

To resolve this MS has created the Office 2010 deployment kit for app v. This creates bridges between the OS and the virtual applications. This is to give the users the best of both worlds.

The bridges that link the virtual world with the native world are known as feature proxies. Fast Search in Outlook. Opening documents in sharepoint. Send to one note printer. Send to mail function etc

OSD files allow us to launch virtual bubbles in the OS. To configure the proxies we need to add another OSD file with a launch path. We also need to add a modified activex control nativly. This activex control is aware of the virtual bubble. When the user click something in sharepoint IE looks for the activex control. The modified activex control redirects it to the activex control in the virtual bubble and that then launches virtual microsoft word.

Some users have opted to install virtual office 2010 along side native office 2007 and users are to move over gradualy. This is not a good idea because exchange was not designed to handle a single user managing one mail box with two different clients constantly there have been many issues when doing this.

Current limitations
Virtual -> native app integration
Solution is sequence other applications with office. However you need to be aware. The max package size is 4GB.

The way around this is to use DSC to package applications seperatly and link them together.

Another issue is that the OS is unaware of office 2010. The deployment kit solves that by creating the bridges.

two critical questions
Is office being used more as a platform
Does the business write lots of plugins for office etc.

Do applications that integrate with office do they need to stay native, can we virtualize them.

You can sequence
Office Pro plus
Stanard
Small business

You can also virtualize stand alone applications.

You can also Visio in with office pro with visio. There are some issues with licensing here more on that later.


What apps integrate with office ?
Live meeting
Office communicator
Windows sharepoint services
Add-ins (Outlook connector, conferencing add-in tool)
Line of business applications

First option sequence everything into the same package. The downside is that every user that recieves the package will get all that apps, but is that a problem for your business.

Another option branch office package is not recommended. Create one or more packages

Dynamic Suite compositon
Sequence each app seperatly
Link them with DSC

From top to bottom there is increased control but increased complexity

MS recommends to sequence the following with office
Live meeting
Office communicator
Common add-ins that everyone uses
Sharepoint integration

Then sequence other add-ins and line of business plugins in another package and link with DSC

The maximum package size and avoiding it.
Max size is 4GB
Full compression can save up to 1GB off the package size.
MSO Cache can be removed during sequencing time to save 800mb of space.
MSO cache can be used to let the user run repairs we won't be using this in virtualized office.

Office 32bit has the proxy features, 64bit does not.

How to customize office
OCT / Group Policy
Config.XML


Its a good idea to use a test plan. Get a top 5 list of what users need to do.

Installing the deployment kit on the sequencing station. Make sure to use 32bit.

msiexec /i OffVirt.MSI
[featureflags]
[license flags]
This is where you can do a combination`and activate office and visio for example

Sharepoint needs a reg key deleted during monitoring see recipe
Visio has a SxSAppExtension
Office 2010 - Merge with local
Outlook 2007/2010 co-existence recipe
Stick with one outlook until you are ready to fully move and then move
OMS add-in see recipe

OSD version numbers only have to match not the office version number

DSC
Load the root of sequenced apps
All apps will be loaded
select the primary
select the seconday
you can make mandatory if you want
most of the time you wont need to
click save
your OSD's will be over written.
However it will create a backup file.


How do I deploy my client
Install appv client
install deployment kit with only licensing parameters
publish your office package
configure deployment

Gotchas's with OffVirt
No spaces between commas
Curly braces around package guid
Appnames are Case Sensitive


Office 2003 is (office 11) reg hex value for 11 (0x0000000b)
Office 2007 is (office 12) reg hex value for 12 (0x0000000c)

Install commands
\\server\share\setup.exe /adminfile \\server\share\custom\mycustomfile.msp


App-v Forums
http://social.technet.microsoft.com/Forums/en-US/category/appvirtualization

Recipe
http://support.microsoft.com/kb/983462

Seqencing video
http://www.youtube.com/user/mentvanderplas

How to use DSC
http://technet.microsoft.com/en-us/library/cc843662.aspx