Not that I *know* of (usually comes with a new MSIEXEC that sort of thing) ... but I wouldn't be surprised if it did ... not like Windows 10 hasn't been surprising people with "fun" stuff on all sides already.
Well - try using the MSI logging parameter ('/l <location>' if memory serves) and see what the MSI log gives you to begin with. The MSI log has gotten better over the last decade -- and even if it may not necessarily point you at "this is the thing", then at least it may point you in the right direction (say - "permissions" for instance). Gives you at least "something" to work with.
That's how I'd suggest starting off on that track. I've been installing MSI's on Win 10 so "in principle" it works. Could be something to "that MSI" (especially if it's been re-packaged) rather than "MSI's in general" potentially as well.
I will give logging a try and reply with results. Thank you!
I am having the same issue. Any resolution to this? It only affects our Windows 10 clients. Thank you.
onegoodsoul - Read the above comment I wrote & essentially follow the steps I suggested.
"Having the same issue" doesnt really provide any information here -- I suggested enabling MSI logging to see what's going wrong in the first place.
Distributing MSI's to Win-10 works just fine on my boxes, so it's not a "general problem" ... so you need to look at where / why you MSI's break and go from there. It may be something to do with us, it may not.
Maybe it's the MSI itself that's iffy, maybe there's a permissions issue or some such.
Use logging, and between our logging / the MSI logging is the starting point to make sense of what's actually happening .
The first step is in gathering information (hence - logging) to understand better. With understanding, you can then start taking action .
Hope that makes sense?
"Any resolution to this?"
It was just a simple question. Thanks.
It was - my point was that it's not a simple question or a simple answer.
Since we didn't know what wasn't working, some ground-work needed to be done. If you're having similar problems, you need to do that very ground work.
Nohing's been shared yet by those affected in regards to "oh, it was a simple case of X or Y" as can be seen in the thread, unfortunately.
MSI logging at the LD deployment package and Windows Native MSI logging by local GPO were enabled. Both resulted in no logging. Deployment in LD console is marked as successful with code 1101. However, no activity, as far as Windows Installer is logged at the client. The package I am attempting to deploy can be found here...
It is the X64 MSI for LAPS.
We are running LDMS 9.6 SP2 which has been very stable and reliable for us.
No MSI logging at all even though it was turned on ...? That's odd.
I'm assuming you've also used the "/L" swith and specified a log-file as part of the package install commands (that can always help)?
If you don't have any MSI logging, start with our logs on it -- it'll at least be a starting point.
Note that you can enable debug-logging as per here -- How to enable Xtrace Diagnostic Logging -- and I've added a copy & paste'able .REG file content for convenience in the comments.
The logs you're looking for are here -- "C:\Program Files (x86)\LANDesk\LDClient\Data\sdclient_task###.log" where ### is the Task ID (which you can see in the console and/or the DB).
If we're launching the MSI, there really should be *SOME* logging on MSI's behalf ... (again - if you don't use the specific "/L=<logfile>" switch - do so ... MSI logging without it can be ... temperamental I find at times).
If you're having issues with the download not completeing, the following items should help:
Also, feel free to run a PROCMON trace (Process Monitor from Sys Internals). That may give you an idea (and start tracking SDCLIENT and MSIEXEC) ... an introduction to ProcMon if you're not used to it can be found here -- Understanding Process Monitor - as written by the kind wcoffey as a great aid in figuring out what's "actually" going on.
That should help you on a bit .
I found this in the SDClient_Task*.log... any ideas? XTRACE is enabled.
LOG Wed, 12 Jul 2017 12:24:42 The was detected and package install will not be processed LOG Wed, 12 Jul 2017 12:24:42 RunPackageInstall: not install by detection LOG Wed, 12 Jul 2017 12:24:42 processing of package is complete, result 0 (0x00000000 - code 0)
I was able to resolve this issue.
... what was it that was tripping you up?
Sharing that kind of information can be heflpul for anyone else stumbling over similar issues .
(Glad to hear you got un-stuck)
SP3 for LANDesk 9.6 is required. It is a known issue and is somewhat detailed in the SP3 readme.