The right remedy is to allow IIS to "implant" the Ghost System

With the continuous impact of Internet viruses, Windows system crashes frequently. In order to quickly restore a computer system to normal operation, many friends like to use the Ghost system to reinstall the computer. However, while fully enjoying the speed and convenience provided by the Ghost system, we will also encounter some troubles, the failure to install IIS functional components in the Ghost system is a headache. As more and more personal websites rely on the system function components of IIS, when the IIS system function components cannot be installed in their own computer systems, it will bring us a lot of trouble to build personal websites in the future. In the Ghost system, is there really no way to implant the IIS system service?
IIS cannot be implanted
By default, the function components of the IIS system are automatically integrated into the Windows system. You only need to add the system function components, the IIS service can be easily implanted into the Windows system. However, in some system installation disks of Ghost versions, we cannot install IIS system functional components. Why?
In fact, the system installation disks of most Ghost versions are customized for most common users. In order to make the Windows system run cleanly, in the Ghost version, the system blocks all the system function components that are rarely used by common users. This not only greatly improves the system installation speed, but also effectively improves the system operation security. When shielding IIS system function components, the Ghost system uses the "MSDTC" method to disable the system service, when the IIS Installation Wizard detects that the "MSDTC" service in the local system is not running properly, the remaining IIS installation operations will naturally fail, this is also the main reason why we cannot "implant" the IIS service in the system environment of the Ghost version.
Enable System Service MSDTC
Many Ghost versions of the system automatically shut down the system service MSDTC and run it. As a result, the functional components of the IIS system cannot be "implanted" into the computer system, to solve this problem, we need to manually re-enable MSDTC, a system service that is shut down and running in the Ghost version. Before enabling system service MSDTC, you can open the "Start" menu of the local system and click "set"/"Control Panel" commands in sequence, in the displayed system control panel window, double-click the "Administrative Tools" icon. Then, find the "component service" icon in the management tools List window and double-click the icon with the mouse, open the component service window of the corresponding system. In the left-side area of the window, move the cursor to the "console root directory" Node option, click "component service", "computer", "my computer", and "COM + application" under the node options, when the system service MSDTC is not successfully enabled on the local computer system, a message like "COM + cannot talk to Microsoft Distributed Transaction Coordinator" appears on the System screen.
At this time, we need to manually enable the MSDTC System Service in the local computer system. The following describes how to enable the System Service: first, click "start"/"run" on the desktop of the local computer system. In the displayed system run text box, enter the string command "services. msc, click OK, open the Service List window of the corresponding system, find the system service option "Distributed Link Tracking Client", double-click the System Service option with the mouse, open the option settings page, as shown in 1. Click the "General" tab on the settings page, and click the "Start" button on the corresponding tag settings page, in this way, the disabled System Service "Distributed Link Tracking Client" can be successfully enabled. To ensure that the system service can be automatically started with the Windows system in the future, we also need to change the corresponding System Service Startup Type parameter to "automatic ", click OK to save the preceding settings.

When the system service MSDTC is successfully enabled, We will click the "component service"/"computer"/"my computer"/"COM + application" subitem in the future, on the System screen, there will be no prompts such as "COM + cannot talk to Microsoft Distributed Transaction Coordinator. Then, right-click the "IIS Out-Of-Process Pooled" option in the display area on the right Of the corresponding "COM + application" subitem, from the shortcut menu that appears, run the "properties" command to go to the "IIS Out-Of-Process Pooled" option attribute Setting dialog box. Click the "ID" tab in the dialog box to go To the tag settings page shown in 2, and select the "System Account" option at "Account" on the page, select the "Interactive User" option under the corresponding option, and click "OK" to save the preceding settings.

Let the IIS service "implant" the system
After completing the above preparations, it is very easy to install and enable the IIS system component service. The specific settings are as follows:
First, click "start", "set", and "Control Panel" commands in the local computer system. In the displayed system control panel window, double-click the "add or delete programs" icon, and click the "Add/delete Windows Components" tab in The Wizard setting window that appears to enter the Windows component wizard window, in the "components" list box of the window, select the "Internet Information Service (IIS)" option (3), and then click the "details" button, in the Settings dialog box that appears, select the "World Wide Web Service" option and other related options, click the "OK" button, and insert the Windows XP system CD as prompted on the wizard screen, in this way, the functional components of the IIS system can be successfully installed. After the IIS system function components are installed, we can use the IIS service to build our own private website or enterprise website in the Ghost operating system environment.

It is worth noting that after the IIS system component is successfully installed, we sometimes encounter a failure in starting the IIS service, this is probably because the W3SVC service in the system is unexpectedly stopped. At this time, we only need to find a way to restore the system service to normal. Of course, sometimes we only need to reset the IWAM account password in the local computer system to solve the failure of IIS service startup.
When resetting the IWAM account password, we can click "start", "set", and "Control Panel" commands in turn, in the displayed system control panel window, double-click the "Management Tools" icon, and then double-click the "Computer Management" icon. In the displayed System Computer Management window, expand the "Computer Management", "System Tools", "local users and groups", and "users" branch options in the left-side display area one by one, in the display area on the right of the corresponding "user" branch option, we will see the "IWAM_YCB" account, which is automatically generated by the Windows system when we install and start the IIS system component service, it is mainly used to start Internet Information Services for applications other than system processes.
When modifying the IWAM_YCB password, you only need to switch the system to the MS-DOS window and execute the adsutil script command in the command line of the window to change the password, for example, you can enter X: inetpubadminscriptsadsutil set w3svc/wamuserpass "123456" in the command line (the adsutil script command is saved in the script directory of the corresponding computer system by default, so here we need to enter the path information completed by the adsutil script command), click the Enter key, and the password of the "IWAM_YCB" account will be changed to "123456"