Troubleshooting of Remote Management in Windows (1)

The use of remote management is as important as the use of Active Directory AD and the use of group policies. It is an important indicator to measure the level of 2000/03 network administrators and system administrators. In the practice of Remote Management, network administrators are often troubled by various small problems, which seriously hinders administrators from using remote management to efficiently manage networks. This article will focus on WindowsServer2003 as an example to discuss various problems frequently encountered in remote management and their solutions. Some of these problems also involve XP and 2000. However, all discussions only target Microsoft's Windows technology and will not involve non-Microsoft Remote Management tool software.
Remote Management of 03/XP, if you do not consider the tool software, of course, the first "Remote Desktop ". Powerful Remote Desktop, remote software installation for the target computer, remote running of applications on the target computer, remote shutdown ......, This allows you to operate like sitting in front of the target computer. Of course, "Remote Desktop" is also insufficient: you cannot install software that requires a key floppy disk, or use audio devices such as sound cards on the target machine.

03 The Remote Desktop of XP is equivalent to the remote management mode of 2000S Terminal Service. Another mode is called the application server mode ). S can be remotely managed only after Terminal Services are installed. 03/XP only need to select "allow users to remotely connect to this computer" under "my computer/right-click/attribute/" remote "tab.

If you need to perform Remote Desktop Management on multiple computers (03/XP, 2000 S of Terminal Services Installed) on 03. Yes:
1. Start/run: MMC
2. "file" menu/Add/delete Management Unit/Add/Remote Desktop
3. Right-click the root node/Remote Desktop/in the console and add a new connection. Enter the target IP address, name, user name, password, and domain.
4. Repeat Step 3 to add the target computers to the console one by one.
5. Save the console when you exit to facilitate the next use.
Question 1: We often encounter this situation in our actual work: when we want to remotely manage the target 03/XP computer, we find that "Remote Desktop" is not enabled on the target computer ", of course, you can run it to enable it, which is very troublesome. If it is a hosted server, or far away, it will be more troublesome.
Solution: use the remote registry function. The procedure is as follows:
1. Change the administrator password of the local machine to be the same as the administrator password of the target computer, so that the Windows system of the target machine regards you as its local administrator.
Note: The above method is the most effective and common method to solve the problem of Operation permissions for remote target computer management. Other methods will also be described below, such as the second login to RunAs); or enter the user name and password when requesting authentication. However, other methods are not so common or prone to problems.
2. Log in again, start/run: regedit, go to the Registry Editor, select "Connect Network Registry" under the "file" menu, and enter the IP address of the target computer.
3. Find the machine \ SYSTEM \ current Control settings \ Control \ Terminal Service under the target machine Registry: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ TerminalServer ), change the value of fDenyTSConnections from 1 to 0, which is equivalent to selecting the "allow user to remotely connect to this computer" option.
Question 2The Remote Registry function is also commonly used to solve such a fault: After the computer is started, enter the user name and password, click confirm to log on, and stop on an automatically running application, you cannot see the desktop at all. For example, after the prototype of Ghost7.5 is pulled from the image, the system restarts without running the ngctdos (or ngctw32)-hide command. For example, an error or interruption occurs during the process of uninstalling an application that runs automatically upon logon.
These faults will leave garbage under the Run entry of the Registry. In severe cases, the above error will occur: The desktop is not visible at all, and the security mode is the same, so that the registry cannot be modified locally.
Solution: of course, if you know the cause of the problem, the solution is simple.
1. After the Remote Registry comes in, place the cursor on the "machine" sub-tree and click "edit" to search for it. search item: Check the Run cancel value and data, select "match all" to search faster ). The general problem is that you can manually delete a value and data under the Run item "HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run. Currently, we have not seen any problems in RunOnce and RunOnceEx.

2. If no error value is found, you can place the cursor on the "current user" tree and repeat the preceding steps.
Note: It is also a good way to directly search for the relevant content in the error information, but sometimes it may not be possible to search for it.

Question 3: We want to remotely manage the computer, but the goal is: "Remote Desktop" XP/03, 2000S are not installed with Terminal Services, or 2000 P. In this case, the remote function of "Computer Management" is weaker than that of Remote Desktop, because the remote management function of Windows Management tools depends on the provided plug-in ). The procedure is as follows:
0. Operation permission to solve the same common fault as above: win32 rejects access, which is a permission issue or fails verification)
1. Right-click/manage my computer and choose computer management"
2. Local Computer Management)/right-click/connect to another computer and enter the IP address of the target computer.
3. Just like managing local computers: remotely create users, modify passwords, manage devices, disks, and manage services.

Here are two examples to illustrate the problem:
Case 1: to remotely shut down or restart the computer, follow these steps ):
1. Manage the IP address of the target computer)/right-click/attribute/
2. "advanced" labels/settings, "Start and fault recovery" boxes/Shutdown
3. Select, operate: Shut down or restart; force the application to close: data may always be lost)
4. After you click OK, the remote target computer will be shut down or restarted.
The advantage of the remote shutdown method is that the terminal service does not need to be installed on the target machine, and the system is 2000/XP/03, which can be done as long as you have the permission. In addition, the graphic interface is easy to operate without the need to remember commands.

Case 2: the RPC service is disabled because of the "Shock Wave" virus on the target computer. After the host is restarted, the RPC service is stopped. Symptoms ............. As a result, the Property dialog box of the RPC service cannot be opened locally, and the Startup Type of the RPC service cannot be reset.
1. If the target computer is 2000, you can solve the problem as follows: use remote "Computer Management" to set the RPC Service Startup type on the target machine: automatic, and then restart the target computer.
Note: By the way, readers who want to do this experiment will explain how to stop the RPC service:
1) on 2000, you can change the Startup Type of services such as RPC, Plug and Play from "automatic" to "forbidden", but cannot be stopped manually. You need to set "forbidden" and restart the server ).
2) However, this is not possible on 03/XP. the Startup Type drop-down menu is gray. To disable this function, you can use the 2000 computer to connect to it and modify it. That is to say, whether the drop-down menu is optional depends on the local operating system, rather than the target operating system. You can also use the SC config command to set the RPC Service Startup type to "forbidden", which will be detailed later.
3) exercise caution in the experiment. If you cannot start the RPC service after it is disabled, you will have to redo the system.
4) My two assistants made the same mistake while doing this experiment according to my first draft. Therefore, I think it is necessary to explain the following problems and their solutions.
Problem: when trying to disable the RPC service, they disabled the RPC service in the hardware configuration file Profile 1 under the RPC service/right-click/attribute/"login" label. As a result, even if the RPC Service Startup type is set to automatic, the RPC service cannot be started due to the hardware configuration file's prohibitions. The error message is: "The RPC service cannot be started on the local computer. Error 1058: the service cannot be started because it is disabled or the associated device has not started ."
Solution: You can only use the registry because you cannot open a dialog box at this time.
A. Start/run: regedit. Find the following items:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Hardware Profiles \ Current \ System \ CurrentControlSet \ Enum \ ROOT \ LEGACY_RPCSS restart
B. Changing the data of CSConfigFlags under this option from 1 to 0 is equivalent to enabling ).
Note: You can also delete the LEGACY_RPCSS item under ROOT.
C. restart the computer.