I've a problem with my server settings possibly... Previleges etc.

ok thanks

Remaining problems:

1. If log file of MT4 is not managed properly, MT4 exits immediatly. This is why it can not run as NT Schduled Task . Here, "NT Wrapper" is suitable to manage MT4 logs. I'll explain details soon.

2. "NT Wrapper" succesfully runs MT4, while it's main process is under SYSTEM, as an NT service. But the MT4 process under Administrator is not visible / desktop interactive yet. Here I need help from a windows server guru explaning this sentence:

"Administrator" user will require specific privileges to allow your application to interact with the desktop"... I could not find how to do this yet...

Possible solution exists in "NT Wrapper Pro" which includes remote NT services support...

(picture is from a different tool, which could not manage MT4 log and MT4 immediatly exits.)

Here is some possible solution, reading...

http://www.duodata.de/ntwrapper/help/index.html

Attached Images

service.GIF (4.6 KB, 367 views)

...Also some applications do not restore their tray icon when a user logs on. Those applications should be fixed by their developers to restore the tray icon each time the taskbar is (re)created


MT4 possibly is one of them. NT Wrapper succesfully re-starts MT4 after boot, but MT4 itself can not add it's tray-icon, on automatic boot.

**********************************************
Message to MT4 Developer: You need to catch some windows messages and make log files as option. So MT4 will be succesfully restart as NT service or Scheduled task
---------------------------------
It's an easy task for the developers of such programs to provide a command line switch e.g. "-service" and handle some window messages like the WM_QUERYENDSESSION and WM_ENDSESSION in GUI applications or signal CTRL_LOGOFF_EVENT in console based programs in a different manner when the program is running in service mode
***********************************************

For now, I'm thinking of a small exe that will discover all MT4 processes and add them to tray-icon and activate their windows... If someone can do this exe, will solve everything. I forget these things. NT Wrapper + ShowMT4All.exe will solve everything.

ShowMT4All.exe will find all terminal.exe processes or MT4 main windows and send them a restore message...

Thanks

last theory is wrong. because it seems each remote connected user has it's own process space in this architecture. even spy tool can not find the window of remotly executed MT4. I need to learn one more deep level.. remote connections and their izolated process spaces...

c4n, can you please explain us your VPS security settings if you make special changes? and your VPS provider?

remaining problem is "Concurrent Remote Desktop Sessions". "NT Wrapper Lite" succesfully restarts MT4 process, even managing external log files, from it's SYSMTEM process. But when I login using RDP, I get another session and can not see MT4, since it is in another session. I need to see "NT Wrapper Pro" for this problem.

Any guru to solve this?

thanks.


From Arno Garrels, "NT Wrapper" , support@duodata.de
-----------------------------------------------------------------
Any interactive service can interact with session0 desktops
only. If you login remotely thru a TMS session you get session1
or higher by default (same with Fast User Switching and
the second local user).
However since Win2003 server there's an option to login
to session0 remotely
----------------------------------------------------------------
We will try to login "session0" using RDP. So, "NT Wrapper" well be sweet...


from http://forums.firedaemon.com/viewtop...8d555a5f2d895f
-----------------------------------------------------------------
In the case of services, they have no implicit session (since no one logged in) so they are bound to session 0 by default.

Hence, if you run services that Interact with the Desktop the only session in which you will see any GUI component is session 0. That is why you need to instruct the RDP client to connect to the console session via:

mstsc /v:server /console

So in regard to your issue:
- you are seeing Administrator logged into the console (session 0)
- you are seeing Administrator logged into the first available Terminal Services Session (eg. session 1).
-----------------------------------------------------------------

CB: If you can do, connect to VPS without using RDP, directly to console/session0. This solves everything about MT4 auto-restart. (RDP again really stupid thing from microsof againt. terrible design, users isolated, connections isolated, even your root session is not your.)
Many soltions here works withour RDP. With RDP, we need to learn how to get "session0" from our provider...

http://blog.throbs.net/CommentView,g...dd2079752.aspx

http://www.code4ward.net/cs2/files/9/rts1/entry12.aspx

all are valid for windows 2003 server SP1. on vista, session0 policies are totally differen b.of security decisions..

I'm asking my host provider -VPSLand- for "session0" (console logon). When it is allowed, "NT Wrapper" perfetly solves everything for MT4 auto start
----------------------------------------------------------
mstsc /v:server /console (or use RoyalTS instead of MS terminal service, check console option there)

So, we need to ask our windows 2003 VPS service provider, "session0: console" logon rights. Than everything is fine with "NT Wrapper Lite"

http://forum.ultravnc.info/viewtopic...&view=previous
--------------------------------------------------------------
The biggest disadvantage is that the service can only interact with session0.

Until win 2000, the console always was session0. But all later version
can have a console session other the 0.
XP: fast user switching
win2003: After a RDP connection ????
Vista: the console is never session0

As the service ("NT Wrapper" that will start MT4) can only interact with session0. In XP and win2003 you need to force the console to session0. This can only be done by disconnecting the current console user and restart a new console. ( microsoft here)
Not a proper way....but the only possible.

Vista is still a big challenge, as service will not work at all.

http://help.maximumasp.com/SmarterTi...?articleid=979
-------------------------------------
Known issues with the current Virtuozzo release:

You are not able to RDP into the console session of a Virtuozzo instance ( them also)
for example “mstsc /console”
This is a known issue and should be resolved in the next version.
-------------------------------------

"NT Wrapper Lite" is perfectly starting MT4 instances in "session0" (console)
But virtuozzo do not support "session0" connection yet. When they support, I will be able to see MT4 screens running in session0, auto-started by "NT Wrapper".

On the other hand, if your system is not windows 2003, and you are not related with "Virtuozzo", many solutions here is already working.

(So, the young chair-man understands that, there are many dependencies/design problems exists in the real world.)

- alternatives to virtuozzo? we need VPS w/o virtuozzo. since it can not give console / session0 RDP logon. (root of your VPS is not your's in their design yet. and NT service can interact only session0 until windows 2003. vista is not clear yet)

- Metaquotes removes all external resource dependencies (files, etc.) than we start MT4 as schduled task

- some other software that will simulate GUI from session0?

- some other ideas?

Attached Images

VPS6.GIF (30.8 KB, 370 views)

Here pictures show the result. when "virtuozzo" allows me to connect console session, I'll RDP with / console option to watch MT4's. For now, MT4 interface in "session0" will not be visible with (RDP + virtuozzo)

Your case may be diffirent, depending on your OS (2003 server/ 2000 server / XP Server / Vista etc.) and your virtualization stuff (virtuozzo). If you can connect to your VPS "session0" directly, using PCAnywhere.. remotePC etc then this comfort allow you to watch MT4's running in "session0". This is not allowed "virtuozzo" yet (or my service's virtuozzo is old.)

Attached Images

	VPS1.GIF (26.9 KB, 283 views)
	VPS2.GIF (29.9 KB, 256 views)
	VPS3.GIF (31.4 KB, 254 views)
	VPS4.GIF (31.4 KB, 246 views)
	VPS5.GIF (31.3 KB, 259 views)