Microsoft Surface 3 - Manual (Page 23)

© 2014 Microsoft Page 23
Caution: The first item under the Deployment Workbench is the Information Center, where you will find the
documentation for MDT, a getting started guide, and a list of components. It is not recommended to update MDT from
the list of components because the incorrect version of the components may be installed. To ensure the latest tools are
available to MDT, ensure that the latest version of the Windows ADK is installed.
Deployment Shares
A deployment share is a collection of the major components of MDT which are configured together as a collective unit. It
can contain images, applications, drivers, task sequences, boot media, configuration files, and any other deployment
component required. A deployment share is essentially a network share in which these components are located. It is
hosted as a standard network share and secured through the same permissions and settings as any other folder shared
on the network.
After having installed MDT and opening the Deployment Workbench, the Deployment Shares section will be empty, so
you’ll need to connect to an existing deployment share or create a new deployment share. When creating a deployment
share there are several considerations, as follows:

Isolation

Scope

Performance

Security
Note: It is important to remember that it is possible to have more than one deployment share, and in many cases it is
ideal to have at least two for the reasons outlined in this section. The number of deployment shares that are used in any
given environment can vary, but it is common to have more than one.
Isolation
One of the most important reasons to have more than one deployment share is isolation. There are two primary reasons
to isolate one deployment share from another:

The two deployment shares utilize different, incompatible configurations.

Scenarios where deployment shares require different security and permissions.
One common scenario that reflects the need for multiple deployment shares is when one deployment share is
configured for a laboratory or testing environment. This deployment share is configured with permissions that permit
full access to IT pros and does not contain organizational information such as instructions for the joining of the domain.
It is used to prepare base images, test deployment configurations, settings, and applications, and to develop solutions
which can be deployed to production deployment shares. Production shares are used to deploy images that are
configured to join the domain, permissions are much more restricted, and the deployment solutions may be more
automated.
Scope
An important question to ask when considering the number and purpose of separate deployment shares is what those
shares are intended to address. In some cases, the scope of a deployment project may be all-encompassing, so the