Problems deploying/managing new windows host...

[bogle]

I am running into trouble deploying windows images and I am confused about how to troubleshoot the process.

The system product is HP ProOne 600 G4 21.5-in Non-Touch AiO

First question, is this a problem to address? This comes up during the registering the host and sending its inventory to Fog.

[bogle]

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.

[quinniedid]

@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.

[bogle]

@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]

@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?

[george1421]

@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
and
lspci -nn|grep -i net

and post the results here.

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

[bogle]

@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.

[bogle]

@george1421

I am using FOG 1.5.7 and the built-in ethernet adapter.

Hopefully I can post the results in a couple of hours, I have to go setup a user so they can work from home before I can attempt to deploy again.

[george1421]

@bogle If time fixes your issue (i.e. you get to the FOS Linux command prompt on the target computer, wait 30 seconds and then the dhcp command gets an address) then you probably have a spanning tree issue with your building network switch. Installing a dumb (cheap unmanaged switch) between the target computer and building switch is the next step to debugging the problem. If the dumb switch works, then have your networking folks look at the buidling switch and make sure one of the fast spanning tree protocols are enabled (RSTP, MSTP, fast-STP, port fast, or what ever your vendor calls it).

IF time doesn’t solve your problem then we need to dig into what network adapter you have and work the driver route.

The ACPI warning we can ignore because FOG doesn’t use ACPI for imaging

[bogle]

@bogle create a virtual windows 10 pc fully customized and sysprepped it

[bogle]

@george1421 I already have the image deployed to the pc, do I need to wipe the hard drive before trying again?

[george1421]

@bogle Well if you deployed an image to the target computer is the posted image still a problem? For testing purposes, the debug deploy/capture will not impact what is installed on the disk simply because we will not start the program running on the target computer.

[bogle]

@george1421

[george1421]

@bogle So is this the same system as in the original picture? This second picture shows its working. So what changed?

[bogle]

@george1421 after I deploy the image, the host in the fog web console stays offline. I made so many customizations to the general windows 10 image that I am lost when the image is deployed. I think I need to start over with a more generic image and test extra customizations one step at a time…

[george1421]

@bogle said in Problems deploying/managing new windows host...:

the host in the fog web console stays offline

This is done by a task on the fog server. The target host name registered in FOG has to be DNS lookup able for your site. So if you named a host NYCPC01 then from the linux console prompt on your FOG server you should be “required” to be able to ping NYCPC01 and get a response. What I have seen some people do is use quick registration where the system name in FOG is its mac address which is probably not lookupable in your site’s DNS server.

[bogle]

@bogle in your opinion which method is best?

[george1421]

@bogle said in Problems deploying/managing new windows host...:

@bogle in your opinion which method is best?

That’s simple the one that works.

If you want to see accurate up down status the host name listed in FOG and the target system name needs to be the same and the FOG server needs to be able to look up the computer name in DNS.

[bogle]

@george1421 ah the hostname in FOG needs to be the fqdn right?

[george1421]

@bogle no as long as you have the fog server setup correctly you can / should use the short name.

I can tell you for linux you need to edit /etc/resolv.conf file.

You will want to configure these fields.

search domain.com ad.domain.com
nameserver 192.168.1.16
nameserver 192.168.1.17

For every dns server you want to query you should have a nameserver entry. For every DNS domain you want to search add that domain separated by a space after the search key word. Place the most likely candidates first in the nameservers and search keywords.