Problems deploying/managing new windows host...

  • @quinniedid

    I register the host and after deploying the image the status is unknown under host management.

    Windows doesn’t activate like its supposed to and the hostname doesn’t change.

  • Moderator

    @bogle What version of FOG are you using? Are you using the built in ethenet adapter or a usb dongle?

    If you manually register the target computer, then schedule a task capture or deploy (don’t care) but before you schedule the task tick the debug checkbox and then pxe boot the target computer. After a few screens of text where you need to clear with the enter key you will be dropped to a linux command prompt. Don’t worry if you see the same error messages as in your picture, we will be testing something.

    key in the following: (note you need to do these two commands in the first 20 seconds of getting a linux command prompt.
    ip addr show
    lspci -nn|grep -i net

    and post the results here.

    Wait about 30 seconds and then issue this command
    /sbin/udhcpc -i eno1 --now

  • @quinniedid

    Did you just customize one hp pc and capture that image or create a virtual windows 10 pc fully customized and sysprepped it, or make a general window 10 virtual machine and customize it after deployment?

  • @quinni

    udhcpc: started, v1.29.3
    udhcpc: sending discover
    udhpc: sending select for [host ip]
    udhcpc: lease of [host ip] obtained, lease time 691200
    deleting routers
    adding dns x.x.x.x
    adding dns x.x.x
    shh-keygen: generating new host keys: xxxxxxxxxx
    Starting sshd: ok

    • Running pst init scripts…done

    Fog Client Registration screen loads…

  • @bogle We are a pure HP shop and we have seen these errors before. Just as long as you are able to register and deploy/capture images I wouldn’t worry about the errors, I could be wrong if there is truly an issue but in our experience it shouldn’t really matter. What I would like to know is what is the error output after “Starting eno1 interface…?” Anything?

    Now if you are able to register the host in FOG I would recommend going to that specific host in the FOG UI, under the General tab and setting Host Kernel Arguments to apci=off and try to deploy again and see if that helps.

  • I am going to create a new golden image and try to generalize as much as possible. Is it easier to not use sysprep? I only have around 200 computers and usually deploy 5 to 10 computers at a time.