Dropbox has recently made a change to their service and temporarily blocked our ability to verify the acceptability of the link. This link, however, will continue to work if the policy was previously created, or a verifiable link from another source is substituted during the policy creation process. This article will walk through the process of creating a policy with a verifiable link from another source and manually editing the XML to use the DropBox link.
Create the policy to be used as a template
Under either Computer or User Configuration, expand "PolicyPak -> App Delivery & Patching Pak" and select "Remote Work Delivery Manager"
On the "Specify the copy source" page, paste in a working link. If you do not have one, this link below can be used. https://z_deleteme.s3.amazonaws.com/7z.msi
On the "Specify the Copy Destination" page, enter in the directory to copy the file to and set the file name as it should be for the destination file.
In this next step we need to grab the XML and manually update it with the correct DropBox link
Export to XML
Find the option "<rd:source url=xxx" and replace the value with the correct DropBox link.
Note: by default, when you create a DropBox link it ends with [dl=0]. If it does, it must be changed it to [dl=1] to work. This would normally be done by the application automatically.
If needed alter any other sections that are required that were not previously configured within PolicyPak (e.g. destination, afterApply (post-copy action) or beforeRevert (revert action), then save the file
If importing back into the same server as the originating template, and the policy still exists, on the policy line (usually line 2), find "id" and change at least one of the characters, any one of them will do. PolicyPak will not allow the policy to be imported if a policy already exists with the same ID.
The XML can now be imported into your environment – Back into GPO land where it was created, added to an MSI for MDM distribution or imported into the PolicyPak Cloud – through the regular means.
Please note: This policy cannot be altered by either of the Administrative Consoles (On-premise or Cloud). Any changes must be done manually to the XML and re-imported as detailed above.