Web Package Tasks - Tips & Tricks

Deploying Tasks to Computers

The information in this article applies to Prism Deploy 16.0 and above.

Prism Deploy has always been able to deploy Packages from a web address. With Prism 16.0, we’ve improved this capability in two ways:

  • There is now a Web Package Task wizard to help you create the correct syntax for the Task.
  • The credentials you specify to access the Web Package (if necessary) are more secure. Once the Task is created, the password is hidden in the Console and encrypted in the channel database. It is not exposed in the client log file.

One of the most common ways that Prism Deploy customers use Package Tasks is to stage the payload for subsequent Tasks locally on the target PCs. For example, when installing large and/or complex software, Prism administrators manually create a Package that contains the scripts, setup files, folders and other source files necessary for the software installation. They deploy the staging Package and then follow up with a separate Task (MSI, Command or Script Task) to kick off the installation using the locally-staged files. With Web Package Tasks, Prism administrators have another option for supporting off-network PCs.

Here are some tips for getting the right URL syntax for Prism's Web Package Tasks.

Internet-facing web server: The syntax would look like this (or http://).

When deploying from cloud storage sites such as Dropbox or OneDrive, there are some extra steps for getting a correctly formatted URL to use in the Web Package Task.

Dropbox: By default, files shared through Dropbox URLs are for viewing, not for download. A typical Dropbox URL looks like this: To convert the URL to a downloadable one, simply replace the 0 at the end to 1 (…dl=1).

OneDrive: OneDrive URLs also need to be changed before being used for Web Package Tasks. By default, OneDrive URLs are shortened. They first need to be expanded, then converted into a direct download URL. To illustrate, here’s an original (shortened) OneDrive URL to a Prism Package:!AtUhQlsHZZrxi2DHgs8jhmaQyFHe
If it was deployed as a Web Package Task in it’s shortened format, it would fail with error 4400, “unexpected Internet error.”

To expand the URL, use one of these free sites:

Here’s the expanded URL:!1504&authkey=!AMeCzyOGZpDIUd4
This URL isn’t ready to use for a Web Package Task because it needs to be converted to a direct download link.

To get the direct download URL, use one of these direct link generators:

You now have a direct download link that works for the Web Package Task. Here’s the final URL:

Google Drive: Shared URLs from Google Drive are not supported at this time.

Also In This Category

On a scale of 1-5, please rate the helpfulness of this article

Not Helpful
Very Helpful
Optionally provide your comments to help us improve this article...

Thank you for your feedback!

Add Your Comments
Email Address:
RadEditor - HTML WYSIWYG Editor. MS Word-like content editing experience thanks to a rich set of formatting tools, dropdowns, dialogs, system modules and built-in spell-check.
RadEditor's components - toolbar, content area, modes and modules
Toolbar's wrapper  
Content area wrapper
RadEditor's bottom area: Design, Html and Preview modes, Statistics module and resize handle.
It contains RadEditor's Modes/views (HTML, Design and Preview), Statistics and Resizer
Editor Mode buttonsStatistics moduleEditor resizer
RadEditor's Modules - special tools used to provide extra information such as Tag Inspector, Real Time HTML Viewer, Tag Properties and other.
Verification Code:
Last Modified: 7 Years Ago
Last Modified By: Pam
Type: INFO
Level: Intermediate
Article not rated yet.
Article has been viewed 4.5K times.
Customer Support Software By InstantKB 2015-2
Execution: 0.000. 15 queries. Compression Disabled.