You can update (generate) deployment media using the Update-MDTMedia cmdlet and the MDTProvider Windows PowerShell provider. Updating deployment media replicates the content from the original deployment share to the linked deployment share, and then generates .iso and .wim files. You can perform the same process using the Deployment Workbench, as described in Generate Media Images in the Deployment Workbench.

When the Update-MDTMedia cmdlet finishes, the following files are created:

·     An .iso file in the media_folder folder (where media_folder is the name of the folder that you specified for the media)

Generating the .iso file is an option that you configure by:

·     Selecting the Generate a Lite Touch bootable ISO image check box on the General tab of the media Properties dialog box (Clear this check box to reduce the time needed to generate the media unless you need to create bootable DVDs or start virtual machines [VMs] from the .iso file.)

·     Setting the same property using the Set-ItemProperty cmdlet

·     WIM files in the media_folder\Content\Deploy\Boot folder (where media_folder is the name of the folder that you specified for the media)

To update a linked deployment share using Windows PowerShell

1.   Load the MDT Windows PowerShell snap-in as described in Loading the MDT Windows PowerShell Snap-In.

2.   Ensure that the MDT deployments share Windows PowerShell drives are restored using the Restore-MDTPersistentDrive cmdlet, as shown in the following example:

Restore-MDTPersistentDrive -Verbose

Note   If the MDT deployments that share Windows PowerShell drives are already restored, you will receive a warning message indicating that the cmdlet is unable to restore the drive.

3.   Verify that the MDT deployments that share Windows PowerShell drives are restored properly using the Get-PSDrive cmdlet, as follows:

Get-PSDrive -PSProvider Microsoft.BDD.PSSnapIn\MDTProvider

The list of Windows PowerShell drives provided using the MDTProvider are listed.

4.   Update the deployment share using the Update-MDTDeploymentShare cmdlet, as shown in the following example:

Update-MDTLinkedDS -Path "DS002:\Linked Deployment Shares\LINKED002"

In this example, DS002: is the name of a Windows PowerShell drive returned in step 3.

Note   Updating the linked deployment share can take a long time. The progress of the cmdlet is shown at the top of the Windows PowerShell console.

The cmdlet returns with no output if the update is successful.

Related Topics

Managing MDT Using Windows PowerShell