Problems deploying/managing new windows host...

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

[bogle]

@george1421 Ok I got that correct.

[george1421]

@bogle So from the linux command prompt on your FOG server can you ping the devices by their windows host names? Not the FQDN name?

[bogle]

@george1421 yes

[bogle]

@bogle Even though windows firewall was disabled for domain, I added fog client to exclusion list for all network profiles, then opened inbound/outbound traffic on port 445. Can see the newly deployed computer now.

I had to do a “reset this pc” after deployment to fix make the computer run right though…

[bogle]

@bogle I did a “reset this pc” and can see the host online. I created a task to reboot the computer and it didn’t do anything.

[george1421]

@bogle The FOG server talks to the target computer via the FOG Client/service. That service has a check in interval that is set in the fog settings. So the default may be 5 minutes (300 seconds), so if you issue a task to the target computer it could take up to 5 minutes before the target system reacts.

Also on the fog up/down indicator it doesn’t use a ping, but a connect to port 445 to confirm the system is up or not. If your windows firewall is blocking connections to port 445 then fog will assume its down.