Re: How to integrate/slipstream Office 2007 Beta2 TR1 into source.
- From: "Bob Buckland ?:-\)" <75214.226(At Beautiful Downtown)compuserve.com>
- Date: Sat, 16 Sep 2006 18:25:23 -0700
Hi Pawan,
I'm not sure I'm clear on what the differentiation you're is that you're looking for in this case. Are you looking to make updating
quicker, or simpler or ???
The 'old way' (Office XP and Office 2003) of doing a slipstream for Office was to patch the Office Admin Point then recaching
(reinstalling) the Office installation from the Office Admin Point to include the updates.
That was no longer MS's recommended 'first choice' method for updating for Office 2003 ( http://microsoft.com/office/ork/2003 ) for
several reasons.
With the \Updates folder use in Office 2007 to chain an update patch (that's also how you apply customization files, by using .msp
patch files on an Office 2007 deployment). When you apply a product patch using the MS Installer, your MSOCache folder stays
unchanged with the .MSP patches cached as \Windows\Installer content. I'm not sure that this is going to lessen or increase the
support requests (vs storing the patches in a folder under MSOCache)
Running setup using the \Updates folder can still be a 'one run' action and the Office setup program helps insure that only updates
needed for a particular user configuration are applied as part of setup. The nice thing on this one is that almost anyone can learn
that method. Slipstream creation/testing reconfiguring can get to be a tricky proposition and hard to troubleshoot at a later point
(and often the problems didn't show up until the 'next update' came out and then it was 'why is this not working' <g>)
Additionally, you can also do an \MSOCache 'pre run' when setting up your Office 2007 deployments, so that when you later run the
'real' setup basically the network load would be less and you'd be pulling your product from the local \MSOCache area and pushing
only the customizations and patches from the Office Network Installation Point (oNIP). That should (unless someone uses a 3rd party
tool or just 'deletes to make space) allow folks to travel or fix Office installations or even update them without needing to search
for their Office CDs (provided that the install is 'healthy' at the time of applying an update.
If you're going to do a 'single run' slipstream you'd need to create a hard disk image and that is covered.
Reimaging or using VPCs is becoming a more common way of updating, keeping the user customizations in a different drive or area.
Another feature of Office 2007 is that you only need a single MS Office Network Point (oNIP) even if you have multiple Office
products to be managed. With Office 2000 through Office 2003 you should have had a separate Office Admin Point for each product and
that could get pretty messy trying to keep things in synch.
No Office 2007 product SKU is a single .MSI file, so you could look at even a basic setup as either a 'merging' or 'chaining' even
without updates.
Bob Buckland ?:-)
==========
<<"Pawan" <Pawan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:69C57411-6CDA-4ACC-9223-3F6D5E4E0ED3@xxxxxxxxxxxxxxxx
Thnaks Patric & Bob for reply,
Bob your suggestion is good, but by that way it will install the update
after Beta 2 Setup as it says: (When you obtain Office updates from
Microsoft, simply copy them into the Updates folder in the root of your
network installation point) thats not the integration.
I want integration/slipstream as we did with previous versions of office.
Pawan >>
.
- References:
- Re: How to integrate/slipstream Office 2007 Beta2 TR1 into source.
- From: Bob Buckland ?:-\)
- Re: How to integrate/slipstream Office 2007 Beta2 TR1 into source.
- Prev by Date: Re: Outlook 2007 B2TR Send/Receive against Exchange 2K3 never complete
- Next by Date: Re: problem with open XML file on startup following TR installation
- Previous by thread: Re: How to integrate/slipstream Office 2007 Beta2 TR1 into source.
- Next by thread: Re: no option for keyboard shortcuts to insert symbols in office 2003
- Index(es):
Relevant Pages
|
