Attached 3, MDT Update 1 Batch Deployment-windows 7 mirroring method to prevent the remaining Windows reset count reduction

The recent upgrade of the MDT deployment system under the Windows 7 operating system image, upgrade patches, update the application, and then get the mirror after the redeployment, but in the upgrade process encountered a problem, that is, some of the images are properly acquired before deployment, can install normally, but after the first boot, the win 7 system displays a login interface , in this interface no administrator login account (normal MDT after deployment of Windows 7 shows Administrator account), enter the administrator account, password, the results show that the account has been locked.

Using the online method to enable the Administrator account, the original MDT deployment task is interrupted, that is, unable to fully run an MDT task.

This problem actually met last year, but did not notice, through the online information for a few weeks, also did not find a good solution, one day in the foreign web site found may be due to the Windows 7 sample machine multiple deployments, a Windows 7 sample machine packaging up to three times, More than three times may cause problems, and after testing, this problem is really caused. Installation of the original method, WINDOWS 7 system installation, encapsulation, patching, re-encapsulation, patching, re-encapsulation method is not feasible.

Cause analysis, Windows 7 system has a "remaining Windows Reset Count", the system is new installation of 3, such as replacing the motherboard, encapsulation, or a SP patch pack, this counter will be reduced by one, reduced to 0 after the package will be a problem.

Windows 7 System "remaining Windows Reset Count" View method, using the command line "SLMGR.VBS-DLV"

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/69/wKiom1X8vWbCDGLUAAXawcdXXA0848.jpg "style=" float: none; "title=" Win7x86-2015-09-18-19-15-28.png "alt=" Wkiom1x8vwbcdgluaaxawcdxxa0848.jpg "/>

According to enthusiastic netizens tips and network search, in fact, Microsoft provides a win 7 multiple encapsulation method, you can prevent the "remaining Windows Reset count" reduction, in the package add a SkipRearm parameter to Unattend.xml, this file in the MDT UPDATE 1 of the shared directory under the control directory for the corresponding image get directory can be found, and can be modified with a text editor

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/66/wKioL1X8v6HhgzkrAAJV-PpnS6w040.jpg "style=" float: none; "title=" Win2012r2u3-2015-09-18-19-18-39.png "alt=" Wkiol1x8v6hhgzkraajv-ppns6w040.jpg "/>

Using a text editor, add the following, which corresponds to the X86 platform and is limited to the win 7 platform

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/69/wKiom1X8vWrDRNrRAAa2GCY1BZk368.jpg "style=" float: none; "title=" Win2012r2u3-2015-09-18-19-20-01.png "alt=" Wkiom1x8vwrdrnrraaa2gcy1bzk368.jpg "/>

Users can copy down the content to modify their own package parameter file (corresponding to X86, only valid for Win 7)

<component name= "MICROSOFT-WINDOWS-SECURITY-SPP" processorarchitecture= "x86" publickeytoken= "31bf3856ad364e35" Language= "neutral" versionscope= "nonSxS" xmlns:wcm= "Http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi= "Http://www.w3.org/2001/XMLSchema-instance" > <SkipRearm>1</SkipRearm> </component>

After testing the MDT UPDATE 1 deployment platform, adding the above parameters can encapsulate Windows 7 systems multiple times, preventing the remaining Windows reset count from being reduced to 0, enabling Windows 7 systems to be packaged multiple times.

This article from "Computer player Notes" blog, declined reprint!

Attached 3, MDT Update 1 Batch Deployment-windows 7 mirroring method to prevent the remaining Windows reset count reduction