B
Bill Bradley
I want to try and setup an SCCM (SP1) Tash Sequence for the install of Office
2007 Enterprise Pro + VISIO + Project. All I could find on this subject was
to make sure everything is set to install silently and to suppress any
messages and completion message.
Our previous method of deploying this same thing, was a rather complex SMS
Installer package. One of the issues we ran into with that method was, if
the user had already installed any of the components already (suite or VISIO
or Project), the install might halt. Is there something I need to do to
insure that if a Task Sequence installation encounters an existing install
(not always done by SMS or SCCM, could have been manual) of one of the
components, that it's smart enough to just "refresh" or reinstall or skip,
but, CONTINUE?
Other than this issue, any tips or tricks for using a Task Sequence to do
this? It seems from what I've read, that a Task Sequence is more reliable
than either using the Office Linked Install mechanism or SCCM's linked
programs?
Thanks!
2007 Enterprise Pro + VISIO + Project. All I could find on this subject was
to make sure everything is set to install silently and to suppress any
messages and completion message.
Our previous method of deploying this same thing, was a rather complex SMS
Installer package. One of the issues we ran into with that method was, if
the user had already installed any of the components already (suite or VISIO
or Project), the install might halt. Is there something I need to do to
insure that if a Task Sequence installation encounters an existing install
(not always done by SMS or SCCM, could have been manual) of one of the
components, that it's smart enough to just "refresh" or reinstall or skip,
but, CONTINUE?
Other than this issue, any tips or tricks for using a Task Sequence to do
this? It seems from what I've read, that a Task Sequence is more reliable
than either using the Office Linked Install mechanism or SCCM's linked
programs?
Thanks!