neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
neo said:Difficult to answer because you don't mention if this AIP is on a DFS or
Cluster volume. It would also help if you mentioned if Office was
installed by using setup.exe or calling the MSI directly (e.g. msiexec /i
pro11.msi transform=....).
To give an example of why it is difficult is this...
Case 1) AIP but all clients received software by using setup.exe - Assuming
default behavior where the setup files are not removed at the end, users
should have a local install source (LIS) that allows for a more seamless
detect/repair, patching, and add/remove program features to occour.
Case 2) AIP but all clients received software by calling pro11.msi
directly - clients will not have the LIS therefore making detect/repair,
patching, add/remove program features more difficult because the registry
will contain an entry to the original distribution point. Of course this
could be mitigated if DFS or Cluster volumes where originally used.
Sandy Wood said:Neo,
My AIP is more like your example number 2. We installed from a plan old
share using the .msi file. We're doing all our updates to client machines
by
refreshing the installation from that AIP also.
My question at this point is how to make the clients think the 'original'
AIP is really the new one I'm moving things to. I've thought I could just
edit the Install registry key on each client - that may fix it. Or I could
simply re-install the whole install from the new server.
I'm interested in your thoughts.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.