locked
Reliable Office 2010 Sequencing Method? RRS feed

  • Question

  • So, which of these two method's provides the best results?  From what I have read they both do the same thing except that they a do it a different way? 

    http://www.softgridblog.com/?cat=2

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

     

    Thursday, June 17, 2010 12:11 AM

Answers

  • Hello,

    For statement one, see this hands-on example, which I advise that you read thoroughly

    http://www.softgridblog.com/?p=153

     

    #1 Recommendation is to sequence all applications (for office) into a single package using one common asset directory

    Dynamic Suite Composition does not support to add a full software installation as a secondary package and only focuses on providing support for plugins. Project, Outlook are not considered plugins.

    #2 See above, I have experiences from all types of ways and everything always depends on the requirements of the application and the reason its sequenced. Meaning, extremely customer specific.

    /Znack

    Thursday, June 24, 2010 4:35 AM

All replies

  • Hello,

    Is there a specific issue you are trying to avoid?

    /Znack
    Thursday, June 17, 2010 6:42 AM
  • Z,

         I have been out of commission until recently.  Thanks for the reply.  I have been tasked to sequence Office 2010 for POC deployment.  I have tried both of these with relative success.  However, I do have an issue and some questions. My issue is;  at the client install phase both recipes ask you to install the Deployment kit twice.  Once with the license flags and once with the proxies + Guid + OSD(s) ect.  I seem to struggle with this and never can get the command to work. The kit installs but the proxies do not work.  Whats weird is that if I use the following command during sequenceing and client install everything works fine:

    Command:

    msiexec /i OffVirt.msi ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies PROPLUS=1 PROJECTPRO=1 KMSSERVICENAME=”MY.KMS.COM” KMSSERVICEPORT=XXXX

    Have you seen this? and, am I going to run into issues by not included the package GUID or OSD info?

     

    Question #1

         The powers that be would like to create a base office deployment.  This package would included; Word, Excel and PowerPoint.  I would like to include the SharePoint workspace and Visio viewer but we will see. Anyway, the rest of the Pro Plus package would be separate virtual apps.  I have played with the Dynamic Suite Composition tool with success.  I was just looking for some advice or gotchas.  Keep in mind that I have integrated AppV with SCCM R2SP2.

       Note: One gotcha I am running into with the Dynamic Suite Composition tool is with Project 2010 Std.  When I try to create an association with V.Outlook for the insert task function it causes my V.Project app to crash.  As soon as I revert the OSD it fixes it.

    Question #2

       As I mentioned above I am looking at breaking out some apps and sequencing them as separate apps.  So far I have sequenced these separate apps following the same recipe as the base package.  I include all of the Office tools with each app and point the shortcuts to the same directory (Programs\Microsoft Office 2010\Microsoft Office 2010 tools).  Do you or someone have any experience in deploying in this way.  Or, have any suggestions?

     

    Again, thanks for the response.

     

     


    Thursday, June 24, 2010 3:38 AM
  • Hello,

    For statement one, see this hands-on example, which I advise that you read thoroughly

    http://www.softgridblog.com/?p=153

     

    #1 Recommendation is to sequence all applications (for office) into a single package using one common asset directory

    Dynamic Suite Composition does not support to add a full software installation as a secondary package and only focuses on providing support for plugins. Project, Outlook are not considered plugins.

    #2 See above, I have experiences from all types of ways and everything always depends on the requirements of the application and the reason its sequenced. Meaning, extremely customer specific.

    /Znack

    Thursday, June 24, 2010 4:35 AM
  • Good Morning,

    I will read over the doc again. Thanks,

     

    About sequencing office as one package do you mean every office product? or just what comes bundled with a pro plus.  If so, what about Visio, Project ect?  These are separate licenses and I don't want every user to have them? With that we would need to deploy them on a per user basis as separate applications.  This leads me to one of my problems Project and Visio have hooks into other office products?

     

    Thanks,

    Thursday, June 24, 2010 1:47 PM
  • Hello,


    It seems that you have a wish to be compliant with your license agreement and therefore ensure that no users that do not have a license can access those applications.

    How you perform this from a technical perspective could be several ways - I would suggest you try out wish one suites the best (you seem to have a good understanding of what methods are available).

    /Znack

    Thursday, June 24, 2010 8:41 PM
  •  

    Reading your article the Project issue makes more sense.  Thanks,

    http://blog.stealthpuppy.com/virtualisation/dynamic-suite-composition-and-short-names

    Friday, June 25, 2010 4:24 PM
  • When delivering all of the Office applications as a single package, you can control which applications users have access to by using separate groups per shortcut (when using the native deployment method).

    App-V also works with AppLocker which you can use to control access to specific applications: http://www.brianmadden.com/blogs/timmangan/archive/2009/10/28/AppV-and-AppLocker.aspx

    If you aren't yet deploying Windows 7, there are 3rd party products such as AppSense Application Manager which can do the same thing.

    Saturday, June 26, 2010 11:26 AM
    Moderator