Active Setup\Repair if source is no longer on c:
Hi,
The company I work for use AD deployment. The MSI is copied to a temp folder on c:, installed, then the source is deleted.
If it's a computer assigned MSI (that has HKCU or appdata files), when a user logs on, active setup runs, it fails to repair as it no longer has access to the source.
I know there is a cut down version of the MSI in c:\windows\installer, but can the app repair if it requires files? I would have thought the MSI would have to remain in the source that it was installed from for a full repair to be successful?
Is this correct?
Thanks...
The company I work for use AD deployment. The MSI is copied to a temp folder on c:, installed, then the source is deleted.
If it's a computer assigned MSI (that has HKCU or appdata files), when a user logs on, active setup runs, it fails to repair as it no longer has access to the source.
I know there is a cut down version of the MSI in c:\windows\installer, but can the app repair if it requires files? I would have thought the MSI would have to remain in the source that it was installed from for a full repair to be successful?
Is this correct?
Thanks...
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
12 years ago
The company I work for use AD deployment. The MSI is copied to a temp folder on c:, installed, then the source is deleted.Er...why? GP deployment implies a network which implies server-based shares so why not simply install directly from there?
can the app repair if it requires files?In a word, no.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.