Couple of things that should help you along here are included below:
...the above deployment guide actually uses Firefox as a specific example, which should help you .
The HTTP 404 error code generally would indicate that the file couldn't be found on the server, so maybe something's off with your HTTP share? If you need help on how to set up HTTP shares, the following should help you:
... that should get you started, hopefully?
Thank you for answer.
So I will read, learn and try your tipps.
I give answer if it works or even if it not works.
But I am hopefull, that it works. :-)
No worries - if you get stuck, let us know.
The above articles are hopefully enough to get you going, as they're exactly for the "I'm new to this" scenario of things .
now I know the answer for the error 404. The filextension for DMG and PKG are unknown on the IIS.
Actualy the extensions are known, but the PKG-Extensons are invisible.
At the end I made a build for Firefox ( e.g. pkgbuild ) and I made a new task. The task works, but the client does nothing. Actually the task is active, the returncode is 1354, thats all.
I hope, that the task is succesfully until tomorow.
it´s really terrible! After numberless tryings, now it works. Hurray!
I had to do a new method of allocation and then the Landesk Manager says Success.
Many thanks for your help
Heyas - glad to hear that things worked out (and sorry - was out on the road for a longer bit).
I'll mark the thread as assumed answered in that case.
Happy packaging going forward (careful - it *IS* a bit of an art form, not matter which platform - and there's a good reason that there's folks doing this stuff professionally). There's a big difference between "random, over-busy IT-guy" building a software package & some folks who "know how to do it properly" doing it.
I still have nightmares about a (granted - Windows - but it makes the point all the same) case where I had an MSI wrapped around an EXE, wrapped around an MSI, which used command-line parameters for MSI that didn't exist, had 0 documentation, and everyone was afraid of even touching (as it was 10+ years old, and of course no one knew anything about it) ... so yeah ... "fun" can be had with that sort of thing.
"Artform" is correct. For Mac apps I generally find that simply packaging the .app as a .zip file then deploying that works. For some other apps, I will put the .app into a folder, then use Disk Utility to convert that folder into a .dmg archive. It all "depends."