24x7 Scheduler 4.2 Multi-Platform management on windows

I am having a few difficulties in the differences between our old 24x7 Scheduler for Windows environments and some new 24x7 Scheduler Multi-Platform edition environments I'm building. I'm wondering if I just need to go back to the windows automation suite and quit fighting with the multi-platform edition.

I need to run the scheduler as a windows service. That piece of it is easy enough to do. But I'm finding it difficult to manage the scheduler once this has been done. I've read through the forums and have seen references to using the 24x7 Remote Control to connect to the instance running as a service. However, from what I can gather this appears to only be an option when using the Automation Suite and is not available with the multi-platform edition. I see there is a remote control API that can be enabled. But I'm purely looking for a management interface.

With the old automation suite I could open up an interactive session of the scheduler on the same server which would detect that there was already an instance of the scheduler running as a service. It would disable the timer in the interactive scheduler and continue to allow the service instance to handle the running of jobs. This does not appear to be the case wit the multi-platform edition. It seems to just open another complete instance of the scheduler. I'm not sure what kinds of conflicts this might produce but it doesn't seem like a good thing.

And finally, the latest thing I've noticed is that log files do not appear to be maintained over restarting the service for 24x7. The options have been configured to not clear the logs on startup. And this appears to work just fine when using the interactive run mode. But each time the service is restarted all logs disappear.

So, as stated at the beginning of this, am I just trying to do something with the wrong product? Am I missing something or should I go back to the automation suite? The only reason I went down this path is this is what our purchasing department got for me.

Here are the things that can help you

1. Both schedulers support web-based graphical interfaces. The web-based interfaces can be and should be used when the scheduler is running as a service on Windows or service/daemon process on *nix systems. The also support concurrent multi-user and multi-server access to the scheduler(s).

2. 24x7 MP supports command line interface that can be used in all modes interactively and also can be used to script out common administrative type tasks using batch files. 24x7 Win. doesn't support this command line interface

3. 24x7 Win supports graphical remote console (24x7 Remote Control), 24x7 MP doesn't support it.

---

Regarding the logs, I'm not quite sure why logs are deleted? Are you sure they are deleted and not renamed with a date or numeric suffix?
Are you looking in the right directory for log files?