Expert Tips: When a business computer encounters an update that must be restarted to take effect, the

I saw a post in the Microsoft News Group a few days ago, asking how to make the customer-facing business computer must be restarted before it can take effect. The dialog box for confirming the restart does not pop up when the system is updated, so that this dialog box is not allowed to interfere with the normal use of the client. Although the author has provided some suggestions, the computer described by the questioner is too “commercial” and ultimately failed to solve it perfectly. It is necessary to restart when installing some system updates, and not to restart when the commercial computer is working. This seems to be a contradiction that can never be reconciled.

Why do some Windows system updates have to be restarted to take effect when they are installed? This is mainly because the system files that need to be upgraded are currently being used by the operating system. The lack of corresponding system files will immediately cause Windows to crash. Therefore, only Windows is shut down and restarted, and the corresponding system files are upgraded during the restart process. For example, MS09-025 (KB968537) released this month (June 2009) is an update that involves upgrading the Windows kernel files. Conversely, other updates that require upgrading system files that may not be currently in use may not require a reboot at the time of installation, such as MS09-022 (KB961501) released this month, if we do not currently have the Windows spooling service turned on, install There may be no need to reboot when this update is made.

It is due to restart some updates must be installed in order to prevent the restart may result in data loss, update confirmation dialog box appears before the restart will be to alert the user. Once the dialog pops up, it can interfere with applications that are in the foreground of commercial computers, such as customers who are using front-end applications (such as customers who are operating bank ATMs) or non-computer professionals (such as grandfathers who don’t know computers) Aunt's age staff) I don't know what to do. In order to avoid such troubles, we should try to avoid the commercial computer from popping up the restart confirmation dialog box when it is working. This process can refer to the following situations:

1. by way of local installation to install the update:

way if we are to install the update manually from the Microsoft website to download the installation file and save it locally (.MSU or .EXE file), and then manually perform the installation, you can add -QUIET -NORESTART two parameters by command line. -QUIET means to perform the installation silently without human intervention; -NORESTART means that if the update requires a restart, it will not restart. This way you can install this update silently and wait until the working time has elapsed before manually restarting. Note - The -NORESTART parameter requires the cooperation of the -QUIET parameter to take effect, and it does not make sense to use it alone.

This method is suitable for public computers in the office of one or two. For example, this morning I found out that Microsoft released the June security bulletin and manually downloaded the updated installation files. You can install them first without the QUIET -NORESTART method, but they will not be restarted during the day. The impact of the restart. Wait until the computer is turned off when you get off work. When you reboot in the morning, these updates that need to be restarted are already installed.

2. way to WUAU or WSUS to install updates:

locally installed somewhat cumbersome way after all, so many people chose to open WUAU local automatic updates. For companies with a large number of computers, deploying WSUS is also a wise choice. However, installing the update in WUAU or WSUS mode does not apply the -QUIET -NORESTART parameter, which is specific to the local installation and there is currently no way to extend WUAU or WSUS. If we have already started the installation of an update that needs to be restarted via WUAU or WSUS, then this updated restart dialog will be unavoidable. Although there is a "Do not automatically restart after the scheduled automatic update installation" in Group Policy, it does not completely prevent the dialog box from appearing. The difference is that the user is asked to restart immediately when this policy is enabled, and the user is notified for five minutes when this policy is disabled. After the automatic restart. Both types of dialogs will interfere with the front-end programs of commercial computers.

So, if we do not intend to let the front desk of commercial computer programs subject to any interference, so only temporarily start WUAU or WSUS to install updates, but only download the update, postpone the installation. We can set "Configure Automatic Updates" in "Computer Configuration" - "Administrative Templates" - "Windows Components" - "Windows Update" of Group Policy, and then select its fourth item "4. Automatic Download and Plan Installation" and set Planned time outside of working hours. This way, during the working period, WUAU or WSUS will only get updates in the background, but will suspend the installation. As long as the installation is not performed, the front end of the commercial computer will not have any prompts; wait until the non-working time, and then install the update and restart according to the scheduled time.

3. None of formula 7 × 24 hours of rest in commercial computer:

whether locally or installation or WUAU WSUS, both methods mentioned before are only updated delay time to restart Non-working hours. But we know that there are many commercial computers that have no rest for 7×24 hours. They may only have a valuable restart opportunity every day, every week or even monthly. The problem I encountered in the newsgroups was the application of WSUS's 7x24-hour bank ATMs, which had a chance to restart only when the user was scarce at three or four o'clock in the morning. However, even if "Automatically restart after scheduled automatic update installation" is set to Enabled, the ATM will still encounter problems even if the scheduled time is set at 3 or 4 o'clock.

According to the introduction of this man, ATM machine touch-screen and full-screen program default is in the foreground, it can determine whether the user has removed his bank card, if the card is still there, touch screen programming in the ATM machine It can block the ordinary ATM machine, but can't prevent the update restart dialog from taking over the impact of the front desk. WSUS can't judge whether the user has taken the card, which is easy to cause problems. For example, suppose a night owl user who does not sleep in the middle of the night happens to withdraw money at three or four o'clock in the morning. When the bank card is not taken away, WSUS plans to restart. The touch screen program of the ATM will be forced after the restart dialog box appears. Transfer to the background, at this time the user can not continue to touch, only choose to make the update program restart. However, after restarting, the re-running ATM touch screen program will not be able to vomit. Because the bank has regulations, users may leave the site for help when restarting, in order to prevent others from stealing cards, it is forbidden to vomit. At this time, the night owl user can say that the sky should not be called, and the land is not good. Even if he goes to the bank staff for help, he must wait a few hours until the daylight bank goes to work.

read this man's narrative sensory system updates and ATM machine touch screen program needs to be improved. If the system update program does not pop up the dialog box for preempting the foreground, but only prompts in the notification area of ​​the taskbar, it will not cause the failure of the touch screen program of the ATM machine; if the touch screen program of the ATM machine is always forced to display in the foreground, all will be The pop-up dialog box is occluded in the background, just like the Windows Task Manager, it can also prevent itself from being redirected to the foreground display. This problem can be solved no matter which side can be "modest to step" or "tough". In short, there seems to be no good solution to this problem. At present, I can only hope that the system update program or the ATM touch screen program will be improved.