post task bigger than 1.5g why it creates another ID when imported?
I followed the instructions to create a post task install bigger than 1.5g. It use to work no problem, now when I import the package it shows as another task ID in the post install task so the deploy cant find the file.
ex: \\k2box\restore, i have a PO673 then in the task ID it shows as 674.
I deleted the fake task prior to importing.
Importing a task will also bring it in with a new ID#. However, if we are talking about the SDA, there is no longer a need to do it this way if you are on the latest version. The SDA has a share named "clientdrop", if you connect to that, and copy in your large file, then when you create the task, there is an option to select a file from the SDA client drop. Just select that and it will work just fine. Once the new task is created and tested, you can delete the file from clientdrop.