capturing a referral system from a remote location

Question

I would like to understand what is the best solution to capture a reference system that is located in a remote location compared to the sccm site.
What we would like to do is capture a remote location reference system, causing the .wim file to be saved to a network share located in the remote location. This first part we've already done, with a TS capture.

The following phase we have not performed it yet because we have some doubts.
Then, later from the central console, by running the "Add Operating System Image" of the .wim file that is in the remote location share, the .wim file is transferred to the central site anyway? Or this stage, import only the information of the .wim file ?
Then the next step would be to distribute the content only in the Distribution Point of that remote location.

We would like to avoid an exaggerated data transfer.

In the "Add Operating System Image" phase, does the .wim file remain on the remote network share, or is it still transferred to headquarters?

Note: The remote location is connected with VPN to the central site.

Answer 1

Hi,

Thank you for coming Microsoft Q&A forum.

1.==>In the "Add Operating System Image" phase, does the .wim file remain on the remote network share, or is it still transferred to headquarters?
The .wim file on the remote network share will be transferred to headquarters via VPN, unless there is a primary site on the remote location that can manipulate the content individually.

When we create a new package from the administrator console that hasn't been distributed to any DPs yet:
If there is only Distribution Point or Secondary site on the remote location, after the administrator creates the package in the console on local primary site, it will transfer not only the metadata information of the .wim file but also all the .wim package content to the content library on the local Primary site server. So in the "Add Operating System Image" phase, the .wim file on the remote network share will be transferred to headquarters via VPN. All the package content must be add to the content library on the Primary site server before we can do relevant content action, such as distribute, update or redistribute.

2.After the .wim package is created completely, we can then distribute the content to distribution points by the Distribute Content wizard in the Configuration Manager console. This will transfer all files in a package to the target distribution points, excluding those which are already present in the content library of the DP as part of another package.

For more information about content library and content distribution, please refer to:
Package actions in content distribution

Thanks for your time.

Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.