Administrative installations
Hi all,
Let's say you store an MSI on a network location without performing an administrative installation. What is the effect on target machines when they install from the MSI? Is it the same as if the install were done from an adminitrative image? Are there any disadvantages? The SDK is not very clear in explaining this, nor does it say 'Always use an administrative image when the source is on a network share'.
Thanks!
Pudge
Let's say you store an MSI on a network location without performing an administrative installation. What is the effect on target machines when they install from the MSI? Is it the same as if the install were done from an adminitrative image? Are there any disadvantages? The SDK is not very clear in explaining this, nor does it say 'Always use an administrative image when the source is on a network share'.
Thanks!
Pudge
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
WiseUser
18 years ago
Hello PudgeRok,
The main disadvantage occurs during file repairs. If a repair is triggered and a file is required for that repair, the client will have to download the whole package including every single file (albeit compressed). So it might download gigabytes when it only needs a tiny file.
There may also be implications regarding subsequent patching. This is especially true for certain MS products such as Office 2003. Check this page for detailed information:
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
The main disadvantage occurs during file repairs. If a repair is triggered and a file is required for that repair, the client will have to download the whole package including every single file (albeit compressed). So it might download gigabytes when it only needs a tiny file.
There may also be implications regarding subsequent patching. This is especially true for certain MS products such as Office 2003. Check this page for detailed information:
http://office.microsoft.com/en-us/assistance/HA011402381033.aspx
Posted by:
Satin
18 years ago
An admin point is a better options when the patch/hotfix keep coming up for the package. Just apply the patch to the admin point without managing the n number of msi that keep on coming as patch. Any further installations will get the latest files.
Posted by:
WiseUser
18 years ago
Unfortunately, life isn't that simple.
You have to be careful that your admin point doesn't become out of sync with your clients. Once you have updated the admin point, the source files can no longer be used to repair a client until you have done a reinstall and recached the msi on the client.
It is often better to create a second admin image and repair from that one. The original source can be deleted once every client has been reinstalled from the new source (REINSTALL=ALL REINSTALLMODE=vomus).
You have to be careful that your admin point doesn't become out of sync with your clients. Once you have updated the admin point, the source files can no longer be used to repair a client until you have done a reinstall and recached the msi on the client.
It is often better to create a second admin image and repair from that one. The original source can be deleted once every client has been reinstalled from the new source (REINSTALL=ALL REINSTALLMODE=vomus).
Posted by:
PudgeRok
18 years ago
Thanks so much for the responses! It's unfortunate that this isn't explicitly stated in the SDK in clear, concise language. I'm printing your responses for archival :)
Pudge
Pudge
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.