Use Easy Sysprep v4 (ES4) to encapsulate Windows 7 tutorials

Total:
1. Installation system CTRL+SHIFT+F3 (administrator)
2. Backup system, fast Backup (PE)
3. Install patches, software (under the system), do not install security software, need to activate the software after reloading to activate
4. System backup (PE overlay), add Description: Win7 +hotfix +software, can also separate backup, security point, Win7+hotfix, then back up Win7 +hotfix +software
5. First stage package (full hook, System), input relevant information, network public, security update recommended, then select Administrator, Start encapsulation
6. Back up the first phase of the encapsulated system (PE) named "Win7 Sysprep", the purpose of the backup is that once the second phase of the encapsulation operation is wrong, you can directly restore the backup once again to perform the second phase
7. Second stage package (PE), start es4,oem and other information filling, enhance the deployment of two tick, do not tick, computer name selection prefix
8. Backup image (under PE), select "Limit Compression" at this time to create a new scene Win7.wim

(i) Installation and backup system

1. Install Windows 7

probably a lot of people would say that installing Win7 who wouldn't, that's also used to say? Installed Win7 Indeed everyone will, but how to install the most suitable for the system package, it is not necessarily everyone will. Installation is the package of this, there is no good installation method, encapsulation is just in vain, please pay attention to this section content.
Win7 (Vista) at the time of installation, the biggest difference from the system is that it will create a 100M partition (such as) by default, but the 100M partition is not the essence of the difference, the essence of the difference is "Win7 default to store startup files separately from System files”。


Let's leave the partition where the boot file is stored as the "boot Partition", and the partition that holds Windows is called the "system partition." WinXP era the boot partition and the system partition are all C drives, while the Win7 era divides the 100M storage separately from the boot partition, and the system partition as the C drive. So Win7 that 100M is not difficult to understand, understood to be the start of the file ad hoc "single room" on it.

what happens without the 100M? The answer is clear, no 100M system will fail to boot. Although the system files are all intact in the C drive, there is no boot system that does not start properly. Fast-reacting students have realized that this is going to be a problem, if partitioned in this way, package post-Deployment image if you only back up the system partition (C-drive), the image will not start after recovery! (In fact, this is not the case, use easy image X Such recovery image after the automatic repair MBR and boot file image Recovery Tool, the system can still start normally)

Is there any way to put both the boot partition and the system partition on the C drive, as in the XP era? Of course, the implementation is also very simple, using a third-party partitioning tool to partition operations. For example, use the Diskgenius partition as shown in:


After using the third-party partition tool partition, enable the Win7 installer again, you will be presented with a similar situation, will not appear 100M boot partition, select the system partition installation system, boot files and system files are located in the C drive.


2. Enter the most suitable system account for encapsulation: Administrator
Windows 7 Administrator has the highest system permissions available to the user. Even if you create a new administrator account that belongs to the Administrators group with the Administrator user, you cannot have the same system administration and operation permissions as Administrator. System encapsulation needs to perform a lot of modification and execution of system files, so the most suitable for system encapsulation is Administrator users. There are many ways to enter administrator users, but below I recommend one of the most direct methods, and not easy to produce problems and residues.
once the system is installed, it will enter the OOBE stage (e.g.), do not enter any information at this time, do not "next", directlyByCtrl + Shift + F3”。


ThenThe system will suddenly restart automatically, but don't worry, this is Microsoft's official approach, and will not have an impact on the system. When the system restarts, it will automatically log in as Administrator, enable the desktop, and automatically enable the Microsoft Official Packaging Tool "system Readiness Tool 3.14" (for example) when entering the desktop.


At this point you may already understand that this is actually the environment that Microsoft specially prepares for the system encapsulation. "System Readiness Tool 3.14" is the official Microsoft Packaging tool, all packaging aids (such as ES4) are at the core. But we don't need it right now,so just turn it off (x or takeIt is possible. It is worth reminding that the restart will return to this environment, and every time you enter this environment, "System Preparation Tool 3.14" is automatically started, regardless of, shut down.

3, system backup (PE)
The first step in the package is to back up the currently installed operating system. Avoid problems in the next steps, so that we have to reinstall the operating system, wasting time and energy. System backup presumably everyone will. For Win7, it is recommended to use ImageX backup. It is recommended to perform an ImageX backup operation using the  easy image x  in the  u disk installation assistant, with easy image X having a graphical operation and ease of setting the compression rate.


(1) The compression rate does not have to be selected too high, this Just to facilitate the encapsulation of the backup instead of the final backup , the compression rate
(2) imagex is a that can do the image overlay, that is, multiple backups if the file is the same, only the volume of one file (this feature will have a follow-up explanation), So in addition to setting the image file save location, you also set the name of the current sub-image, such as the sub-image name "Win7" in.


After waiting, the system backup is complete.


A stage a backup, a backup a summary, a summary of one progress, multiple progress a success.

(ii) Pre-package preparation
The purpose of encapsulation is to quickly deploy the operating system, reducing unnecessary duplication of effort. Therefore, we need to integrate the system patches to the source system, install common software, thereby reducing the duplication of work after each deployment.
1. installation patch (under System)
Windows 7 patch installation, you can choose to bring your own Windows Update or use a third-party fix pack, such as a system patch installation assistant.


If you are using Windows Update, there is a noteworthy tip that multiple versions are first loaded, and then the patch list is re-scanned , eliminating repeated installations and avoiding certain problems. For example IE10, the first scan will remove IE8 related patches, IE9 installer and IE10 installer , if your purpose is to install IE10, there is no need to install IE8 patch and IE9, directly as only click IE10, automatic installation and restart, Scan the list again and you'll see that IE8, IE9-related content is missing.


* Speaking of IE10, but also to mention a point, this should be the Microsoft side of the bug. If the package is Win7 x64, the default IE8, if the first upgrade IE9, then upgrade IE10, the package error, if IE8 does not upgrade IE9, directly upgrade IE10, the encapsulation is normal. If you want to integrate IE10, remember this point.

2. Install the software
Common software commonly used in a number of general, please according to your own system deployment scope and decide, such as example:

Special Reminders
(1) Not all software can well adapt to the system packaging deployment, especially some domestic software;
(2) Needactivation of the software, after deployment is generally required to reactivate；
(3) do not recommend the integration of security software, some security software will block the normal system deployment process, and even lead to blue screen downtime;
(4) If some software is not suitable for integration in the system, you can use the first-in-desktop silent installation method to resolve.

3. system backup

patch installation of about 20 minutes, software also need to install and adjust, so the overall time is generally not less than 30 minutes. to prevent unknown errors during encapsulation, it is recommended to back up the system again for future adjustments. After this backup, we can confidently start the encapsulation operation.
This backup we are going to talk about ImageX's multi-image overlay feature.The so-called image overlay (also known as an "incremental backup") is the ability to host multiple sub-images in the same image file, such as Win7 's installation file Install.wim generally contains the home base, Home Premium, Professional, the ultimate version of four sub-images. The best part is that the same file occupies only one volume, so four Win7 images do not occupy 4 Win7 of volume.
The overlay feature is useful for multiple backups in the package, and we can save our hard disk space by backing up patches, software Win7 with systems that were not previously installed, and multiple sub-images of the same file without taking up extra volume. Also, the more time it takes to attach a new image to an existing image file, the shorter the backup time required for the same file, which facilitates our multiple backup operations.
is the overlay image complex? No, easy Image X is a simple thing to use. The method of stacking backups is similar to the first backup method, except that this time you do not need to create a new image file, but instead choose a previously backed up WIM file, but note that you need to write a new sub-image description,such as "Win7 +hotfix +software".


When performing an image backup, there is a prompt asking if it is aimage attach action, click Yes.


After a moment, the image attach operation starts.


Once the image has been attached, we will find that the new image is added to the existing image file and overlaid with the old sub-image, and the WIM file adds only the patches and portions of the software that were just installed. （The second sub-image in the figure "Win7 +hotfix" is a backup that I made after I loaded the patch, the tutorial is not this backup, if you need, you can also do multiple backups at many times, anyway, no extra "duty-free", and can be multiple insurance)

(iii) The first phase package
Easy Sysprep v4 (ES4) differs from previous ES3, ES2, and traditional encapsulation aids in that it divides encapsulation into two phases.
The first stage: to complete the packaging operation as the primary purpose;
The second stage: To complete the adjustment of the system for the primary purpose.
the package and adjustment are separated to reduce the influence of the adjustment operation on the package operation and guarantee the package success rate.
1. Start ES4


2. Package Options


Description
(1) "Serial number" to fill in the system corresponding serial number, but Win7 serial number can be entered into the desktop and then fill out, so non-OEM version please leave blank(the wrong serial number will cause the deployment to fail!) )
(2) "Registered user and registered organization" cannot be null value, please fill in your relevant information, otherwise will remain the default.
(3) "Time zone" please set according to your time zone.
(4) "Use Current user profile for new Create user" uses the current user's configuration for all users, implemented in Microsoft's official method, allowing new users to keep their current configuration (such as desktop icons, themes, desktops, basic settings, etc.).
(5) "Transfer Current user desktop shortcut to public desktop" to move the current user desktop shortcut to the public desktop, making it easy for new users to use.
(6) "Package phase automatically clean up the computer device driver" package when cleaning Plug and play drive, in the official Microsoft method, recommended for use . (If the deployed computer is identical to the hardware configuration of the source computer, it can be used for bulk purchase and deployment of the enterprise intranet computer)
(7) The "Deployment phase automatically cleans up non-target computer device drivers" is not used to clean the current computer driver when deployed, it is recommended to use Microsoft Official method. (If the deployed computer is identical to the hardware configuration of the source computer, it can be used for bulk purchase and deployment of the enterprise intranet computer)
(8) "Working Group"The workgroup cannot be empty, otherwise it will remain the default.
(9) "Domain" please fill in the correct domain address, domain user and password, and ensure that the deployment time domain can be logged in, otherwise the deployment will not be able to end the problem.
(10) The language used by the system language system UI.
(11) "User Habits" time 12 hours/24 hours system, date arrangement, currency symbol and so on.
(12) The "keyboard rule" selection (current rule) saves the current input method rule to the deployed system, and selecting the specified keyboard rule will only use the specified rule.
(13) "OOBE" setting, can set network location, security update, etc., can make the OOBE process more automation.

3. User account
(1) login directly using administrator


This is the most commonly used is also recommended a way, after the deployment is completed without OOBE, directly to Administrator user login system, the most efficient, with the highest system permissions, ignoring UAC, System directory permissions lock and other effects. However, this mode invalidates the OOBE option that was previously set, and the OOBE option keeps the source system default, prompting you to set the network location when you first enter the desktop.

(2) Manually create an account at OOBE


This mode is the same as the installation version Win7, which restarts into the OOBE phase after deployment and prompts to create a new user. However, this OOBE is short (because the specified value has been assigned before the OOBE setting), basically just fill in a new username. The newly created user belongs to the Administrators user group by default, but does not have the same permissions as the Administrator user, and some system defaults are imported when the system creates a new user, such as re-joining Microsoft Pinyin and the smart ABC Input method, which is Microsoft's default, Not the outside can be arbitrarily left or right.

(3) Pre-create user account


This method is similar to (2), except that the user was created at the time of the first OOBE, but was preconfigured to create which users.
A. "Edit user" create user only need to set user name, password, user group, and then click "Add" on it, very simple.However, you are advised to fill in the correct user groups, the most commonly used are "Administrators", "Users", the same user belongs to multiple user groups when the user group is separated by semicolons, such as "Administrators; Users ".Note that a user with no password will be forced to set the user password for the first time, but cannot skip the process required to set it.
B. "Automatic login" is used to set a specified user to automatically log on to the system, need to fill in the correct user name and password.The number of automatic logons must be set to a positive integer value of 0 or leave blank to not limit the number of logins. Note that users without passwords cannot be set to log on automatically (except for administrator users).
C. "Administrator Password" can set Administrator password, if you are enterprise gateway, and do not want users to use Administrator, you can add a password.

4, Pre-package preview


5. Start Package

The first phase of the ES4 package involves only the required operations for encapsulation, so fewer operations and more adjustment operations are left for the second phase.

(iv) Phase II package
The second phase of Easy Sysprep v4 (ES4) is packaged in a PE environment rather than a regular system desktop environment. The second phase focuses on: adjusting the system configuration.
PE under the advantages of the system adjustment, the advantages are three:
(1) In fact, the system packaging necessary operation has been completed, to adjust the package after the system, do not worry about the adjustment to the success of the package impact;
(2) There is no need to think too much about the effect of system authority on system adjustment;
(3) Once some adjustments have been made, there is no need to re-encapsulate the system and adjust again.

1, backup the first stage encapsulated system
(1) also use the incremental backup method described earlier, The new sub-image is named "Win7 Sysprep"


(2) Wait for backup to complete


(3) Image overlay, the same file does not occupy additional space


this The purpose of the backup is that once the second phase of the encapsulation operation is wrong, you can directly restore the backup once again to execute the second phase of without having to re-execute the first phase of encapsulation. It is important to note that the second phase is not repeated because many of the settings are irreversible and are prone to unpredictable problems, so if the second phase fails, restore this backup to perform the second phase of encapsulation again.

2, start ES4


3, set up OEM information


(1) "Registered users" and " Registered organization "cannot be empty, if the configuration file is not loaded, read the settings in the first stage, otherwise the default will be maintained.
(2) "OEM Information" please fill in your information, the parts you do not need can be left blank.
(3) "OEM Picture" please set your OEM picture, leave blank when not needed.
(4) "Login page" means to modify the background of Win7 user login, use Microsoft Official to provide the method for OEM to modify, cannot be greater than 250K .

4, registry optimization


To import your registry-optimized items to this location, ES4 will be imported at multiple times to ensure the availability of registry optimizations

5, service optimization


Can adjust the running state of the service, but do not optimize it too much, or it will cause the system to be unstable or affect functionality.

6, deployment settings


(1) "OEM serial number" can be filled out with the OEM serial number to activate Win7 on the OEM PC. If there is no or enter the desktop, please leave blank, must not fill in, the wrong serial number will cause the deployment to fail!
(2) "OEM Certificate" If you have an OEM corresponding certificate, please set it here, ES4 will be imported automatically.
(3) "Time zone" please set according to the actual situation.
(4) "Regional language" sets the system's UI language, user habits, and keyboard rules (same as the first stage), and the keyboard rules, if no special requirements, remain "current rules."
(5) "Take over deployment process" can be used to add pre-and post-deployment interfaces, add deployment plug-ins and change deployment backgrounds (such as), but this method is not officially provided by Microsoft, so if you like the original stable system, Do not select this item (before and after the deployment interface Win7 is not necessary), and if you prefer a more beautiful deployment interface and more extended functionality, you can select this item.


(6) "Computer name" a legitimate computer name only allows a combination of 15-bit letters, numbers, and an underscore "-" (also said to be a system bug when all numbers are present)
• "completely random" 15-bit completely random, such as XDVG8B903V98SE4
• Fixed value within 15 bits of "fully fixed", such as Itiankong
• [Date]-[time] "date and time combination, such as 20130524-112117
• [prefix]-[date] [random] prefix is up to 5 bits, such as SKY-20130524KXQ, with more prefixes, fewer random values
(7) "System resolution" is used to set the resolution after the system is deployed, in fact, after the use of universal driver Assistant in the deployment, the graphics driver is installed properly, The first entry to the desktop is already the best resolution, without setting it, so it is recommended to keep it by default. It is necessary to change this project unless it is a large-scale similar computer deployment.
Note: OEM Activation requires three elements: Slic in the computer BIOS, System serial number, System OEM certificate, indispensable. Therefore, the OEM serial number and certificate features are used only when deploying OEM computers heavily, and are useless for various types of illegal activations.

7. Network Settings


(1) "Network Settings" can be set to specify IP or use DHCP. When using manual settings, be sure to fill in the correct IP and mask, otherwise the setting will fail, and "*" can be used to refer to the random number between 2~254.
(2) "network environment" can be set to use workgroup or domain, regardless of which please fill in the correct, not empty.
(3) "Network location" is divided into family, work and public, and the Win7 system comes with the three types of network standards are consistent, such as unfamiliar or complex network environment, can be temporarily selected "public" to ensure network security, deployment and then adjust according to the actual needs.

8. Dedicated calling interface


(1) Special invocation interfaces are generally reserved for specific applications or functions
(2) Universal Driver Assistant calling interface, reserved for it Sky Universal Driver assistant, can set deployment in/into desktop call
(3) Universal Driver Assistant calling interface comes with the first-in-the-Go Launcher Task Manager and the ability to remove decompression drivers
(4) Quick Configuration tool, can be set into desktop call it Sky Quick Configuration tool for quick System setup
(5) Integrated runtime, dedicated interface for it Sky One-click Run Library, can set deployment in/into desktop call
(6) Other functions See UI description

9, Universal calling interface


Description:
(1) Call EXE, BAT, CMD run, can set run parameters, can be set to hide and not wait.
(2) calls the Reg file for automatic silent import.
(3) deletes the specified file.
(4) deletes the specified directory.
(5) After the task is set, select the calling opportunity and click the Add button to add the task to the list.
(6) Select the task, click the Delete button to delete the task, and click the Edit button to adjust the task.
(7) Select the task and click the Move Up or Move Down buttons to move the task execution order.
(8) The finishing feature automatically sorts the tasks by the call time, and the second-phase encapsulation task is automatically organized before it starts.
Note:
(1) when the calling program is on the system disk, the drive letter is automatically converted to%systemdrive%.
(2) when the calling program is in a non-system disk, the drive letter is automatically converted to%x%, and the deployment automatically searches for all drive characters to find the specified program.
(3) also available? Rom% and%udisk% refer to the optical drive and USB drive, and will only search the specified device for the specified program when deployed.
(4) If you hide the running program and the program is stuck, you will not be prompted to use this feature with caution.
(5) If no wait mode is enabled, Will not wait for the execution of the current program to start the execution of the next program, which is a very bad state, only for special application calls, not to use, this function will not speed up the execution of the program or shorten the deployment process, instead of a bunch of problems.

10. Disk controller Driver


(1) IAR driver List is consistent with the latest Skyiar stable version
(2) To provide a complete set of broad compatibility of the IAR drive scheme, it is recommended to use
(3) If there is a need, you can manually select only the IAR driver, if there is a conflict between the IAR driver, the program will automatically remind
(4) The IAR drive scheme is not all selected, but the most compatible driver combination is selected

11. Save Settings


12. Start the second stage encapsulation operation


13. Back up the system image

At this point, the system encapsulation is over, we want to preserve the fruits of labor. Bring up the familiar easy image X, but this time don't choose to attach the image, but create a new image, because this image you have to deploy, do not mix with the previous backup.

(1) Setting (note selecting "Limit compression")


(2) Backup


(3) Image production completed


Of course, the final image you can also choose to use Ghost to backup, to see a person's preferences.

(other) ImageX vs. Ghost in Backup Windows 7 o'clock

The significance of this section is not to let people discard ghost and change with ImageX, just to let everyone have a more intuitive sense of the two. Ghost is the oldest and most used and best-practice image tool, and ImageX has the biggest advantage: it's a Microsoft biological.

To make a simple comparison, use the ImageX limit compression mode in the previously encapsulated image:


Start Backup:


I do not know if you have carefully observed the meaning of this figure, especially the shape of:

1. \ $windows. ~bt
2. \ $windows. ~ls
3. \windows\csc
4. \recycled
5. \recycler
6. \pagefile.sys
7. \hiberfil.sys

This paragraph of the above content? The meaning of this paragraph is to skip files that conform to this rule. These skips are the default by ImageX, and Microsoft's official support ignores all files that are irrelevant to the encapsulation deployment. Ignoring these files can effectively save the system volume-which is also the benefit of ImageX as a pro-son of Microsoft, after all, which files do not use Microsoft most clearly.

Approx. 3.03G after backup:


The same system uses ghost to back up and set the limit compression mode:


Backup start:


Approx. 3.61G after backup:


The contrast result is obvious, Imagex:3.03g,ghost 3.61G. In addition to compressing more than ImageX is slightly larger than ghost, the biggest reason is that ImageX automatically ignores useless files, and there is a certain advantage in this respect. However, it is not possible to say that ImageX must be better than Ghost,imagex can only run under PE, while Ghost is Dos/pe (but the newest Ghost12 has no DOS version), and ImageX needs more system resources than Ghost in backup and recovery. So choose which one, and also ask you to carefully consider.
There is a workaround, first use ImageX to back up the system, and then delete the source system to restore the system just backed up, so it is equivalent to using ImageX to remove the system of useless parts, and then use Ghost to back up, it seems good.
Digression, why is WinXP not recommended with ImageX? ImageX is a tool that has been used since the NT6 generation, while XP belongs to the NT5,NT5 system that does not support the WIM format as well as NT6, and ImageX itself is not designed for the NT5 generation. XP uses ImageX, a certain chance of the first-time system scan disk problem, but restart and normal, so it is recommended that XP or honest ghost.

Original address: http://blog.sina.com.cn/s/blog_6723f54b0102e3v3.html

Use Easy Sysprep v4 (ES4) to encapsulate Windows 7 tutorials