Remote software installs of MSI packages via WMI
Manfred Braun
Richard, has you stepped through the sample with the debugger??? I have no
time currently, but will give it a try later. I was always interested on
that theme.....
Best regards,
Manfred Braun
(Private)
Lange Roetterstrasse 7
D68167 Mannheim
Germany
mailto:_mbr...@manfred.mannheim-netz.de
(Remove the anti-spam-underscore to mail me!)
"Richard Mayston" <Richard...@mfat.govt.nz> wrote in message
news:erJg6mslAHA.2252@tkmsftngp05...
> I'm trying to use WMI for remote software installations of MSI packages.
> I found a code sample in MSDN, but when I run it nothing happens, no
errors,
> no install.
>
> Anyone had any luck with this sort of thing?
>
> regards,
> Richard...@mfat.govt.nz
>
>
>
Richard Mayston
No, I've never used a debugger - I know I should give it a go some time,
just found it too easy to wscript.echo here and there.
I don't know anything about all that SWbemSink stuff either!.
I suppose at worst I could always just do a remote execute, but I'd like to
use the proper facilities if possible.
It would be great if you did have a go.
Thanks,
Richard...@mfat.govt.nz
"Manfred Braun" <mbr...@manfred.mannheim-netz.de> wrote in message
news:#b0mPE6lAHA.1588@tkmsftngp05...
Andrea Cuozzo
I've played with it a bit with Visual Basic and at the end I could have it
work. I've almost no experience at scripting WMI but if you think you can
rearrange the vb code in a vbs I can send it to you by mail.
Let me know.
Bye
Andrea
"Richard Mayston" <Richard...@mfat.govt.nz> wrote in message
news:#wnjGUFmAHA.1364@tkmsftngp05...
Manfred Braun
I am interested too. Could you send it to me too? I have enough scripting
experience to make the move (even if Richard would be interested, I'll do
it).
Has someone something like a nearly-dummy MSI file? Something what be good
exactly for that test. I found never the time to get the details on MSI (but
I should...). So an experimental one, what, for sample, "install"s a batch
file (Best add-on:Don't let make this simple install a reboot - a very nice
test option)? From my more "administrators point of view", I wished even to
"install" scripts this way, because this way would enable you to solve
better all the dependency problems.
Best regards,
Manfred Braun
(Private)
Lange Roetterstrasse 7
D68167 Mannheim
Germany
mailto:_mbr...@manfred.mannheim-netz.de
(Remove the anti-spam-underscore to mail me!)
"Andrea Cuozzo" <andrea...@reti.it> wrote in message
news:uaSA9tFmAHA.1364@tkmsftngp05...
Richard Mayston
that will create a basic .MSI
regards,
Richard...@mfat.govt.nz
"Manfred Braun" <mbr...@manfred.mannheim-netz.de> wrote in message
news:OH8DYwTmAHA.1892@tkmsftngp05...
Richard Mayston
Yes thanks, maybe even post it to the group. Others may be interested.
regards,
Richard...@mfat.govt.nz
"Andrea Cuozzo" <andrea...@reti.it> wrote in message
news:uaSA9tFmAHA.1364@tkmsftngp05...
Manfred Braun
thanks so far, I'll look for it...
Regards,
Manfred
"Richard Mayston" <Richard...@mfat.govt.nz> wrote in message
news:#S#5aPimAHA.1804@tkmsftngp03...
Asle Rokstad
I've been through some of the same problems. At this point I'm able to
install using Win32_Product.Install if the .msi file is located locally at
the remote computer. If not the methods "ReturnValue" property is 1619
("This installation package could not be opened. Verify that the package
exists and that you can access it, or contact the application vendor to
verify that this is a valid Windows Installer package".)
I'm using C++ code but the same happens if I execute the Install Method from
WMI CIM Studio and fills in the parameters there.
The call fails with 1619 if the PackageLocation is eg
"\\ServerComputer\SharedCatalog\MyPackage.msi" (the share has full access to
anybody)
but works fine if PackageLocation is like "c:\temp\MyPackage.msi".
Try to run the Install method from WMI CIM Studio and have a look at the
return value. It might give you a clue.
Asle
Andrea Cuozzo
the problen with the remote share maybe that the msi service doesn't have a
way to access the network or something similar. I was able to install sw on
a remote machine from a network point setting the share as a
NullSessionShares as stated below (I'm not sure weather it was Darwin Sanoy
or DFENS to point me in that direction, but they're both terrific elements):
you have to use RegEdt32 to access this, 'cause it's a Hex value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameter
s]
"NullSessionShares"= SOFTWARE ...
unfortunately it was too much time ago so I may miss something here, but the
detailed info are on the technet, just search for NullSessionShares
remember this is a security issue because everybody will be able to access
this share
hope this can help
bye
andrea
"Asle Rokstad" <asle.r...@agresso.no> wrote in message
news:#db$5tWoAHA.948@tkmsftngp02...
Asle Rokstad
My application (a service) is running with administrator rights and
connected to remote WMI with security level set to impersonate. I thought
(hoped:-) this enabled the remote WMI service to access the network share
using the security context of the admin user, but this was not the case.
Asle
"Andrea Cuozzo" <andrea...@reti.it> wrote in message
news:OE4WxjXoAHA.2224@tkmsftngp05...
Richard Mayston
putting the MSI on the local machine first, it still doesn't install. I wish
Microsoft would give us a working vbscript example.
Thanks for trying.
regards, Richard...@mfat.govt.nz
"Andrea Cuozzo" <andrea...@reti.it> wrote in message
news:OE4WxjXoAHA.2224@tkmsftngp05...
Asle Rokstad
(thanks to Andrea pointing me in that direction), and now it works. I
haven't tried the script samples though...
Have you tried to invoke the method using WMI CIM Studio? This should give
you a return value that you can look up in MSDN or the Win32 errors code
list.
Asle
"Richard Mayston" <Richard...@mfat.govt.nz> wrote in message
news:OUQZcYqoAHA.1092@tkmsftngp03...