assign msi to computer problem
hey all,
Here's the problem:
i created an msi package. I want to assign that msi to workstations in a certain OU. The installation fails everytime. Error: "
Event ID: 102
User: NT AUTHORITY\SYSTEM
Computer: THINKCENTRE2
Description:
The install of application SBClient524 from policy sbclient failed. The error was The installation source for this product is not available. Verify that the source exists and that you can access it. . "
Now, the tricky part is that im sure the path is correct: "\\nas\public\packages\product\sbclient542.msi"
If i type in that address in the workstation's explorer, it will take me to the correct folder/file.
Moreover, if i assign the same msi file to 'user' as opposed to 'computer' fotr that OU, the installation works like a charm.
TIA for all your help,
Adam
Here's the problem:
i created an msi package. I want to assign that msi to workstations in a certain OU. The installation fails everytime. Error: "
Event ID: 102
User: NT AUTHORITY\SYSTEM
Computer: THINKCENTRE2
Description:
The install of application SBClient524 from policy sbclient failed. The error was The installation source for this product is not available. Verify that the source exists and that you can access it. . "
Now, the tricky part is that im sure the path is correct: "\\nas\public\packages\product\sbclient542.msi"
If i type in that address in the workstation's explorer, it will take me to the correct folder/file.
Moreover, if i assign the same msi file to 'user' as opposed to 'computer' fotr that OU, the installation works like a charm.
TIA for all your help,
Adam
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
kkaminsk
20 years ago
User: NT AUTHORITY\SYSTEM
If this is the account installing the MSI it will have no network rights. You either have to set up a null session share on the server which is a security risk or use a different account to install the MSI.
If this is the account installing the MSI it will have no network rights. You either have to set up a null session share on the server which is a security risk or use a different account to install the MSI.
Posted by:
sawczukx
20 years ago
Thanks kkaminsk...
Can ya tell me how can i use a different account to install an msi?
Thanks
~a
Can ya tell me how can i use a different account to install an msi?
Thanks
~a
Posted by:
cdupuis
20 years ago
If you want to call it from a script then you can use the runas command.
Posted by:
plourenco
20 years ago
Hi,
Is it the only software that gets this error message when assign it to a workstation?
Is it the only software that gets this error message when assign it to a workstation?
Posted by:
kirkpatrick
20 years ago
Hi!
I had the same thing.
I was working on a contract and accepted the location for the MSI repository as given to me.
Turns out it was on a NT4 Server (member server) in an AD Domain (mixed mode)
What OS is the server that is hosting the packages share?
NT will not provide Kerberos Authentication to the workstation thereby making application installation of an assigned nature impossible.
Hope that helps!
Mike
I had the same thing.
I was working on a contract and accepted the location for the MSI repository as given to me.
Turns out it was on a NT4 Server (member server) in an AD Domain (mixed mode)
What OS is the server that is hosting the packages share?
NT will not provide Kerberos Authentication to the workstation thereby making application installation of an assigned nature impossible.
Hope that helps!
Mike
Posted by:
peart75
20 years ago
in addition to what kirkpatrick is saying, the same is true if the install files reside on a clustered share. i read up on a "fix" for the clustered share issue but it seemed really involved and risky.
-drew
-drew
Posted by:
kkaminsk
20 years ago
Can ya tell me how can i use a different account to install an msi?
Thanks
Well I missed this one by a long time but here are some suggestions. If you want to use a different account you would have to publish the MSI to a user instead of a machine. That is what I am assuming by looking at the eventlog entry.
Also I got a 102 error when I installed a per machine install of a Canon driver that used InstallShield Script V7. The MSI could not make a successful DCOM call to the InstallShield Script Driver. So I guess in short turn on all the MSI logging so that you might see the real reason the 102 error is happening.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.