Posts made by Wayne Workman

Use the installer to delete all partitions, and have the installer auto-create the required ones for you.

Do these machines support UEFI ? Is it enabled in their firmware settings?

Just ran a capture on our DHCP server and the underlying NICs for our virtualized FOG server.

I’ve confirmed it gets the right options in DHCP, asks for the ipxe.efi file, and it looks like it gets the file.

So… This comes down to the files themselves.

[url=“/_imported_xf_attachments/1/1856_UEFI_Communications.zip?:”]UEFI_Communications.zip[/url]

In Fedora 21 Server, I’ve found it must check the validity of the installation media before proceeding. You must allow it to do this, and not skip it. It takes about 5 - 10 minutes.

In Fedora 21 Workstation, it does not do this check. And I know workstation installs just fine in Hyper-V.

The installer for the newer developmental versions will upgrade your machine for you.
It will use previous settings, and tell you to visit the Web GUI to update the database. Errors during that can be expected, but are non-impacting. They are related to supporting upgrading from much older FOG versions.

[url]http://fogproject.org/wiki/index.php/SVN[/url]

The issue is resolved. The above post fixed it.

Tom helped me.

I did this in my browser for the problem computer:
[CODE]http://10.2.1.10/fog/service/hostname.php?mac=<macaddresshere>[/CODE]

and found that the ADPass was really, really, really long, and therefore really, really, really wrong.

I ran that same address for a working computer and found that the ADPass was correct.

So, in the database on the FOG server, Tom had me do this:

[CODE]mysql -u root fog[/CODE]
[CODE]update hosts set hostADPass=‘<yourgoodpassword>’ where hostADPass !=‘<yourgoodpassword>’;[/CODE]

This affected the exact number of computers in this particular computer lab. Tom thinks it’s solved now. I’m testing it at the moment.

Reinstalled the FOG client totally on this problem device. Re-uploaded a new image… Made sure “Join AD” was enabled. Deployed the image back to the system… no domain join…

Here’s the FOG client log:

[CODE] 4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:35 AM FOG::MODDebug Reading config settings…
4/9/2015 8:35 AM FOG::MODDebug Reading of config settings passed.
4/9/2015 8:35 AM FOG::MODDebug Starting Core processing…
4/9/2015 8:35 AM FOG::MODDebug Operating System ID: 6
4/9/2015 8:35 AM FOG::MODDebug Operating System Minor: 1
4/9/2015 8:35 AM FOG::MODDebug MAC ID 0 1C:C1:DE:91:D6:0A
4/9/2015 8:35 AM FOG::MODDebug MAC POST String: 1C:C1:DE:91:D6:0A
4/9/2015 8:35 AM FOG::MODDebug No user is currently logged in
4/9/2015 8:35 AM FOG::MODDebug Hostname: r0227502701WLMB
4/9/2015 8:35 AM FOG::MODDebug Attempting to open connect to: http://10.2.1.11/fog/service/debug.php
4/9/2015 8:35 AM FOG::MODDebug Server responded with: Hello FOG Client
4/9/2015 8:35 AM FOG::MODDebug Module has finished work and will now exit.
4/9/2015 8:35 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:35 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::GUIWatcher Dispatch Failed!
4/9/2015 8:36 AM FOG::UserTracker Event: LOGIN for r0227502701WLMB\tech
4/9/2015 8:36 AM FOG::UserTracker Unable to notify server because the MAC address was not correctly formated.
4/9/2015 8:36 AM FOG::GUIWatcher Message found, attempting to notify GUI!
4/9/2015 8:36 AM FOG::PrinterManager New user detected: r0227502701WLMB\tech
4/9/2015 8:36 AM FOG::PrinterManager Waiting for tray to load…
4/9/2015 8:37 AM FOG::GUIWatcher Dispatch OK![/CODE]

[quote=“Chris Wells, post: 45232, member: 28938”]I was going to try to do that or better develop the Snapin management.[/quote]

May the force be with you.

So, I tested another model with a known-good image and it joined the domain just fine…

I’ve been working on this for some days now, on and off. I’ve not had any success, thought it was time to make a thread.

FOG - r3225
Fedora workstation 21 - fully updated about a week ago.

So, I’m using Windows Server 2012 for DHCP and have control over it. These two models boot fine in BIOS mode with undionly.kpxe , but when switched to UEFI they will not boot.

I’ve changed option 067 to:
ipxe.efi
snp.efi
snponly.efi

It seems like the computers aren’t even getting the files. There are no specific errors that they give. They just sit there for a minute or two saying “Initializing devices…” and then fail.

I plan to install wireshark on our DHCP server and capture these packets, and do the same on the FOG server.

[quote=“Tom Elliott, post: 45204, member: 7271”]Because the boot file is undionly.kkpxe I believe you need to also have undionly.kkpxe.0 in the tftpboot folder.[/quote]

undionly.kkpxe.0 ?? or cp undionly.kkpxe undionly.0 ?
I thought I was using undionly.[B][U]kpxe[/U][/B] ?

Upgraded to 3225.

Still no change, but there was a change in traffic. tcpdump said 13 or so packets were captured, but the filter only stored 5 of them. I’ve also reboot the FOG server too, and tried again.

New ltsp.conf file:
[CODE]port=0
log-dhcp
tftp-root=/tftpboot
dhcp-boot=undionly.kpxe,10.0.0.3
dhcp-option=17,/images
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt=“Press F8 for boot menu”, 3
pxe-service=X86PC, “Boot from network” undionly
pxe-service=X86PC, “Boot from local hard disk”, 0
dhcp-range=10.0.0.3,proxy[/CODE]

[url=“/_imported_xf_attachments/1/1854_issue.pcap.zip?:”]issue.pcap.zip[/url]

In the ltsp.conf file,

I am eyeballing this line:

[CODE]dhcp-option=vendor:PXEClient,6,2b[/CODE]

I don’t think it’s right… How can I bypass it so that it just gives undionly.kpxe to everything?

According to Wireshark, my FOG server’s dnsmasq service only sends out one packet…

[IMG]http://s29.postimg.org/56b9s2qp3/Screenshot_from_2015_04_08_17_30_15.png[/IMG]

I started the below command, booted the target computer, waited till it failed and started booting windows, then killed the command. Says 5 packets were captured.

I’ve got the feeling that 5 packets doesn’t cut it…

[CODE][root@localhost ~]# sudo tcpdump -i enp2s0 -w issue.pcap udp
tcpdump: listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
stop
^C5 packets captured
5 packets received by filter
0 packets dropped by kernel
[root@localhost ~]# [/CODE]

Think it has anything to do with the adapter name? It’s very unusual… enp2s0

Packet capture file is attached.

EDIT: getting wireshark now…

[url=“/_imported_xf_attachments/1/1853_issue.pcap.zip?:”]issue.pcap.zip[/url]

Removed the dhcp option 66 and restarted dnsmasq… still no luck…

I booted the machine up fully and used the command prompt to grab the file.

[CODE]C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix  . :
    IP Address. . . . . . . . . . . . : 10.0.0.15
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.0.1

Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix  . :
    IP Address. . . . . . . . . . . . : 10.198.1.6
    Subnet Mask . . . . . . . . . . . : 255.255.255.252
    Default Gateway . . . . . . . . . : 10.198.1.5

C:\Documents and Settings\Administrator>tftp 10.0.0.3 get undionly.kpxe c:\undio
nly.kpxe
Transfer successful: 89460 bytes in 1 second, 89460 bytes/s

C:\Documents and Settings\Administrator>cd c:\

C:>dir
Volume in drive C has no label.
Volume Serial Number is FC56-C26E

Directory of C:\

04/03/2015 01:26 AM 0 AUTOEXEC.BAT
04/03/2015 01:26 AM 0 CONFIG.SYS
04/04/2015 02:23 AM <DIR> dell
04/03/2015 01:28 AM <DIR> Documents and Settings
04/03/2015 01:23 AM <DIR> Inetpub
04/04/2015 02:25 AM <DIR> Intel
04/03/2015 10:24 PM <DIR> Program Files
04/08/2015 04:37 PM 89,114 undionly.kpxe
04/03/2015 10:33 PM <DIR> WINDOWS
3 File(s) 89,114 bytes
6 Dir(s) 61,086,072,832 bytes free

C:>[/CODE]

undionly.0 is also present.

[CODE][root@localhost tftpboot]# ls
boot.txt ipxe.efi ipxe.pxe snponly.efi undionly.pxe
default.ipxe ipxe.kkpxe memdisk undionly.0 vesamenu.c32
foginstall.log ipxe.kpxe pxelinux.0.old undionly.kkpxe
i386-efi ipxe.krn snp.efi undionly.kpxe
[root@localhost tftpboot]# [/CODE]

I’m going to do a TCP dump as Uncle Frank suggested… It should shed some light on what’s happening…

Oh, and so you guys don’t freak, it only has 1 NIC. The second one listed there in IPCONFIG is a virtual adapter for my encrypted VPN service. It has zero bearing on net-booting, as it’s virtual and part of the OS.