You could for example set up a link which replicates the drivers folder from your central MDT server to your branch server. This allows you to replicate your central deployment share or certain selected parts of your deployment share to other servers. New in MDT 2010 is the ability to create Linked Deployment Shares. You would need to manually copy your deployment share, or some of its subfolders to your branch server in order to update it. One of the main problems is that when you make changes to the deployment share on your central MDT server, the changes will not be updated on your branch server.
Whilst the method above is a quick and dirty fix to get your existing deploment share up and running on a new server, it has several shortcomings.
#File details modified by copiy to usb install#
The only other thing you need to be careful of is any hard coded references to the UNC path of the old server deployment share that you may have in any custom scripts that you are using to install applications or make customisations.įinally, update the deployment share by right clicking on it in the Deployment Workbench and choose ‘Update Deployment Share’. You can also update the deployment share properties to reflect the new path if required: DeployRoot=\\NewServerName\DeploymentShare$ This setting should be edited to reflect the UNC path to the distribution share on the new server.Į.g. The only significant change you need to make using this method is to edit the DeployRoot setting in the bootstrap.ini file found in the ‘Control’ folder of your deployment share. In the first instance it is simple enough to take a copy of the deployment share to a USB drive, and then copy this on to the branch server and add then add it to the Deployment Workbench on the branch server. Having finalised our new task sequence for Windows 7 SP1, we started looking at options for copying the deployment share from our central MDT server to the branch offices and came up with several methods.
We had previously been using MDT 2010 at our central site to install and commision new computers, or rebuild existing computers, but to get Windows 7 rolled out quickly we needed this functionality in each of our branch offices. During our recent Windows 7 and Office 2010 rollout we decided to set up MDT 2010 on each of our branch Windows Server 2008 servers to automate the client upgrades.
0 kommentar(er)
