Hello Oleg,
I have two suggestions that might be useful for future releases of OEP, in terms of administration:
1) Sometimes I want to administer my projects, without running scheduled downloads. Unfortunately, when it?s the time of a scheduled download, it begins.
The suggestion is to have a button in the button-bar to start-stop the scheduler (i.e. stop all scheduled downloads).
2) I use OEP in a Windows 2003 machine, and administer it via Terminal Server. The problem is that each session of Terminal Server has it?s own desktop, and I cannot "guess" if OEP is still/already running in another session. If I run OEP and it is already running in another session, I get error messages.
The suggestion is that OEP should set a flag meaning that "it is running on this machine", so If you try to execute it again in the same or different session, it would not load.
Best Regards,
Pablo.
I have two suggestions that might be useful for future releases of OEP, in terms of administration:
1) Sometimes I want to administer my projects, without running scheduled downloads. Unfortunately, when it?s the time of a scheduled download, it begins.
The suggestion is to have a button in the button-bar to start-stop the scheduler (i.e. stop all scheduled downloads).
2) I use OEP in a Windows 2003 machine, and administer it via Terminal Server. The problem is that each session of Terminal Server has it?s own desktop, and I cannot "guess" if OEP is still/already running in another session. If I run OEP and it is already running in another session, I get error messages.
The suggestion is that OEP should set a flag meaning that "it is running on this machine", so If you try to execute it again in the same or different session, it would not load.
Best Regards,
Pablo.
1. Yes, we plan to improve the scheduler to add more features, pause/resume and ability to view missed schedules. But it will take some time to do. It will be not yet included in 5.0 version.
2. It can be a problem, because newest Windows systems do not allow access to common areas, like Registry HKEY_LOCAL_MACHINE key, etc. with no administrative rights.
So, I am not sure about this. However one way to check if Offline Explorer is running is to browse to the address:
http://127.0.0.1:800/
If the page loads, then it already runs on your computer.
Best regards,
Oleg Chernavin
MP Staff
> 2) I use OEP in a Windows 2003 machine, and administer it via Terminal Server. The problem is that each session of Terminal Server has it?s own desktop, and I cannot "guess" if OEP is still/already running in another session. If I run OEP and it is already running in another session, I get error messages.
> The suggestion is that OEP should set a flag meaning that "it is running on this machine", so If you try to execute it again in the same or different session, it would not load.
>
> Best Regards,
> Pablo.
>
2. It can be a problem, because newest Windows systems do not allow access to common areas, like Registry HKEY_LOCAL_MACHINE key, etc. with no administrative rights.
So, I am not sure about this. However one way to check if Offline Explorer is running is to browse to the address:
http://127.0.0.1:800/
If the page loads, then it already runs on your computer.
Best regards,
Oleg Chernavin
MP Staff
> 2) I use OEP in a Windows 2003 machine, and administer it via Terminal Server. The problem is that each session of Terminal Server has it?s own desktop, and I cannot "guess" if OEP is still/already running in another session. If I run OEP and it is already running in another session, I get error messages.
> The suggestion is that OEP should set a flag meaning that "it is running on this machine", so If you try to execute it again in the same or different session, it would not load.
>
> Best Regards,
> Pablo.
>