LIS and Admin Installs

[John P.]

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?

 

[Susan Ramlet]

Hi, John P.

You cannot use a local installation source (even generated after the fact
with the LISTOOL) if you originally deployed Office from an uncompressed
administrative image. The admin image is a different kind of install, from
uncompressed files, where a CD installation (and LIS-capable one) is from
compressed cab files, which the LIS uses.

See this for more information:

Microsoft Office Assistance: Change the Local Installation Source After the
Installation:
http://office.microsoft.com/en-us/assistance/HA011402361033.aspx


--
Susan Ramlet
MVP - Office

Please reply to the newsgroups where others may benefit.

Our company would like to convert our Microsoft Office 2003 installations on
clients' desktops from an ADMIN installation to using the LIS installation
model. However, after reading some article out on Microsoft's site, that we
will have to uninstall the current installation on client's machine before
using the LIS installation. Could we use the LISTOOL to create the hidden
folder with cab files and redirect the package code source file location for
self-healing and feature installs? I would like to not impact the client of
going through the pain of uninstalls/reinstalls. Is there a way around

this?