Applications can also become "system services"

Recently, in order to ensure the stable operation and security of the shared server in the LAN, Tom decided to install a network firewall for the server. However, the enterprise-level network firewall will not be purchased because of the high price, therefore, Tom intends to temporarily use Rising's personal network firewall as an "enterprise-level" network firewall. But the problem also comes one after another.
Rising's personal Network Firewall runs in the form of applications. Every time you log on to the Windows system, the network firewall starts to run and cannot run in the form of system services in the background. How can this problem be solved? Tom found a tool named "“srvinstw.exe" in the Windows resource toolbox. It can change the application to a Windows system service. In this way, rising network firewall can run in the background as a system service, you don't have to log on to Windows every time to start the firewall.

Tool: http://www.cpcw.com/04/yf.rar

Application of srvinstw

Changing an application to a Windows system service is not simply accomplished by using "srvinstw". Note that there are two scenarios for changing an application to a system service.

If programmers fully consider using an application as a system service when developing and designing it, it is very easy to convert it into a Windows system service, you can use "srvinstw.

However, most applications did not take this into account at the beginning of development and design, such as rising's personal network firewall and peanut shells. Simply using "srvinstw" cannot turn them into system services. In this case, you need to use a combination of "srvinstw + srvany" to complete this operation, "srvany" is also a command in the Windows 2000 resource toolbox.

Battle

Now, Chubby will turn Rising's personal Network Firewall Application into a Windows system service. As Rising's personal network firewall didn't take it into account as a system service at the beginning of its design, its conversion can only be completed using the "srvinstw + srvany" combination method.

Step 1: Add system services

First, install the rising personal network firewall on the Windows 2000 server in the LAN. Next, Run "upgrade srvinstw.exe" in the Windows resource toolbox. In the "Install/Remove Server" Wizard dialog box, select "Install a Server" (add a service) option, and click "Next, select the "Local Machine" option, so that you can start to configure Rising's personal network firewall as a system service of the Local server in the LAN, click "Next, in the "Server Name" dialog box, Name the service (for example, "RFW ").

To access the selection execution file for the service, you cannot choose the main program named rfw.exe ", because it is not designed to be used as a system service. Now, you can solve this problem by using "“srvany.exe.exe". Click "Browse browse" to find the "“srvany.exe" file. Next, let's Select the "Server is its own process" option, so that the program is defined as an independent process running state, and click "Next, select the "System Account" option. At the same time, specify the service to run in "Automatic" mode, eliminating the trouble of Manual start. Finally, click "finish.

Step 2: Modify the Registry

After adding the system service, the RFW service cannot run properly. You must modify the registry of the Windows 2000 Server. Then restart the Windows 2000 Server.

Through the above settings, chubby has turned Rising's personal network firewall in the shared server in the LAN into a system service of the server. It runs in the background by default and can be started without logging on to Windows 2000.