Helo!
I try to use dude, I see it becomes still more usefull, but I have one general problem. When I run dude on Win Server 2003 and use multiuser, configuration is often cleared and overwriten by default conf, when another user logs on/off to server. I think that problem will be resolved by implementing “native” windows service, to which client applications will connect to. In other case every one win session tries to create it’s own dude service.
And best of all - if the Dude collecting data service runs on Mikrotik (or collecting data MT services will deliver them to one Win service, which one generate GUI), and client application (Win) will connect to MT service. There are two major benefits:
for me: I do not need to buy separate win machines (and licences) for my many remote sites
for you (MT developers) - only MT users will use Dude
When the configuration is cleared? Is is happening when the other users install the Dude?
Note, that one Windows computer will only have one Dude server.
I’m not absolutelly sure - I’ll check it again, but I suppose, what I done:
installed Dude (only once)
logged in twice at the same time (console and rdp)
configured dude from rdp while console session remains active (the same user, roaming profile - if it depends)
logged out from rdp
logged out from console. at this point conf has gone
I understand roaming profile fonctionality, but Dude should have one central configuration, as I understand?
Because I made lot of operations that time and I noticed this bug some time after, my description may not be precise now and there can be mistakes. One thing is absolutely sure - dude was installed only ONCE and conf was cleared while logging in or out in multiuser enviroment.
I’ll try repeat this behaviour next few days and will describe result.
regards
kj
I have lost my whole config again (with newest beta). I was working on the maps and other amin was logging in/out (from different account). Please, make an ordinary Windows service instead dudes … It is most likely second user tries to make another instance of service while logging on - in my opinion.
