Posts made by David Osinski

@DeRo93 Maybe different UEFI architectures than what your other machines are using
(Example)NOTE: There are many other UEFI architectures besides just “PXEClient:Arch:00007”.

“PXEClient:Arch:00002” and “PXEClient:Arch:00006” both should get “i386-efi/ipxe.efi” as their option 067 boot file.

“PXEClient:Arch:00008”, “PXEClient:Arch:00009”, and “PXEClient:Arch:00007” should get “ipxe.efi” as their option 067 boot file.

“PXEClient:Arch:00007:UNDI:003016” should get “ipxe7156.efi” this file is specific to the Surface Pro 4.

@DeRo93 Please try following this article to setup your DHCP for UEFI/Legacy
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

@Scott-Boucher This issue is definitely not fog related. I have seen this on multiple occasions and usually comes down to a UEFI machine with a SSD. either try disabling sleep is the advanced power settings, try disabling hibernation, Disable fast boot in bios, or theres a “turn off hard disk after” setting that you may want to see if thats disabled. I have linked this issue to usually the computers bios misidentifying the SSD as a HDD making windows use the wrong things to sleep/hibernate.

If you are using a HDD then try to see if there is a bios update for your machine and/or driver updates from the manufacturers website. Good Luck, this problem is proprietary to your type of device. Do some research in that and also look at disabling the settings.

I have also learned that 5400 rpm 2.5" HDD are absolutely horrible. If that is what you have within those machines, try to put in a SSD for a test and see if you get the same results.

@agray You said you set the machine to legacy, and secure boot is off, but
1 did you enable CSM support?
2 did you change your boot order?
Please take a picture of your BIOS/UEFI settings so i can help as well.
Im interested in your boot page, CSM, boot order, and secure boot pages

@Jay-Bosworth
Jay on a side note while the guys are trying to troubleshoot the problem with services, ect., can you go ahead and try to spin up a new virtual machine and load widows from scratch. Mabey every try audit mode again but dont disable services (i never do and it works perfect) like you mentioned in your original post. Just install fog client and %WINDIR%\system32\sysprep\sysprep.exe /generalize /shutdown /oobe
If your running a unattended.xml, please make sure your not doing post scripts for the test. Just try to make it as bare bones as possible. This will test to make sure
1 your fog enviroment is running functionally
2 you are building your windows images correctly

If it works, you need to evaluate on how your building your images.
If it doesnt work, then im going to leave it to the other guys

@Jay-Bosworth
Please log into fog and go to hosts --> pick your host --> go to the Active directory tab
please confirm there is a check next to “Join Domain after deploy” on the host that is in question

What version of fog are you running?
What version of fog client are you running?

@george1421

George/Tom…you are genius’s

I am overcomplicating things. To not define address’s was the answer. Multicast works on my network as i said earlier because i can VLC RTP stream just fine. I have routers setup to do PIM SM. Specifying a multicast rdv was my downfall.

All of you are amazing. Please keep up the great work!

@george1421
I chose this IP address due to the documentation on https://wiki.fogproject.org/wiki/index.php/Multicasting

The direct line where i took this information was
If your image is partclone

udp-receiver --nokbd --portbase 9000 --ttl 32 --mcast-rdv-address $fogserverip | \
partclone.restore --ignore_crc -O /dev/sda<filenumber> -N -f 1

Being that said, i will definately try 239.10.10.74

@Sebastian-Roth
i used VLC to run a RTP stream off the servers to test.

@Sebastian-Roth
Here is what i ran on the server

udp-sender --interface rope --min-receivers 1 --max-wait 600 --mcast-rdv-address 10.10.10.74 --portbase 56854 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/W10EDULenovoFlex3x64/d1p1.img

Here is what i ran on the client

udp-reciever --nokbd --portbase 56854 --ttl 32 --mcast-rdv-address 10.10.10.74 > /dev/null

I am getting the same results, nothing in coming through.
Im going to be a little more specific to help out.
Im running on a physical Dell emc server with 4 Nics bonded together. I can see all multicast traffic from other servers on the same vlan just fine, This server just seems to not be broadcasting its multicast session to the switch
I run

 ip maddr

but am not getting any other multicast on the server except 224.0.0.1
I boot the client and join the multicast session i can see that the client is trying to join a multicast session on the switch.

I have other windows servers nic teamed together on the same vlan without a problem on multicast. It just seems to be Cento7 w/fog.

The receiving client is on another vlan than the server.

I would like to also point to attention that i dont know if its a bond issue or a issue with this particular server/settings

(Display igmp-snooping Switch Client is on)

VLAN 2: Total 11 entries.
  (0.0.0.0, 234.10.10.74)
    Host ports (1 in total):
      GE2/0/7

(Display igmp group Switch Server is on)

Vlan-interface1010(10.10.10.254):
  IGMP groups reported in total: 2
   Group address   Last reporter   Uptime      Expires
   239.255.255.250 10.10.10.90     9w:1d       00:04:19
   239.255.255.254 10.10.10.20     1w:1d       00:04:19

Server ip address is 10.10.10.74, its not joining the multicast group.

@george1421 said in Multicast off of bond:

ip addr show

[root@tisd-fog01 ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master rope state UP qlen 1000
    link/ether d4:be:d9:b1:19:cb brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master rope state UP qlen 1000
    link/ether d4:be:d9:b1:19:cb brd ff:ff:ff:ff:ff:ff
4: em3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master rope state UP qlen 1000
    link/ether d4:be:d9:b1:19:cb brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master rope state UP qlen 1000
    link/ether d4:be:d9:b1:19:cb brd ff:ff:ff:ff:ff:ff
6: rope: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
    link/ether d4:be:d9:b1:19:cb brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.74/24 brd 10.10.10.255 scope global rope
       valid_lft forever preferred_lft forever
    inet6 fe80::32e0:22c8:7b56:41c9/64 scope link
       valid_lft forever preferred_lft forever

(i dont abide by your linux bond0 rules…)

also heres this

DEVICE=rope
BONDING_OPTS="miimon=100 updelay=100 downdelay=2000 mode=balance-rr"
TYPE=Bond
BONDING_MASTER=yes
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=rope
UUID=5b88e67a-093b-491b-9540-c172fb9f726d
ONBOOT=yes
IPADDR=10.10.10.74
PREFIX=24
GATEWAY=10.10.10.254
DNS1=10.10.10.11
DNS2=10.10.10.12
DOMAIN=terrellisd.lan

“/etc/sysconfig/network-scripts/ifcfg-bond-rope”

[MOD Note] Fixed formatting for readability. -Geo

We’ve been using fog for years and am just now trying to get multicast to work correctly. I use 4 ethernet nics bonded together in CentOS 7. I start the multicast session and look at the logs:

"/usr/local/sbin/udp-sender --interface rope --min-receivers 1 --max-wait 600 --mcast-data-address 239.255.20.105 --mcast-rdv-address 10.10.10.74 --portbase 54232 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/W10EDULenovoFlex3x64/d1p1.img;/usr/local/sbin/udp-sender --interface rope --min-receivers 1 --max-wait 10 --mcast-data-address 239.255.20.105 --mcast-rdv-address 10.10.10.74 --portbase 54232 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/W10EDULenovoFlex3x64/d1p2.img;/usr/local/sbin/udp-sender --interface rope --min-receivers 1 --max-wait 10 --mcast-data-address 239.255.20.105 --mcast-rdv-address 10.10.10.74 --portbase 54232 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/W10EDULenovoFlex3x64/d1p3.img;/usr/local/sbin/udp-sender --interface rope --min-receivers 1 --max-wait 10 --mcast-data-address 239.255.20.105 --mcast-rdv-address 10.10.10.74 --portbase 54232 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/W10EDULenovoFlex3x64/d1p4.img;"

As you can see the command is listed 4 times. If i change the interface in either multicast settings or nfs server, it still uses the interface “rope”

I dont know if this is my problem but my clients stay at the image is starting within part clone. I looked in your troubleshooting guide and ran the MySQL commands, no effect.
I have ran a RTP stream from my vlan to the server vlan, Multicast streaming works. We use HP Comware devices.

My next choise if you dont have anything is to either take an interface out of the bond and set it up as the only interface to test it, or build another fog server, only using 1 nic, for testing purposes.

@Wayne-Workman According to Fortinet, this seems to be an incompatibility issue between the two clients. If you install Fog client alone, It works. Once you install forticlient, it seems to break fog client. Even if you disable forticlient completely, and stop the service. They think it may be a driver issue. I have an open ticket with fortinet that they are researching the issues.

After fighting with the client for about a week now, it seems to be our antivirus/webfiltering client (Forticlient) that is causing the problems. If i completely remove forticlient, it works just fine. I have been on tech support with fortinet for the past few days trying to figure this out. If I turn off all services and shutdown forticlient, it still happens. The only way i can get it to work is actually uninstalling it. So, this leads me to revert back to the old fog client and that works like a champ still. Thanks for all your suggestions. I did try what wayne said but still didnt work after that.

@Wayne-Workman
This does not seem to be the reason for the issue. as stated the client is off. I only brought the forticlient antivirus to your attention because at the beginning of the log it says authentication error. This still does not fix the first issue. It will still not join active directory or do snapins. Tom wanted my to disable snapins but my client will still not join active directory.

@Tom-Elliott
I turned off the machine, disabled snapins and turned the machine back on. Here is the log again. 0_1479413974844_fog.log
You may notice that i am getting an authentication error until 2:16. I found out that it is our antivirus program (Forticlient) that causes that. once i disabled and shut it down, you can see that its back to the normal messages.

@Wayne-Workman
That is correct Wayne. The ip address is 10.10.10.74.

I only have 2 hosts right now. The VM on which i created the image and a physical client that i am testing. I put both of them into a group and reset encryption. Still nothing

Server

• FOG Version: 1.3.0-RC-23
• OS: Ubuntu server 16.04

Client

• Service Version: 0.11.5
• OS: Windows 10 Pro x64

Description

I have bee using fog version 1.2 for years. I have recently built a new server upgraded to 1.3 for the UEFI support and its working great! im able to image just fine. My problem if that the fog client is not working on joining the domain or snapins. ill post my fog.log. It seems like the the error is tied to the communication url? I’ve looked it over but am by no means an expert. I have looked at other posts that suggest reseting encryption data but that didnt work.
0_1479407520104_fog.log

Thanks for all you guys do!