原帖地址：http://blogs.technet.com/mniehaus/archive/2009/06/27/mdt-2010-new-feature-5-support-for-multiple-deployment-shares.aspx

With MDT 2008, you could have one distribution share, which corresponded to a lab deployment point.  You could then have additional network deployment points and media deployment points, with each of these receiving a subset of what was on the main lab deployment point.
在2008里，一个lab分发点只能有一个分发共享。你也可以使用网络共享或者媒介（比如光盘），但你必须创立新的分发点

With MDT 2010, we’ve changed terminology somewhat.  Now, instead of distribution shares and deployment points we just have deployment shares.  And there’s no real differentiation between “lab” and “network” – a deployment share is a deployment share.  You can have as many of those as you want, and you can choose to replicate all content between them or keep them independent.  Each deployment share can be on the local machine or on a different server (accessed via the UNC path); we even support standalone DFS roots.
在MDT2010里，我们不再称呼分发共享或者部署点，我们称之为部署共享。而lab和network之间并没有本质的不同。你可以根据需要创建无数个共享，可以选择是复制相同的内容或者保持独立。没一个部署共享可以建立在本地机器或者不同的服务器上，甚至支持独立的DFS根

So let’s talk about a few different scenarios that you might want to consider.
所以让我们来讨论这几个方案的不同之处：
Scenario #1: Simple but reliable
场景1：简单而可靠
You want to have a single deployment share on a highly-available file server cluster with SAN-attached storage, but you don’t want to install MDT on that server.  That wasn’t possible with MDT 2008, but it’s simple with MDT 2010.  You can install MDT on your workstation (or any other machine) and use it to manage the contents of a deployment share on the file server cluster via the UNC path that you created.
你在一个使用存储网络的高可用性的文件服务器上建立单独的部署共享，但你不想在这台服务器上安装MDT——这在2008里是不可能的，但在2010里却变得十分简单。你可以在你的工作站上安装MDT，用它来管理文件服务器上的部署共享

Scenario #2: Private and public
场景2：内部和公开
You have a lab environment where you create your reference p_w_picpaths.  You import those p_w_picpaths into Deployment Workbench and create new task sequences to deploy those.  But you don’t want your end users to ever deploy the reference p_w_picpath task sequences, just the ones that deploy the reference p_w_picpaths.  With MDT 2008, you could have done that using a lab deployment point and a network deployment point.
你在一个实验室环境里创建了参考镜像，你把镜像导入了工作台并建立了TS去部署他们。但你不想让你的终端用户使用你用来制作参考镜像的TS，而只想让他们使用部署镜像的TS。在MDT2008里，你需要分别使用两个部署点来实现。
With MDT 2010, you would create two deployment shares, for example \\SERVER1\Lab and \\SERVER1\Production.  You can then replicate only the items you want from lab to production.  This is done using “linked deployment shares”, a new feature that allows you to specify the target deployment share (e.g. \\SERVER1\Production) and the content that should be replicated to it.  Or, you could do this manually as Deployment Workbench could have both deployment shares open at the same time, enabling you to manually copy the needed items from one share to the other.
在MDT2010里，你可以创建两个部署共享，例如 \\SERVER1\Lab和 \\SERVER1\Production. 把需要的部分从lab复制到production里。这是通过新功能“linked deployment shares”来实现的，允许你把两个部署共享建立链接。或者你可以手动来完成，因为工作台可以同时打开两个部署共享，允许你从一个共享拷贝到另一个中
Scenario #3: Server and desktop
场景3：服务器和桌面
You might have two different teams, one which works on server OSes, p_w_picpaths and task sequences, and the other that works on desktop OSes, p_w_picpaths, and task sequences.  You can create two deployment shares to support that, and even selectively copy content (e.g. a subset of drivers or applications) between them.
有时我们有两个团队，分别负责服务器和桌面计算机。你可以创建两个部署共享来分别支持，并有选择的拷贝内容

Scenario #4: Cooperative deployment shares
场景4
Some companies do not have a completely centralized IT group.  They may have a central team that creates reference p_w_picpaths and packages applications, but regional IT groups are responsible for the actual deployment, including figuring out what drivers are needed for the hardware used at that location.  With MDT 2010, you can have a central deployment share, then selectively replicate content to regional deployment shares, e.g. all p_w_picpaths and applications, without disturbing the rest of the deployment share content.  The IT administrators at the regional sites can maintain their own task sequences, drivers, etc.
有的公司并没有一个完全集中管理的IT部门。也许他们有一个核心的团队负责创建镜像和包，而实际的部署则由地区的it部门实施。这就带来一个问题，两个不同的地区，硬件软件的需求并不一定一致，比如驱动。在mdt2010里，你可以创建一个核心的部署共享，有选择的把内容复制到各个地区的部署共享上。例如，把镜像和程序进行复制，而驱动、TS等则由本地提供