P
Pawan
Is there a way to slipstream/integrate Office 2007 Beta2 TR1 into Office 2007
Beta 2 source?
Beta 2 source?
P
Patrick Schmid
I don't know if Microsoft has made those instructions available yet to
the public. Check back in a few days.
Patrick Schmid
the public. Check back in a few days.
Patrick Schmid
B
Bob Buckland ?:-\)
Hi Pawan,
The MS Office 2007 Resource Kit (Beta) is on MS Technet. The basic slipstream process (use of the \Updates folder) is described
here
http://technet2.microsoft.com/Office/en-us/library/5e62ead2-5d6a-41ab-93d2-b902460f2d2d1033.mspx
along with a method for creating a hard disk image.
If you don't have Office 2007 Beta 2 on a CD then you'll need to use the /extract switch on the Office 2007 Pro download file to
extract the contents to an Office 2007 CD Image (aka an Office Network Installation Point (oNIP).
=============
Is there a way to slipstream/integrate Office 2007 Beta2 TR1 into Office 2007 Beta 2 source? >>
--
I hope this helped you,
Bob Buckland ?
MS Office system products MVP
LINKS to the 2007 Office System
1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress
2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview
3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/
4. Try the 2007 OfficeOnline preview website , without Office2007
a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033
b. then visit
http://officebeta.iponet.net
The MS Office 2007 Resource Kit (Beta) is on MS Technet. The basic slipstream process (use of the \Updates folder) is described
here
http://technet2.microsoft.com/Office/en-us/library/5e62ead2-5d6a-41ab-93d2-b902460f2d2d1033.mspx
along with a method for creating a hard disk image.
If you don't have Office 2007 Beta 2 on a CD then you'll need to use the /extract switch on the Office 2007 Pro download file to
extract the contents to an Office 2007 CD Image (aka an Office Network Installation Point (oNIP).
=============
Is there a way to slipstream/integrate Office 2007 Beta2 TR1 into Office 2007 Beta 2 source? >>
--
I hope this helped you,
Bob Buckland ?
MS Office system products MVP
LINKS to the 2007 Office System
1. Free MS Office 2007 book from MS Press, 213 pages:
http://microsoft.com/learning/office2007/default.mspx#booksfrommspress
2.. Office 2007 Beta 2 Online Test Drive, Downloadable beta,
e-learning courses, doucmentation and movies:
http://microsoft.com/office/preview
3. Send 2007 Office System Beta 2 feedback directly to the MS Office 2007 product team with this feedback tool:
http://sas.office.microsoft.com/
4. Try the 2007 OfficeOnline preview website , without Office2007
a. Install the ActiveX access control
http://office.microsoft.com/search/redir.aspx?AssetID=XT101650581033
b. then visit
http://officebeta.iponet.net
P
Pawan
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
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
B
Bob Buckland ?:-\)
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 ?
==========
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 >>
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 ?
==========
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 >>
P
Pawan
HI Bob,
Thanks for reply.
I want to make things quicker, simpler and smaller. If I put the update
patch in update folder the size will be double and it will take more time
becasue at first the setup will start and the update patch will start only
after the setup completed. And if I want to install Office 2007 on multiple
PCs or multiple times on single PC then it would take a lot of time.
In Office 2003 there is an option to slipstream Sp1/Sp2 in the source itself
and thats take smaller space though the source size increases from 400+ MB to
600+ MB but installing it on multiple pc or a single pc for multiple times
becomes very easy. Other wise every time when I format my system, I have to
install office first then update and then other update.
The patch should be slipstreamable.
Pawan
Thanks for reply.
I want to make things quicker, simpler and smaller. If I put the update
patch in update folder the size will be double and it will take more time
becasue at first the setup will start and the update patch will start only
after the setup completed. And if I want to install Office 2007 on multiple
PCs or multiple times on single PC then it would take a lot of time.
In Office 2003 there is an option to slipstream Sp1/Sp2 in the source itself
and thats take smaller space though the source size increases from 400+ MB to
600+ MB but installing it on multiple pc or a single pc for multiple times
becomes very easy. Other wise every time when I format my system, I have to
install office first then update and then other update
.The patch should be slipstreamable.
Pawan