On demand username and password are invalid.

  1. 2 years ago

    On demand username and password are invalid.

    When I switch kernels from 3.18.1 to 4.4.3 It wont allow me to login when trying to access on demand on boot up. It states my credentials are invalid. Any Idea?

    OS: Windows 10 pro

  2. clonedeploy

    26 May 2016 Administrator

    The kernel should not have anything to do with it. Is there anything in the exception log? Can you attach your default boot menu?

  3. DEFAULT vesamenu.c32
    MENU TITLE Boot Menu
    MENU BACKGROUND bg.png
    menu tabmsgrow 22
    menu cmdlinerow 22
    menu endrow 24
    menu color title 1;34;49 #eea0a0ff #cc333355 std
    menu color sel 7;37;40 #ff000000 #bb9999aa all
    menu color border 30;44 #ffffffff #00000000 std
    menu color pwdheader 31;47 #eeff1010 #20ffffff std
    menu color hotkey 35;40 #90ffff00 #00000000 std
    menu color hotsel 35;40 #90000000 #bb9999aa all
    menu color timeout_msg 35;40 #90ffffff #00000000 none
    menu color timeout 31;47 #eeff1010 #00000000 none
    NOESCAPE 0
    ALLOWOPTIONS 0

    LABEL local
    localboot 0
    MENU DEFAULT
    MENU LABEL Boot To Local Machine

    LABEL Client Console
    kernel kernels\3.18.1
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=debug consoleblank=0
    MENU LABEL Client Console

    LABEL Add Computer
    kernel kernels\3.18.1
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=register consoleblank=0
    MENU LABEL Add Computer

    LABEL On Demand
    kernel kernels\3.18.1
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=ond consoleblank=0
    MENU LABEL On Demand

    LABEL Diagnostics
    kernel kernels\3.18.1
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=diag consoleblank=0
    MENU LABEL Diagnostics

    PROMPT 0
    TIMEOUT 50

  4. 4.4.3

    DEFAULT vesamenu.c32
    MENU TITLE Boot Menu
    MENU BACKGROUND bg.png
    menu tabmsgrow 22
    menu cmdlinerow 22
    menu endrow 24
    menu color title 1;34;49 #eea0a0ff #cc333355 std
    menu color sel 7;37;40 #ff000000 #bb9999aa all
    menu color border 30;44 #ffffffff #00000000 std
    menu color pwdheader 31;47 #eeff1010 #20ffffff std
    menu color hotkey 35;40 #90ffff00 #00000000 std
    menu color hotsel 35;40 #90000000 #bb9999aa all
    menu color timeout_msg 35;40 #90ffffff #00000000 none
    menu color timeout 31;47 #eeff1010 #00000000 none
    NOESCAPE 0
    ALLOWOPTIONS 0

    LABEL local
    localboot 0
    MENU DEFAULT
    MENU LABEL Boot To Local Machine

    LABEL Client Console
    kernel kernels\4.4.3
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=debug consoleblank=0
    MENU LABEL Client Console

    LABEL Add Computer
    kernel kernels\4.4.3
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=register consoleblank=0
    MENU LABEL Add Computer

    LABEL On Demand
    kernel kernels\4.4.3
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=ond consoleblank=0
    MENU LABEL On Demand

    LABEL Diagnostics
    kernel kernels\4.4.3
    append initrd=images\initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://10.38.42.10/clonedeploy/service/client.asmx/ USER_TOKEN= task=diag consoleblank=0
    MENU LABEL Diagnostics

    PROMPT 0
    TIMEOUT 50

  5. clonedeploy

    26 May 2016 Administrator

    Is it a problem with all machines or just this one? When you change the kernel back to 3.18 it works again? If so, the new kernel may not be compatible with the nic for that machine. Therefore it can't communicate with server and login fails.

  6. On 3.18 it works fine, let me try it out on a different model and I will get back to you on that. It does sound like a compatibility issue. Is there any way to import new kernels?

    Thank you!

  7. clonedeploy

    26 May 2016 Administrator

    You can grab the latest 4.5 here
    https://sourceforge.net/projects/clonedeploy/files/kernels/4.5.0/

    Just put them in program files\clonedeploy\tftpboot\kernels and they will show up in the web.

  8. Thanks!!!!!!!!!!!!!!

 

or Sign Up to reply!