Office 2003 Local Installation Source

[Osceolakid]

The server folder name was changed that is used for this application's
installation. I know source paths are important for Administrative shares and
I know with Office 2003 LIS installed on pcs that they will self-heal.

However, what I was wondering is if the LIS cache gets corrupted on Local PC
will it look for the installation source path on server which is now changed
and have a box pop-up to point to a new source path like the Admninshare
version does? If so I hear there is a Visual Basic program that will let you
change source paths and add source paths can this be used to fix the LIS
installations?

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[neo [mvp outlook]]

Assuming that Office 2003 was installed with the setup executable, the setup
files where not deleted at the end, and the site didn't get to carried away
about adding setup paths in the CIW/MST, then there should be no reference
to source media (e.g. CD or network path).

To work with the LIS, use the LIS Tool from Microsoft.
http://office.microsoft.com/en-au/assistance/ha011402361033.aspx

/neo

ps - the only thing that i am aware of that can damage the LIS is Windows
XP's cleanup wizard that runs every 60 days. (I always advise disabling it
in corporate environments.)

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.

 

[Osceolakid]

used the setupstd.exe, In the MST generated no source paths where inputed
into CIW during MST creation. I didn't script to delete setup files so to
recap what your saying with all conditions you stipulated met. There will be
no source path no network or CD. So if the files in msocache get corrupted
the resolution is to reinstall this office package again....however the
likehood of corruption of msocache on local PC should be finite on a properly
managed network.