14 Comments

  1. Kurt Johnson
    May 5, 2019 @ 1:39 pm

    LO 3 Console does not scale for HD displays (3840×2160) when logged in remotely through Windows Server Experience Dashboard. Properties windows are especially hard/impossible to use.

    Reply

    • Martin Rothschink
      May 5, 2019 @ 6:16 pm

      Hi Kurt, thanks for reporting. Will look into the issue on Monday.

      You are connecting form a local High-DPI system via RDP to a remote server, correct? Are you running Dashboard remotely or the Lights-Out Console?
      As a workaround, can you install the Lights-Out console on your local machine and give it a try?

      Regards
      Martin

      Reply

      • Kurt Johnson
        May 6, 2019 @ 2:35 am

        Hi Martin,
        Yes, a high DPI client and opening the LO “tab” from the remote (WSEE) dashboard. Also, LO 3 remembers that previous window sizing (stays really small) and displays that way on another client that is running a more normal 2560×1600 DPI display.
        I assume I install the console directly from the LO website … does the program need to be removed after I’ve tested?

        Reply

  2. Kurt Johnson
    May 6, 2019 @ 3:17 am

    Hi Martin,

    I installed the console on my high DPI device and the window text and properties boxes look normal (good). The cursor gets really small when I hover over the links in the Status (left) pane on the Status tab, but is normal size when I hover over links in the other panes (Recording, Savings, etc.).
    I should clarify my last post; the *window* size is correct, but the window *contents* (text, cursor) is scaled small.

    I assume I should uninstall this program as I manage my clients from the Server Console, correct? I don’t know how to manage the client from a local console… 🙂

    Reply

    • Martin Rothschink
      May 6, 2019 @ 9:10 am

      Kurt,

      you can manage your clients from the local console. On startup, select the name of your server and connect to it. You can run Dashboard and Console parallel, no need to uninstall.

      I will look into the RDP scaling issue and try to fix that asap.

      Reply

  3. Kurt Johnson
    May 7, 2019 @ 2:45 am

    Hi Martin,

    When I connect the console installed on my client to the server, LO tells me I can only have one computer using my existing license. When I remove the license LO on the client reverts to a trial. Do I need TWO licenses to use the LO console to manage ONE server from a client AND the server; that is, to manage locally on the client OR from the WSEE Dashboard on that same client?

    Reply

  4. Kurt Johnson
    May 9, 2019 @ 6:13 am

    Hi Martin,

    Here is my confusion, you asked/stated previously, “As a workaround, can you install the Lights-Out console on your local machine and give it a try?” and “You can run Dashboard and Console parallel, no need to uninstall.”

    I misunderstood that this suggestion implied I should *uninstall* the Console on the server if I intended to run it permanently from the client.

    In any case, as I stated earlier, the text in the Lights-Out console when run from the client appears normal, but when run from the server Dashboard (console installed on the server) is scaled too small.

    Reply

    • Martin Rothschink
      May 9, 2019 @ 9:09 am

      Kurt,

      The console is an optional component on the download page of Lights-Out (via http://server:7782). You can install the console on any client computer to manage Lights-Out on the server. Sorry I didn’t express myself clearly enough.

      The scaling issue has been fixed in update 3.0.1 which will be published later today.

      Regards
      Martin

      Reply

  5. Kurt Johnson
    May 10, 2019 @ 8:37 am

    But you are not permitted to have the console installed on BOTH devices at the same time, correct?

    Reply

    • Kurt Johnson
      May 10, 2019 @ 8:56 am

      BTW, build 4433 has fixed the high DPI problem for me, thank you.

      Reply

    • Martin Rothschink
      May 12, 2019 @ 4:39 pm

      You can install and use the separate management console on as many computers you want. The separate console installer is available on the internal download page (via http://server:7782).
      The full installer for the server also includes the console. But that should only be installed once on the server computer.

      Martin

      Reply

  6. Warren Poulson
    November 4, 2019 @ 10:39 pm

    Hello Martin,

    If I’m posting this request for assistance incorrectly, please let me know.

    I just installed LO 3 on my server; then, through the http://server:7782, I installed both the console and client software to two other computers. The installation completed successfully; however, while the two clients show up under the “Network Devices” tab, they do not show up on the “Computers” tab on the Server’s LO Dashboard or the clients Console. Only the Server shows up in the “Computer’s Tab. My clients are both showing as “Not Managed” and I don’t have a managed option under computer tasks.

    Also, when I click on the LO Client on the task bar of the Windows 7 client computer, the LO Client is X’d out and says “Server is offline.” This is on both my clients, though if I right click on the client and click Settings>Connect to Server, it shows I’m connected to server, when I do this from either client machine

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *