post task bigger than 1.5g why it creates another ID when imported?

Hi All

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.

any ideas?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: cserrins 1 year ago
Red Belt

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.

  • oh wow..ok much easier :)
    thanks - psaussey 1 year ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ