Office2003 Local Install Source and Updates

[Troy S]

Hi all

Just a couple of quick questions but will save me tons of time having to go
through the process of testing it myself if anyone has been down this track
already.

I'm about to create a Compressed CD Image on the Network and I wish to
slipstream SP1 on the Image does anyone know where the documentation is for
that? Has anyone got a KB Number? I can't seem to find it.

Last question, using the Entsetup.exe for this Compressed CD Image and
enforcing the Local Install Source, will users be able to install client
updates to Office2003 if they are NOT an administrator on their system
(WinXPSP2Pro). I'd like to make I can simply send them a URL to run the
update...

Thanks for any help...

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[GMan Slater]

Troy,
The term slipstreaming really isn't correct for Office 2003, if used in
the same manner as when someone talks of 'Slipstreaming' Windows XP SP2.
Yes an admin install of Office 2003 can be patched with SP1, but this is
really not slipstreaming as the admin install is "uncompressed". That is not
what you want as you state you will be using the 'Compressed CD Image'
method. There is no way to 'slipstrean' SP1 into the compressed files. Since
you are doing a 'Compressed CD Image' you will need to chain the SP1
installation in the Setup.ini file. Look at:

http://www.microsoft.com/office/ork/2003/five/ch18/MntA01.htm

but note that there are lots of errors in the Office 2003 ORK text. One such
error is when using msiexec direct instead of using the oHotfix util, the
syntax given is incorrect. See my post here:

http://www.tech-archive.net/Archive/Office/microsoft.public.office.setup/2004-05/0607.html

(or better my reply to my own post there)

Installing patches requires rights to do so. I am using SMS to push out
updates.

GMan

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[Troy S]

Thanks Gman for your detailed info and other 'heads-up' info too - very
helpful.

I think I'm in the same boat as some other folk in trying to evaluate which
deployment method will best be suited for our situation.

The 2003ORKs helpfile as you say has a number of errors and I found it isn't
much help at all -
For instance in OXP if you created a customised version, Enterprises needed
to add two switches in the Modify Setup Properties - ENTERPRISE_IMAGE TRUE
and NOUSERNAME TRUE. I haven't found documentation if this is still true in
O2K3.

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

At the same time I can then ensure the latest patches are current to date.
With WUS becoming available soon (I 'm also presuming that WUS will allow
updates to AdminPoint installed Office products), this should be the easiest
solution to update the Office products.

Thanks again for your input. (Sorry that this is long-winded but I thought
this may be helpful for those browsing for solutions and that it may help
their thinking process).

Kind regards
Troy S

 

[GMan Slater]

Taking into consideration your details below and our methodology I'm leaning
toward using an Admin Point again but use the ENTSetup.exe in the AP. I'm
presuming this will work as I hope so that I can still create the Local
Installation Source option and disable users from removing the cached files.
Then I plan to Image the build and rollout the image using Ghost.

No you can not create the Local Insallation Source (LIS) when installing
from an Administrative Installation Point (AIP). If you want an LIS you
must install from the Compressed CD Image (CCI). And in doing so, if you
want HFs or SPs at the same time then you must chain them. I did AIPs with
O2K and OXP, but no longer. Despite its occasional problems (I've seen some
patches - like KB828041 - that when they are aborted/fail, remove more
files than they are suposed too and hose the LIS), I am going the CCI route
for my installs.

If you do go the AIP route, then make sure to set the MSINODISABLEMEDIA
property to 1 on the setup command line or in the Setup.ini file so that an
alternate source can be used.