What about Windows Remote Desktop?

To make it easy for users to connect to remote desktops, Microsoft offers Remote Desktop technology to users from Windows Server, but with the rapid development of Internet technology, the level of Remote Desktop Connection continues to climb, remote control software has rapidly entered the people's view, More and more office workers want to use remote technology to improve efficiency. The following system home to you to explain the Windows Remote Desktop that thing.

Personally do not like the server-side program to the Windows operating system as a running platform, but, many times, under the circumstances of the situation, need to make their own program to achieve cross-platform.

In the development of the new Golden Hill game operating platform, found: Although most games, server-side programs running on Linux servers, but there are still exceptions. Several recent agents of the game, servers running on the Windows server. West Hill development of the game, server-side cluster architecture, both Windows servers, and Linux servers.

The game runs the system's Knose program, I originally developed under Linux, and later realized the compatible Windows cross-platform version.

Under Linux, Knose is the "parent-child process + instruction processing thread pool + standalone function multithreading" structure; on Windows, the Knose parent-child process structure is split into Knose_daemon.exe (service services Program) and Knose.exe (main program) , starting Knose.exe by Knose_daemon.exe.

A problem has been encountered: according to operational maintenance requirements, Knose.exe and the game server-side process launched through it requires a "window interface" that is displayed on the desktop. And Knose_daemon.exe is run in service mode, no window interface, Knose_daemon.exe start Knose.exe, the window interface does not bounce out.

To solve this problem, I used the Windows sc command in Install.bat to start Knose_daemon.exe as a system service, "type= interact type= own" set up "allow desktop to interact with services." In the native (Windows XP SP3) test, the Knose.exe window interface and the game-process window interface that started through it all bounced out.

@echo off

SC create "Kingeyesknose" binpath= "%cd%knose_daemon.exe" displayname= "kingeyes knose daemon" start= Auto type= Interact Type= own

SC description Kingeyesknose "Jinshan Game operating system Kingeyes knose daemon. "

SC start Kingeyesknose

Then publish the program to the Windows Server 2003 server, Remote Desktop Connection, found that the Knose.exe window interface always can't play out.

Later, colleagues found that the original is "Remote Desktop" caused the trouble:

The Remote Desktop client mstsc has a/console parameter that is equivalent to a local terminal monitor login,/console does not occupy a/console Remote Desktop, and Remote Desktop allows two normal connections and one console/console connection, and a normal connection and/ Console-connected desktop operations are not visible to each other, and the pop-up Knose.exe window interface is visible only if you are connected to a Windows 2003 server via the/console parameter Remote Desktop.

In Windows XP SP3 above, the/console parameter is renamed to/admin and needs to be mstsc/admin at the beginning of the system desktop-run to start Remote Desktop, connect up and finally be able to see Knose_daemon.exe started by knose The. exe program window, and the game server-side process window started by Knose.exe.