Shulou(Shulou.com)06/03 Report--

System environment: windows2012

The problem with this method: when the PE image does not have a network card driver to install the system, it cannot be installed on the network.

Software link used: https://pan.baidu.com/s/1pLUIlXD password: k7hf

The software used is shown below:

In order for the system image to be loaded using the network, you need to download a networked pe image (I used the win7pe.iso in the figure above). But this win7pe.iso has some incomplete functions, such as no diskgenius partitioning tool, no winntsetup installation tool, so you need to package the software in the XMPE2012.ISO above into the win7pe.iso image. Let's talk about the packaging process.

For WDS services, the most important thing about the PE image is the boot image (that is, the wim file in PE that ends with .wim), so this is the same file we need to modify. After loading the PE image through the CD-ROM drive, you can look for the wim file in various directories. The location of the wim file in the two PE images used here is as follows:

Once found, copy the two files to a directory (such as I put directly into the D disk directory above) for subsequent operations.

Start the unencapsulation and encapsulation of the image:

First, set up two directories and store them as two PE unpackaged files. Above I set up win7 and win8 directories in the same location as PE (directory names have no meaning, just to distinguish)

Next, you need to operate on the command line, open the command prompt and execute the following command to unpackage one to the win7 directory and the other to the win8 directory:

Dism / mount-wim / wimfile:D:\ WIN7PE.WIM / index:1 / mountdir:D:\ win7dism / mount-wim / wimfile:D:\ BOOT.WIM / index:2 / mountdir:D:\ win8

The implementation results are as follows:

In fact, when you enter PE, you will see that what is displayed in its Bootx directory is the bottom of these directories, that is, we just need to put the desired application in these directories, but the general program will be placed in the Program Files directory.

If you want to display these programs on the desktop, you also need to modify the D:\ win7\ Windows\ system32\ PECMD.INI file and make a link in it.

The contents of the pecmd.ini file in the win8 directory are as follows:

All we have to do is paste the contents of the above desktop in the red box into the pecmd.ini file in the win7 directory, and copy these application directories under the Program Files directory in the win8 directory to the Program Files directory in the win7 directory. This allows you to use the following command to encapsulate it at the command prompt.

Dism / unmount-wim / mountdir:D:\ win7 / commitdism / unmount-wim / mountdir:D:\ win8 / commit

After the encapsulation is successful, there are no files in the directory used for unencapsulation, and the command line prompt is as follows:

In this way, you can use WDS to load the boot image, and enter the PE interface to see the packaged application. However, the partition tools and system installation tools in the above PE image XMPE2012.ISO are not easy to use, so I download them from the Internet and replace the original program.

This is the encapsulation and unencapsulation of the boot image. At the same time, there may be some problems in the execution of unencapsulated and encapsulated commands, and finally the problems encountered will be affixed.

The problem of the installation system loading the installation image can be solved like this: since the PE image can be connected to the network, use sharing to download the windows installation image from the WDS server. I gave it a try. It really works. In the following three pictures, the machine on which the system is to be installed enters the PE

Enter the user name and password of the WDS server here

Enter the user name and password and go to the shared directory

The image directory of the WDS server below is the same as the directory seen above in PE, so you can put the image files in this directory.

This allows you to use the system installation tools in PE to install the system. When selecting an image file, you can use the remote address directly, as shown below:

The following are the problems encountered in the process of starting image encapsulation and unencapsulation

D:\ > dism / mount-wim / wimfile:D:\ install.wim / name: "windows 7 ultimate" / mountdir:D:\ win7dism / mount-wim / wimfile:D:\ WIN7PE.WIM / index:1 / mountdir:D:\ win7D:\ > dir drive D is a newly added volume directory with serial number 1094-F81C D:\ 2017-05-05 17:34 3316 Autounattend.xml2017/08/02 17:18 4413020160 cn_windows _ server_2012_r2_x64_dvd_2707961.iso2017/08/11 09:17 3028612426 install.wim2017/08/02 17:03 RemoteInstall2010/11/21 12:03 win72017/08/02 18:13 3448406016 win7_souche.iso 4 files 10890041918 bytes 2 directories 35308953600 available bytes D:\ > dism / p_w_picpath:D:\ win7 / apply-unattend: D:\ Autounattend.xmlD:\ > dism / unmount-wim / mountdir:D:\ win7 / commit deployment image service and management tool version: 6.3.9600.16384 image file: d:\ install.wim image index: 4 saving image [= 100.0% image =] uninstalling image [= 100.0% image =] operation completed successfully.

After the above is mounted once, it cannot be mounted again:

Reason: after encapsulation, the directory mounted by the image will be unmounted. Because the directory mounted by the image may be open, the uninstall cannot be completed, and then you will exit directly. The next time you use this directory, an error will occur because it is still in use.

Solution: check which directories are still in use, and then uninstall them.

After mounting it once, you cannot mount it again: C:\ Users\ Administrator > dism / mount-wim / wimfile:D:\ BOOT.WIM / index:1 / mountdir:D:\ win8 deployment Image Service and Management tool version: 6.3.9600.16384 error: 0xc1420127 has mounted the specified image in the specified WIM for read / write access. You can find the DISM log file C:\ Users\ Administrator > dism / get-mountedwiminfo deployment Image Service and Administration tool version: 6.3.9600.16384 installed image: installation directory: d:\ $RECYCLE.BIN\ Smura 1-5-21-2059717224-812489170-812489170\ $RMT6N56 image file: d:\ BOOT.WIM image index: 1 installed read / write: status: invalid operation completed successfully. C:\ Users\ Administrator > dism / unmount-wim / mountdir:D:\ $RECYCLE.BIN\ Smur1-5-21-2059717224-3891187800-812489170-500\ $RMT6N56 / discard deployment Image Service and Management tool version: 6.3.9600.16384 Image File: d:\ BOOT.WIM Image Index: 1 unmounting image [= 100.0% image =] operation completed successfully.

Reference:

Http://winsystem.ctocio.com.cn/Longhorn/375/8817375_3.shtml

Https://wenku.baidu.com/view/fbbeee8db9d528ea81c779fb.html

Https://wenku.baidu.com/u/yuanfeng1129?from=wenku

Https://wenku.baidu.com/view/9bb52a7d52d380eb63946d4b.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.