Virtualization

When I sequenced Office 2007, I used my client's baseline system as my sequencer but removed Office 2003 (no Office products). At stream / launch time, Office 2003 remained the default Office product until I manually added Office 2007 FTAs on my system. This allows those that want to make use of Office 2007 optional at present.

When Office 2007 gets mandated, I can make those changes on the server. Is this what you were looking for?

Thanks Badshadd.
The issue is slightly different... My Question is As i guess some applications during installation if it identifies that Office is installed it is installed differently. And even few apps integrate with Office during installation.
So If Microsoft Office is part of the base image of the client, then should we include Microsoft Office as part of the base image of the sequencer ???

I wouldn't say that it doesn't matter for the present where a previous specific Office version is present on all systems, but here are some things to consider.

1. Do all of your clients have the exact same local Office installation?
   
2. Will you have to reaccomplish your sequenced package once systems are delivered without an Office product?
   
3. If you stream to a 'clean' system without Office, will some of the files / registry settings be missing that SoftGrid-enabled version of Office assumes is already there?

I don't claim to be an expert, but creating an 'upgrade' virtual Office package in theory would rely on having a specific Office product already installed. I would only recommend that your SoftGrid-enabled Office product should stand on its own & not rely on something already being present.

The actual problem is that the Microsoft Office application in all the client machines are not virtualized...

1. Yes they have the same local Office Installation
2. Guess once they decide to go for an upgrade or a virtualized Microsoft Office app we might have to resequence the applications
3. Cant really check the 3 pt in your previous post in our environment

One answer is to always sequence an application and all it's depencencies on the cleanest machine to build the most portable sequence but... Since Office is a core application on the base load I would suggest leveraging it. Patching Office sequences every month would be painful and I think Office is one of those things that can be left in the base and sequenced on top of. If you have an application that needs a non-standard configuration of Office then I would consider that to be a candidate for virtualization.