... have a look at the SDCLIENT logs - if files get downloaded, policy-side everything should be fine, so you'll likely have to look there.
The following links / reading material should help:
The client-side SDCLIENT_TASK### log (under LDCLIENT\DATA\ ) should hold information on what's actually going on. You can make this more verbose if needed (see further below).
Useful to have, but don't think this'll apply in your situation
You can also enable debug-logging (which will make the logs A LOT chattier) ... work your way from the bottom up, since you'll not care much about the stuff that will work . How to enable debug logging? That's mentioned here:
... I've included a "copy and paste" importable registry thing in my response to this article here (I'm assuming you're running a 64-bit client):
NOTE - you may also want to enable package-internal logging - so if it's an MSI, make sure you use the flag to write out the MSI log. That may hold useful information too!
Hope that helps!
Were you able to get this working? We want to make sure you were taken care of.
I was not able to get this working and I had the same problem. The files copy but the installer fails.
Did you have a look through the logs / enable the debug stuff I've linked to?
If need be, you can try to work it through with support (they may request a copy of the package in question, to duplicate / debug locally potentially). At the very least, the installer should start up.