Updating deployment share

For the purposes of this topic, we will use three machines: DC01, MDT01, and PC0005.DC01 is a domain controller, MDT01 is a Windows Server 2012 R2 standard server, and PC0005 is a blank machine to which you deploy Windows 10.Separating the processes of creating reference images from the processes used to deploy them in production allows greater control of on both processes.You will then configure the deployment share, create a new task sequence, add applications, add drivers, add rules, and configure Active Directory permissions for deployment.– Run the Java exe on a test machine, digg out the MSI files from the %userprofile%\Appdata\….area – Create an MST using ORCA, set the update settings to not update etc.

updating deployment share-18updating deployment share-69

The second half of the server-side process is controlled by the Address Book Service which pulls information from the SQL database and writes the changes to the address book files.

If this is not the case or for some reason normal replication is failing then a manual process can be used to toss out the entire copy of AD information in the SQL database’s address book store and regenerate a completely new copy.

To rebuild Lync’s copy of the AD data simply use the cmdlet.

MDT01 and PC0005 are members of the domain for the fictitious Contoso Corporation. These steps will show you how to configure an Active Directory account with the permissions required to deploy a Windows 10 machine to the domain using MDT.

Note For important details about the setup for the steps outlined in this article, please see Deploy Windows 10 with the Microsoft Deployment Toolkit. These steps assume you have downloaded the sample Set-OUPermissions.ps1 script and copied it to C:\Setup\Scripts on DC01.