salmageo

I am setting up ADR for MS patch Tuesdays, and have a question concerning the process and how best to minimize disk space for updates. I have a need for targeting PILOT collection first, and then PRODUCTION, once the PILOT is successful. Currently I have the following: For the PILOT collection:: Create the ADR Target a collection - in this case pilot Deployment package is selected for example XXXX Package source path is \\YYYY ADR runs on a schedule and creates a new SUG The deployment is enabled after the rule is run Deployment Schedule is X For the PRODUCTION collection: Create the ADR Target a collection - in this case production Deployment package is selected for example ZZZZ Package source path is \\WWWW ADR runs on a schedule and creates a new SUG The deployment is enabled after the rule is run Deployment schedule is X+5 days My question is can I share the Deployment Package between PILOT and PRODUCTION ADRs [e.g. XXXX] and therefore share the package source [e.g. \\YYYY]? This may be a silly question but want to ensure I can piggyback in this way, as running the ADRs separately into distinct package source paths duplicates the download file content. Appreciate your assistance,