Windows Windows Server

Copy Deployment Share between Servers without using linked Deployment Shares


The Microsoft Deployment Toolkit (MDT) is for Windows operating system deployment. It is a free tool for automating Windows and Windows Server operating system deployment, leveraging the Windows Assessment and Deployment Kit (ADK) for Windows 10. In this article, I will show you how to copy Deployment Share between Servers without using linked Deployment Shares. Here are some related articles: How to remove an MDT Deployment Share, how o fix Error Code: 0x80070035: MDT unable to access the Log share, the Network Path was not found, learn about the differences between MDT and WDS, how to fix MDT Warning: Unable to set the working directory, the application returned an unexpected code 2.

Note: MDT performs deployments using the Lite Touch Installation (LTI), Zero Touch Installation (ZTI), and User-Driven Installation (UDI) deployment methods. But MDT uses the LTI deployments only. While ZTI and UDI deployments are performed using MDT with Microsoft System Center Configuration Manager.

Deployment shares

A deployment share is essentially a folder on the server that is shared and contains all the setup files and scripts needed for the deployment solution. Please learn how Associate SSH Public key with Azure Linux VM, How to create an AMI using AWS console, How to install ENA Driver on Amazon EC2 Windows instance, how to copy and paste between a host machine and VirtualBox VM, and how to configure WatchGuard WebCenter

Why copy Deployment Share without using the Linked Deployment Share?

Copying a deployment share between servers without using the “Linked deployment shares can be necessary for certain scenarios where linked deployment shares are not desirable. Here are a few reasons why you might choose to copy a deployment share instead:

  1. Redundancy and Backup: Having a copy of the deployment share on another server provides redundancy and serves as a backup. If the original server fails or experiences issues, you can switch to the copied deployment share to ensure continuous operation.
  2. Independent Configuration: Copying a deployment share allows you to maintain an independent configuration on the destination server. This can be useful if you want to have different settings, customizations, or modifications on the target server
  3. Isolation and Security: Copying the deployment share can isolate the deployment process and content from other servers or networks. This enhances security by keeping the MDT server contained within a specific server or network segment.
  4. Geographical Distribution: If you have multiple servers distributed across different locations, copying the deployment share can improve performance and reduce network latency. Each server can serve the deployment content locally, eliminating the need for content retrieval over the network.

Most importantly, some files may not be copied (overwritten) if the folder in the target deployment share isn’t present. Or when it contains similar files. Therefore, I will recommend using a new deployment share when performing a synchronizing of shares. Want to take a look at the MDT Deployment process, take a look at this link.

How to link a removable media to a Deployment Share: Replicate Deployment share to a removable device, how to replicate MDT Deployment Share: How to Create a Selection Profile and Link MDT Deployment Shares, and how to fix Administrative Shares issues: How to create and access a hidden share folder on Windows devices.

Connect to a different (Target) MDT Server

Note: The connection is bidirectional and does not matter the server you are connecting to. This means, you can connect to the source or target and get the desired behaviour.

To do this, connect to the MDT/WDS Server. Launch the Microsoft Deployment Toolkit. This will open the Deployment WorkBench.

Right-click on the Root Deployment Share. Or click on the Root Deployment Share and on the Action pane, select Open Deployment Share.


Enter the Deployment Share name you want to connect to. If you wish to use a UNC path, it should be like the one below. hen click on Next to continue.


On the summary page, please confirm the details and click on Next to continue.


On the confirmation page, click on Finish to complete.


The connected Deployment Share is associated with the UNC path as shown below. This will help you in spotting the opened deployment Share.


Copy and Paste Content Between MDT Share

You should copy contents over MDT and not the File Server. To copy contents, locate the target deployment share and copy the application, OS, or Drivers as the case may be to the source deployment share. The image below shows the drivers copying to the source folder.

Copy MDT shares

Click on Close Deployment Share as shown below when done.

Close Deployment share

Note: Update the Deployment Share to reflect the configuration settings on the source server to reflect the new deployment share location. This step also involves modifying the paths, and task sequences to function correctly.

I hope you found this article useful on how to Copy Deployment Share between Servers without using linked Deployment Shares. Please feel free to leave a comment below.

Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x